[
https://issues.apache.org/jira/browse/HIVE-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13001584#comment-13001584
]
He Yongqiang commented on HIVE-1644:
------------------------------------
Take SkewJoinResolver as an example, in its resolve method, it adds all root
tasks to be iterated by the optimizer. (topNodes.addAll(pctx.rootTasks);)
Adding all root task should be good now, but you can add all tasks, and in the
second step, look at the table scan operator in the current task, if all table
scan ops are not top table scan ops, then skip this task.
And in the dispatcher, the dispatch is in process of current task. It creates a
rule R1 ( the same optimizer coder you have now.) And adds the reducer operator
tree to iterate (you may want to add the mapper operator tree.).
Please let me know if you have any questions.
> use filter pushdown for automatically accessing indexes
> -------------------------------------------------------
>
> Key: HIVE-1644
> URL: https://issues.apache.org/jira/browse/HIVE-1644
> Project: Hive
> Issue Type: Improvement
> Components: Indexing
> Affects Versions: 0.7.0
> Reporter: John Sichi
> Assignee: Russell Melick
> Attachments: HIVE-1644.1.patch, HIVE-1644.2.patch, HIVE-1644.3.patch,
> HIVE-1644.4.patch
>
>
> HIVE-1226 provides utilities for analyzing filters which have been pushed
> down to a table scan. The next step is to use these for selecting available
> indexes and generating access plans for those indexes.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
