hadoop-hive-dev mailing list archives

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

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

Namit Jain commented on HIVE-627:

We can do the following cleanups:

1. Include a new field: OperatorCompile, which is a transient field, in the Operator
2. This can include the RowResolver - we can get rid of the whole hashmap - opParseContext.
If other operators need more compile time information, they can extend OperatorCompile.
3. All resolutions have already happened till the time optimizer is called. So, we don't need
to do any name resolution at that time. However, in order to ensure that, we should just cleanup
   the row resolver from OperatorCompile before calling the optimizer.

> 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.

View raw message