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: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
