[
https://issues.apache.org/jira/browse/ORC-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16518739#comment-16518739
]
ASF GitHub Bot commented on ORC-380:
------------------------------------
GitHub user mmccline opened a pull request:
https://github.com/apache/orc/pull/286
ORC-380: Add isOnlyImplicitConversion boolean function to SchemaEvolu…
…tion
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mmccline/orc master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/orc/pull/286.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 #286
----
commit 6a24f3913015c703f62de3faf8aed723691dad50
Author: Matt McCline <mmccline@...>
Date: 2018-06-21T00:10:17Z
ORC-380: Add isOnlyImplicitConversion boolean function to SchemaEvolution
----
> Add isOnlyImplicitConversion boolean function to SchemaEvolution
> ----------------------------------------------------------------
>
> Key: ORC-380
> URL: https://issues.apache.org/jira/browse/ORC-380
> Project: ORC
> Issue Type: Bug
> Components: ORCv2
> Reporter: Matt McCline
> Assignee: Matt McCline
> Priority: Critical
>
> The current hasConversion boolean function returns true if there is *any*
> conversion between the reader and file schemas. Prasanth pointed out this is
> too strict for the check I'm adding in HIVE-19951: "Vectorization: Need to
> disable encoded LLAP I/O for ORC when there is data type conversion (Schema
> Evolution)". He points out that integer type widening and float to double
> ought to be allowed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)