You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2015/11/02 06:13:27 UTC

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

    [ https://issues.apache.org/jira/browse/SPARK-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14984753#comment-14984753 ] 

Apache Spark commented on SPARK-5354:
-------------------------------------

User 'nongli' has created a pull request for this issue:
https://github.com/apache/spark/pull/9404

> 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
>
> *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: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org