[
https://issues.apache.org/jira/browse/HIVE-20693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17492847#comment-17492847
]
Dagang Wei edited comment on HIVE-20693 at 2/15/22, 7:39 PM:
-------------------------------------------------------------
The workaround is mentioned here in the mail archive [1]:
{{set orc.force.positional.evolution=true;}}
[1]:
[https://www.mail-archive.com/user@orc.apache.org/msg00229.html|https://www.mail-archive.com/user@orc.apache.org/msg00229.html.]
was (Author: functicons):
The workaround is mentioned here in the mail archive [1]:
{{set orc.force.positional.evolution=true;}}{{}}
[1]:
[https://www.mail-archive.com/user@orc.apache.org/msg00229.html|https://www.mail-archive.com/user@orc.apache.org/msg00229.html.]
> Case-sensitivity for column names when reading from ORC
> -------------------------------------------------------
>
> Key: HIVE-20693
> URL: https://issues.apache.org/jira/browse/HIVE-20693
> Project: Hive
> Issue Type: Bug
> Components: Hive, ORC
> Affects Versions: 2.3.2
> Reporter: Alexandre Crayssac
> Priority: Major
>
> Hello everyone,
> I observed a different behavior between version 1.2.1 and 2.3.2 (that's the
> only two versions I've been able to test).
> When creating an external table pointing to ORC files and having upper cased
> column names in the ORC files metadata I'm able to read the data on 1.2.1 but
> not on 2.3.2.
> I tested with both upper cased and lower cased column names in my CREATE
> TABLE statement and it does not work in both cases. Looks like normal since
> column names are normalized to lower case in Hive.
> So, I would like to know if this is a feature or a bug in Hive 2.3.2 ?
> In fact, if this is a feature it would be impossible to have upper case
> column names in ORC files with Hive 2.3.2.
> Please, let me know if you need more informations.
> Kind regards,
> Alexandre
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
