[
https://issues.apache.org/jira/browse/HIVE-19638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16780457#comment-16780457
]
Mass Dosage commented on HIVE-19638:
------------------------------------
Has this been merged into any released versions of Hive? We'd really like it in
the 2.3.x line and I'd be happy to help with the changes needed to get it in
there.
[~pvary] is this something you could help with or point me in the direction of
a Hive committer who could assist getting this patched?
The test failures above to me don't look like they are related to the patch and
are rather the usual background noise of Hive test failures.
> Configuration not passed to ORC Reader.Options
> ----------------------------------------------
>
> Key: HIVE-19638
> URL: https://issues.apache.org/jira/browse/HIVE-19638
> Project: Hive
> Issue Type: Bug
> Components: Configuration, File Formats, ORC
> Affects Versions: 2.3.0, 2.3.1, 2.3.2
> Reporter: Rentao Wu
> Assignee: Rentao Wu
> Priority: Major
> Attachments: HIVE-19638.patch
>
>
> Configuration is not passed to ORC's Reader.Option in OrcFileInputFormat
> which causes some [ORC
> configurations|https://github.com/apache/orc/blob/master/java/core/src/java/org/apache/orc/Reader.java#L170-L176]
> to not be able to be picked up.
> Related issues:
> For example, the ORC upgrade in Hive 2.3.x changed schema evolution from
> positional to column name matching. A backwards compatibility configuration
> "orc.force.positional.evolution" could be set in ORC Reader.Options by
> [ORC-120|https://issues.apache.org/jira/browse/ORC-120] however it could not
> be picked up resulting in null values when querying ORC tables where the
> column names do not match.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
