[
https://issues.apache.org/jira/browse/HIVE-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12998148#comment-12998148
]
Russell Melick commented on HIVE-1644:
--------------------------------------
Like we said, writing the index query to the temp file is broken in patch 2. I
tried to look into the approach you mentioned above: using the already
generated tmp file resulting from the SELECT query.
I set a breakpoint in
{{org.apache.hadoop.hive.ql.optimizer.GenMapRedUtils.splitTasks}} when
executing index_opt_where.q to examine the temp file name, but that method was
never executed. Do you know why? Even looking through that method, it appears
that we only know the directory of the temp file (with {{String taskTmpDir =
baseCtx.getMRTmpFileURI();}}, and we never know the actual file name. Without
the actual name, we cannot set the input config correctly. Is this the right
place to be looking?
> use filter pushdown for automatically accessing indexes
> -------------------------------------------------------
>
> Key: HIVE-1644
> URL: https://issues.apache.org/jira/browse/HIVE-1644
> Project: Hive
> Issue Type: Improvement
> Components: Indexing
> Affects Versions: 0.7.0
> Reporter: John Sichi
> Assignee: Russell Melick
> Attachments: HIVE-1644.1.patch, HIVE-1644.2.patch
>
>
> HIVE-1226 provides utilities for analyzing filters which have been pushed
> down to a table scan. The next step is to use these for selecting available
> indexes and generating access plans for those indexes.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
