[
https://issues.apache.org/jira/browse/HIVE-15929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15868516#comment-15868516
]
ASF GitHub Bot commented on HIVE-15929:
---------------------------------------
GitHub user omalley opened a pull request:
https://github.com/apache/hive/pull/149
HIVE-15929. Fix HiveDecimalWritable compatibility with Hive 2.1.
This allows Hive 2.1 to work without getting an exception.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/omalley/hive hive-15929
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/hive/pull/149.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 #149
----
commit aeaf8dc2d8ef0adf0c6fdf216da89453a807459a
Author: Owen O'Malley <[email protected]>
Date: 2017-02-15T01:25:46Z
HIVE-15929. Fix HiveDecimalWritable compatibility with Hive 2.1.
----
> Fix HiveDecimalWritable to be compatible with Hive 2.1
> ------------------------------------------------------
>
> Key: HIVE-15929
> URL: https://issues.apache.org/jira/browse/HIVE-15929
> Project: Hive
> Issue Type: Bug
> Reporter: Owen O'Malley
> Assignee: Owen O'Malley
>
> HIVE-15335 broke compatibility with Hive 2.1 by making
> HiveDecimalWritable.getInternalStorate() throw an exception when called on an
> unset value. It is easy to instead return an empty array, which will allow
> the old code to allocate a new array.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
