Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Fri, 18 Mar 2011 03:18:39 +0000 (UTC)
From: "Russell Melick (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: 
 <233196770.10913.1300418319609.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Updated: (HIVE-1644) use filter pushdown for automatically
 accessing indexes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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.8.patch

HIVE-1644.8.patch

Fixed unit tests per John and Yonqiang.  Cleaned up comments.  Ready for review.  I still have a few questions that are probably best answered in the review:

 * When we have multiple indexes, and we get different tasks lists from querying each index, what should we do?  Right now we use all tasks (IndexWhereProcessor.java:57)
 * Is it possible to improve the regex we use so that it only matches WHERE clauses?  Right now we use FIL to get to the WHERE (IndexWhereTaskDispatcher.java:141)
 * What comparison operators should we support?  Right now it's only <, >, and =.  We don't have <= or >= (CompactIndexHandler.java:272)

Should I put this into the reviewboard?

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