[
https://issues.apache.org/jira/browse/HIVE-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977472#action_12977472
]
John Sichi commented on HIVE-1643:
----------------------------------
Notes for working on this:
Background is in
http://wiki.apache.org/hadoop/Hive/FilterPushdownDev
* In HiveHBaseTableInputFormat, newIndexPredicateAnalyzer needs to add
additional operators (and stop restricting the allowed column names). And then
convertFilter needs to set up corresponding HBase filter conditions based on
the predicates it finds. Note that for inequality conditions on the key, it's
necessary to muck with startRow/stopRow (not just the filter evaluator).
* See also the comment in HBaseStorageHandler.decomposePredicate. Currently,
it can only accept a single predicate. If you want to be able to support AND
of multiple predicates (using HBase's FilterList) then this will need to be
relaxed.
* Beware of the fact that until HIVE-1538 gets committed, it is more difficult
to make sure that the HBase-level filtering is working as expected. The reason
is that without HIVE-1538, a second copy of the filter gets applied within Hive
(regardless of how the filter was decomposed when it was pushed down to HBase).
So even if HBase doesn't filter out everything you're expecting it to, you
won't notice in the results since Hive will do the filtering again.
> 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: John Sichi
> Fix For: 0.7.0
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
