hadoop-hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zheng Shao (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HIVE-627) Optimizer should only access RowSchema (and not RowResolver)
Date Mon, 13 Jul 2009 20:29:14 GMT

    [ https://issues.apache.org/jira/browse/HIVE-627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730495#action_12730495
] 

Zheng Shao commented on HIVE-627:
---------------------------------

Talked with Namit offline. Namit can add more details, but the synopsis is that we should
be able to do it, and the best way is to wipe out the RowResolvers before we enter into the
optimization phase.


> Optimizer should only access RowSchema (and not RowResolver)
> ------------------------------------------------------------
>
>                 Key: HIVE-627
>                 URL: https://issues.apache.org/jira/browse/HIVE-627
>             Project: Hadoop Hive
>          Issue Type: Improvement
>            Reporter: Zheng Shao
>
> The column pruner is accessing RowResolver a lot of times, for things like reverseLookup,
and get(alias, column).
> These are not necessary - we should not need to translate an internal name to (alias,
column) and then translate back. We should be able to use internal name from one operator
to the other, using RowSchema.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message