Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/2217#issuecomment-54344150
Thanks for the PR. Do you mind closing it?
In any case, this changes a fundamental assumption in broadcast variables,
and can brings in potentially unsafe consequences and break existing code
somewhere else in Spark or in other frameworks built on top of Spark. I believe
you should be able to find workarounds even without changing the mutability of
broadcast variables. It is best to not do this right now.
If you think we need a new primitive for doing this, you are welcome to
write up a design doc that discusses the benefits and the long term
maintainability of the primitive.
---
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]
