You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Herman van Hovell (JIRA)" <ji...@apache.org> on 2016/10/23 11:26:58 UTC
[jira] [Resolved] (SPARK-18038) Move output partitioning definition
from UnaryNodeExec to its children
[ https://issues.apache.org/jira/browse/SPARK-18038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Herman van Hovell resolved SPARK-18038.
---------------------------------------
Resolution: Fixed
Fix Version/s: 2.1.0
> Move output partitioning definition from UnaryNodeExec to its children
> ----------------------------------------------------------------------
>
> Key: SPARK-18038
> URL: https://issues.apache.org/jira/browse/SPARK-18038
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 2.0.1
> Reporter: Tejas Patil
> Assignee: Tejas Patil
> Priority: Trivial
> Fix For: 2.1.0
>
>
> This was a suggestion by [~rxin] over one of the dev list discussion : http://apache-spark-developers-list.1001551.n3.nabble.com/Project-not-preserving-child-partitioning-td19417.html
> {noformat}
> I think this is very risky because preserving output partitioning should not be a property of UnaryNodeExec (e.g. exchange).
> It would be better (safer) to move the output partitioning definition into each of the operator and remove it from UnaryExecNode.
> {noformat}
--
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