-
Notifications
You must be signed in to change notification settings - Fork 28.9k
[SPARK-11322][PySpark] Keep full stack trace in captured exception #9283
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
Conversation
|
Test build #44371 has finished for PR 9283 at commit
|
|
Test build #44395 has finished for PR 9283 at commit
|
|
Test build #44398 has finished for PR 9283 at commit
|
|
Test build #44402 has finished for PR 9283 at commit
|
|
ping @davies any comments about this? Is it in right direction? |
|
@viirya Not sure, could you post an example how the full stack trace looks like? |
|
When the exception is thrown from JVM, we see a simplified description: If we catch the exception, we can print its full stack trace: |
python/pyspark/sql/utils.py
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
'\n\t at ', make it looks like a Java stacktrace
|
Test build #44513 has finished for PR 9283 at commit
|
|
Test build #44514 has finished for PR 9283 at commit
|
python/pyspark/sql/utils.py
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
another space after at?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yap.
|
Test build #44540 has finished for PR 9283 at commit
|
|
Test build #44545 has finished for PR 9283 at commit
|
|
@davies Thanks. I think this is ready now. |
JIRA: https://issues.apache.org/jira/browse/SPARK-11322
As reported by @JoshRosen in databricks/spark-redshift/issues/89, the exception-masking behavior sometimes makes debugging harder. To deal with this issue, we should keep full stack trace in the captured exception.