[
https://issues.apache.org/jira/browse/ORC-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16055233#comment-16055233
]
ASF GitHub Bot commented on ORC-202:
------------------------------------
Github user omalley commented on the issue:
https://github.com/apache/orc/pull/132
Actually, you can't work around it unless you wrap the enum in a separate
message. The problem is that a reader can't tell the difference from the orc
files produced by ORC 1.4 (no writer set) and an unknown writer (writer mapped
to the default). They will both show up as null. You would need to wrap a
message around the enum to make it work.
> Add enum that encodes which writer wrote a file
> -----------------------------------------------
>
> Key: ORC-202
> URL: https://issues.apache.org/jira/browse/ORC-202
> Project: ORC
> Issue Type: Bug
> Reporter: Owen O'Malley
> Assignee: Owen O'Malley
> Fix For: 1.5.0
>
>
> Add a protobuf enum value in the footer that can encode which writer wrote
> the file:
> * ORC Java Writer
> * ORC C++ Writer
> * Presto Writer
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
