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

Sandy Pratt commented on HIVE-1643:
-----------------------------------

John,

Thanks for the feedback.  My reasoning about implementing HiveStorageHandler 
instead of HiveStoragePredicateHandler is that is seems a bit safer.  With 
HiveStorageHandler, we still have the predicate passed to us during getSplits, 
allowing us to optimize, but we're not "on the hook" to sort out pathological 
queries and do the right thing.  However, based on your feedback, I've added 
HiveStoragePredicateHandler back in and tried to filter out anything weird in 
decomposePredicate.

I'm testing a patch which allows a single equals predicate or a single or 
double ended range scan against the rowkey.  I'll let you all know how it goes. 
 As I mentioned before, I'm running CDH3u0 in all my environments, so that's 
what it will be easiest for me to test against.  The HBase integration package 
looks largely the same on trunk, so hopefully that won't be a problem.

Thanks,
Sandy


                
> support range scans and non-key columns in HBase filter pushdown
> ----------------------------------------------------------------
>
>                 Key: HIVE-1643
>                 URL: https://issues.apache.org/jira/browse/HIVE-1643
>             Project: Hive
>          Issue Type: Improvement
>          Components: HBase Handler
>    Affects Versions: 0.7.0
>            Reporter: John Sichi
>            Assignee: Vaibhav Aggarwal
>
> HIVE-1226 added support for WHERE rowkey=3.  We would like to support WHERE 
> rowkey BETWEEN 10 and 20, as well as predicates on non-rowkeys (plus 
> conjunctions etc).  Non-rowkey conditions can't be used to filter out entire 
> ranges, but they can be used to push the per-row filter processing as far 
> down as possible.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to