You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Josh Rosen (JIRA)" <ji...@apache.org> on 2015/09/22 23:23:05 UTC
[jira] [Resolved] (SPARK-10714) Refactor PythonRDD to decouple
iterator computation from PythonRDD
[ https://issues.apache.org/jira/browse/SPARK-10714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Rosen resolved SPARK-10714.
--------------------------------
Resolution: Fixed
Fix Version/s: 1.5.1
1.6.0
Issue resolved by pull request 8835
[https://github.com/apache/spark/pull/8835]
> Refactor PythonRDD to decouple iterator computation from PythonRDD
> ------------------------------------------------------------------
>
> Key: SPARK-10714
> URL: https://issues.apache.org/jira/browse/SPARK-10714
> Project: Spark
> Issue Type: Improvement
> Components: PySpark, Spark Core
> Reporter: Reynold Xin
> Assignee: Reynold Xin
> Fix For: 1.6.0, 1.5.1
>
>
> The idea is that most of the logic of calling Python actually has nothing to do with RDD (it is really just communicating with a socket -- there is nothing distributed about it), and it is only currently depending on RDD because it was written this way.
> If we extract that functionality out, we can apply it to area of the code that doesn't depend on RDDs, and also make it easier to test.
--
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