hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lefty Leverenz (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-15929) Fix HiveDecimalWritable to be compatible with Hive 2.1
Date Wed, 08 Mar 2017 00:59:38 GMT

    [ https://issues.apache.org/jira/browse/HIVE-15929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900500#comment-15900500
] 

Lefty Leverenz commented on HIVE-15929:
---------------------------------------

Status nudge:  This was committed to master on Feb. 16 with commits 74c50452c5c644a3898bce2738ee040e625caa01,
a9c429e637cf366b90a87cc5c1f3c2b4e60ae0c8, and e732aa27efec014302af41fb77c0b1c5197c4b90.

[~owen.omalley], please update the status and fix version.

> 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
>         Attachments: HIVE-15929.patch
>
>
> 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)

Mime
View raw message