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

Posted to issues@spark.apache.org by "Jiang Xingbo (JIRA)" <ji...@apache.org> on 2016/11/29 10:29:58 UTC

[jira] [Closed] (SPARK-17031) Add `Scanner` operator to wrap the optimized plan directly in planner

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

Jiang Xingbo closed SPARK-17031.
--------------------------------
    Resolution: Won't Fix

We don't want this now.

> Add `Scanner` operator to wrap the optimized plan directly in planner
> ---------------------------------------------------------------------
>
>                 Key: SPARK-17031
>                 URL: https://issues.apache.org/jira/browse/SPARK-17031
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>            Reporter: Jiang Xingbo
>
> We should add a wrapper node for scan(table scan or file scan), and this wrapper node can also hold project list and filter conditions. Then in optimizer we can improve the ColumnPrunning and FilterPushdown rules to push down into this wrapper node. After this we don't need PhysicalOperator anymore and the planner can match on the wrapper node directly.



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