Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/3679#issuecomment-67119469
@jbencook Thanks for the updates! (Your comment about checking for
exceptions makes me wonder if you were right before to throw a more meaningful
exception than a Py4JJavaError. But at least the error message includes the
Scala-side error message. If you prefer to catch the Py4JJavaError, identify
the issue, and report a simpler error message, that could be nice, though it'd
require reinstating some of your code. Whatever you think best. I'd say it's
good to go.)
CC: @mengxr LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
