[ https://issues.apache.org/jira/browse/HIVE-19638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16780522#comment-16780522 ]
Mass Dosage commented on HIVE-19638: ------------------------------------ OK, so from what I can tell this is about being able to pass a conf variable into the ORC Reader which allows one to override certain ORC properties. I don't think we need an ORC committer to review per se but if you think that's the best path I guess I could ask? In the meantime should I create a properly named patch file for the 2.3.x branch? Could we get the current patch merged into master (assuming it applies cleanly, I haven't checked). > 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)