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

Russell Melick updated HIVE-1644:
---------------------------------

    Attachment: HIVE-1644.7.patch

HIVE-1744.7.patch:

@Yongqiang, I fixed the problems in GenMRTableScal1.java, and think I have 
dealt with most of your comments.  I'm confused about what you mean with the 
combinehiveinputformat.

@John, I made a first attempt at factoring SemanticAnalyzer calls into the 
ParseContext, but would appreciate your input.  This patch will also fail the 
unit test index_opt_where_simple.q as it stands.  However, if you remove the 
lines that attempt to use manual indexing, it succeeds.  The test that succeeds 
looks like

{code:sql}
CREATE INDEX src_index ON TABLE src(key) as 'COMPACT' WITH DEFERRED REBUILD;
ALTER INDEX src_index ON src REBUILD;

SET hive.optimize.autoindex=true;
EXPLAIN SELECT key, value FROM src WHERE key=86 ORDER BY key;
SELECT key, value FROM src WHERE key=86 ORDER BY key;

DROP INDEX src_index on src;
{code}

It appears as if our regular expression that identifies WHERE clauses by 
looking for FIL operators (filters) may not be specific enough.  I think the 
remaining errors might be caused by trying to generate index queries for both 
the {{{SELECT ... FROM src}}} (as desired), and the {{{SELECT ... FROM 
default__src_src_index__}}} that we generated, which is a problem.

> 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-1644.5.patch, HIVE-1644.6.patch, HIVE-1644.7.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