Github user willb commented on the pull request:
https://github.com/apache/spark/pull/143#issuecomment-38189119
Thanks for the quick review, @kayousterhout! I think that the current
state of the branch addresses all of the concerns you raised; sorry that I had
to dig in a little more than I expected to verify how things were working in
`DStream`.
If anyone has further thoughts about making this a configurable option,
please let me know. The approach I'm currently taking to
[SPARK-729](https://spark-project.atlassian.net/browse/SPARK-729) depends on
serializability checking happening in `ClosureCleaner.clean`, so if we did
decide to make this checking optional it would affect when variable capture
occurred if the option were disabled (as well as requiring that the
serializability check go back in to `DAGScheduler`, at least conditionally, as
mentioned above).
---
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.
---
