Liang-Chi Hsieh 3dfa4ea526 [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.		2015-10-28 21:45:00 -07:00
..
docs	[SPARK-10447][SPARK-3842][PYSPARK] upgrade pyspark to py4j0.9	2015-10-20 10:52:49 -07:00
lib	[SPARK-10447][SPARK-3842][PYSPARK] upgrade pyspark to py4j0.9	2015-10-20 10:52:49 -07:00
pyspark	[SPARK-11322] [PYSPARK] Keep full stack trace in captured exception	2015-10-28 21:45:00 -07:00
test_support	[SPARK-11292] [SQL] Python API for text data source	2015-10-28 14:28:38 -07:00
.gitignore	[SPARK-3946] gitignore in /python includes wrong directory	2014-10-14 14:09:39 -07:00
run-tests	[SPARK-8583] [SPARK-5482] [BUILD] Refactor python/run-tests to integrate with dev/run-tests module system	2015-06-27 20:24:34 -07:00
run-tests.py	[SPARK-7018][BUILD] Refactor dev/run-tests-jenkins into Python	2015-10-18 22:45:27 -07:00