You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Yin Huai (JIRA)" <ji...@apache.org> on 2015/10/29 22:12:27 UTC

[jira] [Updated] (SPARK-5354) Set InMemoryColumnarTableScan's outputPartitioning and outputOrdering

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

Yin Huai updated SPARK-5354:
----------------------------
    Summary: Set InMemoryColumnarTableScan's outputPartitioning and outputOrdering  (was: When possible, correctly set outputPartitioning for leaf SparkPlans)

> Set InMemoryColumnarTableScan's outputPartitioning and outputOrdering
> ---------------------------------------------------------------------
>
>                 Key: SPARK-5354
>                 URL: https://issues.apache.org/jira/browse/SPARK-5354
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>            Reporter: Yin Huai
>
> Right now, Spark SQL is not aware of the partitioning scheme of a leaf SparkPlan (e.g. an input table). So, even users want to re-partitioning the data in advance, Exchange operators will still be used.



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