[
https://issues.apache.org/jira/browse/HIVE-12645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15083616#comment-15083616
]
Ashutosh Chauhan commented on HIVE-12645:
-----------------------------------------
* We are able to replace key columns in RS with constants (where applicable)
which is good.
* However, we were earlier able to prune constants from value columns, which we
are seeming to loose now.
* Can you check changes of {{dynpart_sort_optimization2.q}} Here it seems we
are losing one MR job, which may be opposite to what test case might be wanting
to do. Because it might specifically trying to insert a job.
> ConstantPropagateProcCtx.resolve() should verify internal names first instead
> of alias to match 2 columns from different row schemas
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HIVE-12645
> URL: https://issues.apache.org/jira/browse/HIVE-12645
> Project: Hive
> Issue Type: Bug
> Reporter: Hari Sankar Sivarama Subramaniyan
> Assignee: Hari Sankar Sivarama Subramaniyan
> Attachments: HIVE-12645.1.patch, HIVE-12645.2.patch,
> HIVE-12645.3.patch
>
>
> Currently, it seems that we look to match the ColumnInfo between the parent
> and the child rowschemas by calling rci = rs.getColumnInfo(tblAlias, alias)
> which might be a bit aggressive. i.e. we will lose opportunity to constant
> propogate even if the columns are the same but the alias in the rowschemas do
> not match.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
