[
https://issues.apache.org/jira/browse/HIVE-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13428956#comment-13428956
]
Mahsa Mofidpoor commented on HIVE-2845:
---------------------------------------
I put my code in optimizer/physical, pretty much the same as how HIVE-1644 is
organized.
I removed the TS from topToTable and opParseContext and also the table from
topOps. Then I updated the correspondent operator and table(index table) in
OpParseContext and ParseContext respectively, but the map logs shows the
original table still being scanned.
1.Should I regenerate the operator tree afterwards? probably by using
RewriteParseContextGenerator?
2.Is a new RowResolver needed?
> Add support for index joins in Hive
> -----------------------------------
>
> Key: HIVE-2845
> URL: https://issues.apache.org/jira/browse/HIVE-2845
> Project: Hive
> Issue Type: New Feature
> Components: Indexing, Query Processor
> Reporter: Namit Jain
> Labels: indexing, joins, performance
>
> Hive supports indexes, which are used for filters currently.
> It would be very useful to add support for index-based joins in Hive.
> If 2 tables A and B are being joined, and an index exists on the join key of
> A,
> B can be scanned (by the mappers), and for each row in B, a lookup for the
> corresponding row in A can be performed.
> This can be very useful for some usecases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
