Github user squito commented on the pull request:
https://github.com/apache/spark/pull/7028#issuecomment-115466021
OK, I took a closer look at the the way the exception handling works and I
see what you mean. I'm not particularly tied to that formatting I suggested,
that was just an example, totally fine to do something else that is similar. I
agree that as long as the user can clearly identify their code in the driver,
and their code in the executors, that is a big help.
I think either of your proposed solutions sound fine -- I'm also a little
partial to (2) if its simpler. I am not sure I understand it 100%, but sounds
good :)
---
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
