GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/9283
[SPARK-11322][PySpark] Keep full stack trace in captured exception
JIRA: https://issues.apache.org/jira/browse/SPARK-11322
As reported by @JoshRosen in
[databricks/spark-redshift/issues/89](https://github.com/databricks/spark-redshift/issues/89#issuecomment-149828308),
the exception-masking behavior sometimes makes debugging harder. To deal with
this issue, we should keep full stack trace in the captured exception.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/viirya/spark-1 py-exception-stacktrace
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/9283.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #9283
----
commit 0ccb4ae38b797c10dfea45d762932bb07d1d9d53
Author: Liang-Chi Hsieh <[email protected]>
Date: 2015-10-26T17:33:17Z
Keep full stack trace in captured exception.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
