Github user willb commented on the pull request:
https://github.com/apache/spark/pull/189#issuecomment-38738160
In the discussion on #143, we were talking about whether or not it made
sense to omit the closure serializability check in `DAGScheduler`. Since this
branch, which combines serializability checking and variable capture, removes
serializability checking for the closure argument to `SparkContext.runJob`, I
think it makes sense to either (1) re-introduce the check in `DAGScheduler`, or
(2) add another option to the internal `clean` methods (in `SparkContext` and
`ClosureCleaner`) allowing checking for serializability without forcing
variable capture.
I am inclined to prefer the first option but am interested in other
opinions on the matter.
---
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.
---
