[
https://issues.apache.org/jira/browse/HIVE-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884434#action_12884434
]
Namit Jain commented on HIVE-417:
---------------------------------
if (work.getReducer() != null) {
work.getReducer().jobClose(job, success, feedBack);
}
if (IndexBuilderBaseReducer.class.isAssignableFrom(this
.getReducerClass())) {
this.closeIndexBuilder(job, success);
}
}
Instead of the above code in ExecDriver,
IndexBuilderBaseReducer/CompactSumReducer should have a jobClose - no code
change needed in ExecDriver.
I would still vote for the index code to be in contrib, it will take some time
to clean it up - then it should be moved to the mainline.
Till then, it is usable, but in a prototype state.
What we should aim for is minimum changes in ql/. and put all changes in
contrib for now. As they become stable, we can pull them
in - even the DDLSemanticAnalyzer should be factored in contrib
> 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.3.0, 0.3.1, 0.4.0, 0.6.0
> Reporter: Prasad Chakka
> Assignee: He Yongqiang
> Attachments: hive-417.proto.patch, hive-417－2009-07-18.patch,
> hive-indexing.3.patch, hive-indexing.5.thrift.patch,
> indexing_with_ql_rewrites_trunk_953221.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.
