[
https://issues.apache.org/jira/browse/SPARK-17031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418508#comment-15418508
]
Apache Spark commented on SPARK-17031:
--------------------------------------
User 'jiangxb1987' has created a pull request for this issue:
https://github.com/apache/spark/pull/14619
> 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: [email protected]
For additional commands, e-mail: [email protected]
