Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/5335#issuecomment-92176190
I also feel that the current approach makes more sense than Josh's
alternative. Changes to SparkContext get a lot of scrutiny during code review,
so clear documentation, IMO is sufficient to ensure this is followed correctly
(famous last words). I didn't have time to dive into this to make sure there
are no correctness issues, but the broad approach looks good to me... I think
it's worth fixing this up.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
