Skip to content

[SPARK-42329][SQL]Assign name to _LEGACY_ERROR_TEMP_2256 #51113

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

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

yuexing
Copy link
Contributor

@yuexing yuexing commented Jun 8, 2025

What changes were proposed in this pull request?

see https://issues.apache.org/jira/browse/SPARK-42329. Assign a meaningful name to error _LEGACY_ERROR_TEMP_2256.

Why are the changes needed?

see https://issues.apache.org/jira/browse/SPARK-42329

Does this PR introduce any user-facing change?

No

How was this patch tested?

UT, there's an existing UT.

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

No

@@ -1775,6 +1775,12 @@
],
"sqlState" : "39000"
},
"FOREACH_WRITER_ABORTED" : {
"message" : [
"Foreach writer has been aborted due to a task failure."
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we take a look at adding a hint for the user on how to actually overcome this issue? Is it possible to point to which task failed or what could prevent it to fail?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hi @mihailom-db , sure. I actually thought about it while renaming, but at that point I was not sure whether it's a good idea to change the msg (exposed to the user) in one commit. Since you also mentioned, I'll just do it ;)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hi @mihailom-db I did an update, please take a look. Unfortunately, it can only capture error detail during Write now. if the exception is thrown from earlier stage, but abort during Write, then the error detail can't be captured.

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.

2 participants