[
https://issues.apache.org/jira/browse/SPARK-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yin Huai updated SPARK-5354:
----------------------------
Assignee: Nong Li
> 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
> Assignee: Nong Li
> Fix For: 1.6.0
>
>
> *Updated*
> Right now, Spark SQL is not aware of the outputPartitioning and
> outputOrdering of a InMemoryColumnarTableScan. Actually, we can just inherit
> these two properties from the {{SparkPlan}} of the cached table.
> *Original*
> 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: [email protected]
For additional commands, e-mail: [email protected]
