[
https://issues.apache.org/jira/browse/HIVE-497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711246#action_12711246
]
Prasad Chakka commented on HIVE-497:
------------------------------------
actually "0" here is not a number but the internal name. so if and when 460 is
fixed, actual names are compared. name of columns change when they flow through
an operator, especially in a select op. so the colExprMap keeps a map of output
columns to input column names (or the other way round, not sure) so that
translation can be done when predicates move up (or down depending on how you
look at it) an operator.
> predicate pushdown fails if all columns are not selected
> --------------------------------------------------------
>
> Key: HIVE-497
> URL: https://issues.apache.org/jira/browse/HIVE-497
> Project: Hadoop Hive
> Issue Type: Bug
> Components: Query Processor
> Affects Versions: 0.4.0
> Reporter: Prasad Chakka
> Assignee: Prasad Chakka
> Fix For: 0.4.0
>
> Attachments: hive-497.patch
>
>
> predicate pushdown seems to fail in some scenarios... it is ok if all the
> columns are selected.
> create table ppda(a string, b string);
> select a from ppda where ppda.a > 10; --> fails
> select b from ppda where ppda.a > 10; --> ok
> select * from ppda where ppda.a > 10; --> ok
> select b from appd where appd.b > 10 and appd.a > 20; --> ok
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
