[
https://issues.apache.org/jira/browse/KUDU-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16051545#comment-16051545
]
Yi Guolei commented on KUDU-2038:
---------------------------------
What about this way:
1. Add index(maybe bitmap index) just on base cfile and the bitmap is
immutable.
2. Apply mutations to index according to query timestamp while reading.
3. using the new index to query data.
At most time, there are only several mutations, so the step 2 is very quickly.
And also we could cache the index to accelerate the upcoming queries.
> 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: Wish
> Reporter: Yi Guolei
>
> 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
(v6.4.14#64029)
