diff options
| author | Liang-Chi Hsieh <viirya@appier.com> | 2015-10-28 21:45:00 -0700 |
|---|---|---|
| committer | Davies Liu <davies.liu@gmail.com> | 2015-10-28 21:45:00 -0700 |
| commit | 3dfa4ea526c881373eeffe541bc378d1fa598129 (patch) | |
| tree | e3c34549d962b02f9d82adda6cde103317bdbd85 /sql/catalyst | |
| parent | 0cb7662d8683c913c4fff02e8fb0ec75261d9731 (diff) | |
| download | spark-3dfa4ea526c881373eeffe541bc378d1fa598129.tar.gz spark-3dfa4ea526c881373eeffe541bc378d1fa598129.tar.bz2 spark-3dfa4ea526c881373eeffe541bc378d1fa598129.zip | |
[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.
Author: Liang-Chi Hsieh <viirya@appier.com>
Closes #9283 from viirya/py-exception-stacktrace.
Diffstat (limited to 'sql/catalyst')
0 files changed, 0 insertions, 0 deletions