You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Wenchen Fan (JIRA)" <ji...@apache.org> on 2016/07/12 09:20:20 UTC

[jira] [Resolved] (SPARK-16189) Add ExistingRDD logical plan for input with RDD to have a chance to eliminate serialize/deserialize.

     [ https://issues.apache.org/jira/browse/SPARK-16189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wenchen Fan resolved SPARK-16189.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 2.1.0

Issue resolved by pull request 13890
[https://github.com/apache/spark/pull/13890]

> Add ExistingRDD logical plan for input with RDD to have a chance to eliminate serialize/deserialize.
> ----------------------------------------------------------------------------------------------------
>
>                 Key: SPARK-16189
>                 URL: https://issues.apache.org/jira/browse/SPARK-16189
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>            Reporter: Takuya Ueshin
>             Fix For: 2.1.0
>
>
> Currently the input {{RDD}} of {{Dataset}} is always serialized to {{RDD\[InternalRow\]}} prior to being as {{Dataset}}, but there is a case that we use {{map}} or {{mapPartitions}} just after converted to {{Dataset}}.
> In this case, serialize and then deserialize happens but it would not be needed.
> This patch adds {{ExistingRDD}} logical plan for input with {{RDD}} to have a chance to eliminate serialize/deserialize.



--
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