Skip to content

fix: native error message not propagated to SparkException on empty errorClass#3727

Open
manuzhang wants to merge 1 commit intoapache:mainfrom
manuzhang:fix-SparkErrorConverter
Open

fix: native error message not propagated to SparkException on empty errorClass#3727
manuzhang wants to merge 1 commit intoapache:mainfrom
manuzhang:fix-SparkErrorConverter

Conversation

@manuzhang
Copy link
Member

Closes #3726.

@manuzhang
Copy link
Member Author

@parthchandra Please help review when you are free.

@mbutrovich
Copy link
Contributor

The original issue references a test failing, are we passing that now? Do we need to make any changes to the test (are we skipping it?)

@manuzhang
Copy link
Member Author

@mbutrovich The failure was from previous commit of #2897, not on the main branch.

Copy link
Contributor

@parthchandra parthchandra left a comment

Choose a reason for hiding this comment

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

This change is fine. It would be good to know what the root cause of the failure was and to ensure that the error is actually handled correctly in native.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Native error is not propagated to SparkException when errorClass is empty

3 participants