You are viewing a plain text version of this content. The canonical link for it is here.

Posted to reviews@spark.apache.org by GitBox <gi...@apache.org> on 2020/05/28 14:27:02 UTC

[GitHub] [spark] srowen commented on pull request #28661: [SPARK-31849][PYTHON][SQL] Make PySpark exceptions more Pythonic

srowen commented on pull request #28661:
URL: https://github.com/apache/spark/pull/28661#issuecomment-635383500


   Yeah that stack trace can be the only useful info in some cases, when the real error is on the JVM side. I get that Python users don't understand it as well. But otherwise by default users won't have much context for an error that occurs, when debugging or reporting it. At the least, leave it on by default? but how unfriendly is it really?


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org