-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expected a closure; got ... IndexedRDD$MultiputZipper #19
Comments
I am getting the same warning all over the place:
I am working with Scala 2.11.7 from release 0.3. |
+1 16/05/24 04:24:30 WARN ClosureCleaner: Expected a closure; got edu.berkeley.cs.amplab.spark.indexedrdd.IndexedRDD$LeftJoinZipper Scala 2.10, IndexedRdd 0.3 from within a Spark 1.6.1 Streaming Job my guess is - as the error says - we're referencing something outside of the RDD closure. it's not killing my job, so i'm happy for now, but the WARN is scary! |
+1
if it helps: someone filed this issue on the spark JIRA, so technically the warning might be false alarm https://issues.apache.org/jira/browse/SPARK-11630 Using Scala 2.11, indexedrdd 0.3 and spark 1.5.1 |
+1 using scala 2.11.7,indexedRDD 0.3 and spark2.0.0 How to fix the problem ? |
+1 |
1 similar comment
+1 |
+1 Anyone answer? |
+1 Expected a closure; got edu.berkeley.cs.amplab.spark.indexedrdd.IndexedRDD$FullOuterJoinZipper |
+1 |
1 similar comment
+1 |
While running your example from the README on a recent Spark (2.0-SNAPSHOT) compiled for 2.11.7, I'm seeing the following exception:
I've compiled your package and its dependency (PART) setting scalaVersion to 2.11.7 and published it to the local Ivy repo. Do you think the problem I'm experiencing is related to Scala or Spark version I'm using (I'd like to stay on Scala 2.11 for my project)? If so, what would your roadmap look like for releasing the Scala 2.11 version of your package (see issue #12)? Thanks
The text was updated successfully, but these errors were encountered: