[
https://issues.apache.org/jira/browse/ORC-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17152317#comment-17152317
]
Arvin Zheng edited comment on ORC-644 at 7/21/20, 4:59 AM:
-----------------------------------------------------------
hi [~findepi],
Thanks for the reply, ORC-120 was intended to add a config item which allows
user to force ORC evolution to be positional (for backward compatibility),
which IMO mapping fields inside Struct positionally should be part of the
feature.
was (Author: arvin.zheng):
hi [~findepi],
Thanks for the reply, ORC-120 was intended to add a config item which allows
use to force ORC evolution to be positional (for backward compatibility), which
IMO mapping fields inside Struct positionally should be part of the feature.
> nested struct evolution does not respect to orc.force.positional.evolution
> --------------------------------------------------------------------------
>
> Key: ORC-644
> URL: https://issues.apache.org/jira/browse/ORC-644
> Project: ORC
> Issue Type: Bug
> Components: Java
> Affects Versions: master
> Reporter: Arvin Zheng
> Priority: Major
>
> I noticed that even when orc.force.positional.evolution is set to true, the
> nested Struct evolution is still Hive field name based, which caused some of
> our queries to return incorrect values for fields inside a nested Struct
> since our Hive column name does not match to ORC column name.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
