You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2016/01/08 15:12:39 UTC
[jira] [Resolved] (SPARK-573) Clarify semantics of the parallelized
closures
[ https://issues.apache.org/jira/browse/SPARK-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Owen resolved SPARK-573.
-----------------------------
Resolution: Won't Fix
> Clarify semantics of the parallelized closures
> ----------------------------------------------
>
> Key: SPARK-573
> URL: https://issues.apache.org/jira/browse/SPARK-573
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Reporter: tjhunter
> Priority: Minor
>
> I do not think there is any guideline about which features of scala are allowed/forbidden in the closure that gets sent to the remote nodes. Two examples I have are a return statement and updating mutable variables of singletons.
> Ideally, a compiler plugin could give an error at compile time, but a good error message at run time would be good also.
> Are there any other cases that should not be allowed?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org