[
https://issues.apache.org/jira/browse/KUDU-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17238400#comment-17238400
]
Andrew Wong commented on KUDU-2038:
-----------------------------------
There is a patch for bitmap indexing out, but I don't think it is being
actively worked on right now: https://gerrit.cloudera.org/c/11722/. It is
something that I have wanted to revisit, but haven't had the time to prioritize
recently.
KUDU-3033 is another ticket that I think would be really helpful for reducing
IO for selective predicates, but again I'm unaware of anyone working on it. If
you're interested in picking up either feature, I'd be happy to help design and
review.
> Add b-tree or inverted index on value field
> -------------------------------------------
>
> Key: KUDU-2038
> URL: https://issues.apache.org/jira/browse/KUDU-2038
> Project: Kudu
> Issue Type: Task
> Reporter: Yi Guolei
> Priority: Major
> Labels: roadmap-candidate
>
> Do we have a plan to add index on any column [not primary column] ? Currently
> kudu does not have btree or inverted index on columns. In this case if a
> query wants to filter a column then kudu has to scan all datas in all
> rowsets.
> For example, select * from table where salary > 10000 and age < 40, the bloom
> filter or min max index will have no effect, kudu has to scan all datas in
> all row sets. But if kudu has inverted index, then it will be much faster.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
