[
https://issues.apache.org/jira/browse/HIVE-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734203#action_12734203
]
Prasad Chakka commented on HIVE-417:
------------------------------------
1) Are you worried about the sort phase of the reducer or the IndexBuilder's
reducer code? I don't think former issue will be a problem. The later issue can
be avoided by writing multiple rows for a key if the number of offsets exceed a
certain limit. So reducer can flush the offsets periodically to disk thus
avoiding OutOfMemory exceptions in reducer.
2) What are the other options for the index output format?
> 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
> Attachments: hive-417.proto.patch, hive-417－2009-07-18.patch
>
>
> 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.
