[ https://issues.apache.org/jira/browse/HIVE-627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730561#action_12730561 ]
Zheng Shao commented on HIVE-627: --------------------------------- Will we be able to clean up the whole OperatorCompile before optimization? Also I feel that 1 and 2 can be done together but 3 can be separate by itself. We can do 1 and 2 in a separate issue. The changes in 3 includes: 3.1. clean up opParseContext before we enter into optimization step; 3.2. make ColumnPruner use RowSchema instead of RowResolver. > 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.