[
https://issues.apache.org/jira/browse/HIVE-15537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15815125#comment-15815125
]
Barna Zsombor Klara commented on HIVE-15537:
--------------------------------------------
Hi [~csun],
I think your fix to HIVE-15507 caused the differences in the qout files
reported in HIVE-15536.
At first glance it seems to me that the golden files only need to be
regenerated because they report the problem that was fixed in HIVE-15507, so it
doesn't seem to be a real regression.
Could you please double check and if I am correct then could you please update
the qout files?
Thanks!
> Nested column pruning: fix issue when selecting struct field from array/map
> element (part 2)
> --------------------------------------------------------------------------------------------
>
> Key: HIVE-15537
> URL: https://issues.apache.org/jira/browse/HIVE-15537
> Project: Hive
> Issue Type: Sub-task
> Components: Logical Optimizer
> Affects Versions: 2.2.0
> Reporter: Chao Sun
> Assignee: Chao Sun
> Attachments: HIVE-15537.1.patch, HIVE-15537.2.patch,
> HIVE-15537.3.patch
>
>
> HIVE-15507 only addresses the issue of
> {code}
> SELECT arr[0].f FROM tbl
> {code}
> However, it didn't handle:
> {code}
> SELECT arr[0].f.g FROM tbl
> {code}
> In this case the current code will generate a path {{arr.g}}, which is wrong.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
