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

HyukjinKwon commented on pull request #28661: URL: https://github.com/apache/spark/pull/28661#issuecomment-635710262 > if this is only removing "unhelpful" stack traces from the console, I can see it. I am pretty certain on this. Actually, this is why I am hiding JVM strackstrace

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

HyukjinKwon commented on pull request #28661: URL: https://github.com/apache/spark/pull/28661#issuecomment-635404514 I actually didn't quite care about it but realised that people actually pretty hate the JVM stacktrace in Python exceptions. Maybe it's because you (and I .. and most of

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

HyukjinKwon commented on pull request #28661: URL: https://github.com/apache/spark/pull/28661#issuecomment-635172575 > One question I have is if we should hide JVM stacktrace for all PySpark exceptions? Is any kind of exception that looks not making sense or useless without JVM

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

HyukjinKwon commented on pull request #28661: URL: https://github.com/apache/spark/pull/28661#issuecomment-635172759 retest this please This is an automated message from the Apache Git Service. To respond to the message,