diff options
author | Andrew Or <andrewor14@gmail.com> | 2014-08-20 17:07:39 -0700 |
---|---|---|
committer | Andrew Or <andrewor14@gmail.com> | 2014-08-20 17:07:39 -0700 |
commit | ba3c730e35bcdb662396955c3cc6f7de628034c8 (patch) | |
tree | 83ebd4cade1acd7f7f204edd132b6b503a193a37 /project/MimaExcludes.scala | |
parent | c9f743957fa963bc1dbed7a44a346ffce1a45cf2 (diff) | |
download | spark-ba3c730e35bcdb662396955c3cc6f7de628034c8.tar.gz spark-ba3c730e35bcdb662396955c3cc6f7de628034c8.tar.bz2 spark-ba3c730e35bcdb662396955c3cc6f7de628034c8.zip |
[SPARK-3140] Clarify confusing PySpark exception message
We read the py4j port from the stdout of the `bin/spark-submit` subprocess. If there is interference in stdout (e.g. a random echo in `spark-submit`), we throw an exception with a warning message. We do not, however, distinguish between this case from the case where no stdout is produced at all.
I wasted a non-trivial amount of time being baffled by this exception in search of places where I print random whitespace (in vain, of course). A clearer exception message that distinguishes between these cases will prevent similar headaches that I have gone through.
Author: Andrew Or <andrewor14@gmail.com>
Closes #2067 from andrewor14/python-exception and squashes the following commits:
742f823 [Andrew Or] Further clarify warning messages
e96a7a0 [Andrew Or] Distinguish between unexpected output and no output at all
Diffstat (limited to 'project/MimaExcludes.scala')
0 files changed, 0 insertions, 0 deletions