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

John Sichi commented on HIVE-1644:
----------------------------------

After looking into this some more, it seems like there are some problems with 
the approach.  Trying to splice in an INSERT statement directly into the SELECT 
plan is going to run into trouble since we would normally do extra processing 
work to move the INSERT results (which first get written to an intermediate dir 
for atomicity) to the correct location.

So either we need to make some changes with the current approach (by using a 
fetchless query and figuring out the remaining parsecontext merge issues, maybe 
getting some help from Persistent Systems since they have figured out a lot of 
complicated splicing), or we need to keep it as INSERT, but instead of trying 
to splice the operator trees together, we do the following:

* fully compile the INSERT statement all the way into a task list (instead of 
stopping at the operator tree)
* add this task list in front of the root tasks for the main select
* leave the parse context and operator tree for the main select alone (other 
than sticking in the index inputformat information)

This is a little clumsy, but keeps the analysis for the two statements 
isolated, and would more closely mimic the way the manual approach works.


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

        

Reply via email to