Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SPARK-44640][PYTHON][FOLLOW-UP][3.5] Update UDTF error messages to include method name #42840

Conversation

allisonwang-db
Copy link
Contributor

(cherry picked from commit 3e22c86)

What changes were proposed in this pull request?

This PR is a follow-up for SPARK-44640 to make the error message of a few UDTF errors more informative by including the method name in the error message (eval or terminate).

Why are the changes needed?

To improve error messages.

Does this PR introduce any user-facing change?

No

How was this patch tested?

Existing tests.

Was this patch authored or co-authored using generative AI tooling?

No

…e method name

This PR is a follow-up for SPARK-44640 to make the error message of a few UDTF errors more informative by including the method name in the error message (`eval` or `terminate`).

To improve error messages.

No

Existing tests.

No

Closes apache#42726 from allisonwang-db/SPARK-44640-follow-up.

Authored-by: allisonwang-db <[email protected]>
Signed-off-by: Takuya UESHIN <[email protected]>
(cherry picked from commit 3e22c86)
Signed-off-by: allisonwang-db <[email protected]>
@allisonwang-db
Copy link
Contributor Author

cc @ueshin

@HyukjinKwon
Copy link
Member

Merged to branch-3.5.

HyukjinKwon pushed a commit that referenced this pull request Sep 7, 2023
…nclude method name

(cherry picked from commit 3e22c86)

### What changes were proposed in this pull request?

This PR is a follow-up for SPARK-44640 to make the error message of a few UDTF errors more informative by including the method name in the error message (`eval` or `terminate`).

### Why are the changes needed?

To improve error messages.

### Does this PR introduce _any_ user-facing change?

No

### How was this patch tested?

Existing tests.

### Was this patch authored or co-authored using generative AI tooling?

No

Closes #42840 from allisonwang-db/spark-44640-follow-up-3.5.

Authored-by: allisonwang-db <[email protected]>
Signed-off-by: Hyukjin Kwon <[email protected]>
@HyukjinKwon HyukjinKwon closed this Sep 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants