[
https://issues.apache.org/jira/browse/ORC-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16466095#comment-16466095
]
ASF GitHub Bot commented on ORC-360:
------------------------------------
GitHub user omalley opened a pull request:
https://github.com/apache/orc/pull/266
ORC-360. Add Java error checking on the types when reading.
This patch adds a check on the types in the footer to ensure that the type
is properly formed before we start building the tree.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/omalley/orc orc-360
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/orc/pull/266.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #266
----
commit f236cf727cc295e93ae1e2347be60562fff17fa8
Author: Owen O'Malley <omalley@...>
Date: 2018-05-07T16:19:17Z
ORC-360. Add Java error checking on the types when reading.
----
> Implement error checking on subtype fields in Java
> --------------------------------------------------
>
> Key: ORC-360
> URL: https://issues.apache.org/jira/browse/ORC-360
> Project: ORC
> Issue Type: Improvement
> Reporter: Owen O'Malley
> Assignee: Owen O'Malley
> Priority: Major
>
> In ORC-313, we fixed the C++ reader to detect badly formed ORC files with
> respect to the subtype ids. We should add similar checks for the Java reader.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)