[
https://issues.apache.org/jira/browse/HIVE-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Syed S. Albiz updated HIVE-2128:
--------------------------------
Attachment: HIVE-2128.2.patch
Hmm, you're right, we would need multiple blockfilter files in that case. I'm
not sure if that is possible though in the framework we have, given that we
choose one single index query to generate each time at each stage. In the case
where we have multiple indexes involved at each stage, the index handler is
responsible for combining index inputs into a single output file. For example,
I have attached a case that seems like it might cause problems (both src and
srcpart have indexes built and filters applied), however since the index
queries are generated separately for separate table scans it seems like there
is no collision between blockfilter files. Does this address the issue? It
seems like there might still be a possibility of collision between table and
blockfilter file, so I wonder if you had a different case in mind?
> Automatic Indexing with multiple tables
> ---------------------------------------
>
> Key: HIVE-2128
> URL: https://issues.apache.org/jira/browse/HIVE-2128
> Project: Hive
> Issue Type: Improvement
> Components: Indexing
> Affects Versions: 0.8.0
> Reporter: Russell Melick
> Assignee: Syed S. Albiz
> Attachments: HIVE-2128.1.patch, HIVE-2128.1.patch, HIVE-2128.2.patch
>
>
> Make automatic indexing work with jobs which access multiple tables. We'll
> probably need to modify the way that the index input format works in order to
> associate index formats/files with specific tables.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
