[
https://issues.apache.org/jira/browse/HIVE-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13482080#comment-13482080
]
Lianhui Wang commented on HIVE-1643:
------------------------------------
Ashutosh Chauhan
Is this correct? What about filters on OR conditions and nested filters. Do you
plan to add support for those ?
select * from tt where col1 < 23 or (col2 < 2 and col3 = 5) or (col4 = 6 and
(col5 = 3 or col6 = 7));
i think there should need range analyze.
in mysql, sql optimizer include the range analyze on partition and index.
binary tree represent conditions ranges.
but there are some difficulties in task split.
because maybe there are many small ranges in one table region. so maybe merge
multi small ranges in one region and use rowkeyFilter.
that can reduce one region's visits.
> 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.9.0
> Reporter: John Sichi
> Assignee: bharath v
> Labels: patch
> Attachments: hbase_handler.patch, Hive-1643.2.patch, HIVE-1643.patch
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
