[
https://issues.apache.org/jira/browse/HIVE-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12710591#action_12710591
]
He Yongqiang commented on HIVE-417:
-----------------------------------
>that is not the case if the index is on a non-primary key column. and i think,
>mostly this is the case where indexes will be used in data warehouses.
Yes. If the index is built on one column, the block/pos list's size will be
large. But if it is built on many columns, i think the block/pos list's size
will be small.
Anyway, we can build this index as the first step.
And after this finished, we can try other kinds of index, like:
1) sort based index
2) lucene index
3) block-scope B+Tree or R-tree or other advantage index data structures.
Prasad, you said you already wrote some code, would you please attach it?
> Implement Indexing in Hive
> --------------------------
>
> Key: HIVE-417
> URL: https://issues.apache.org/jira/browse/HIVE-417
> Project: Hadoop Hive
> Issue Type: New Feature
> Components: Metastore, Query Processor
> Affects Versions: 0.2.0, 0.3.0, 0.3.1, 0.4.0
> Reporter: Prasad Chakka
> Assignee: He Yongqiang
>
> Implement indexing on Hive so that lookup and range queries are efficient.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
