You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Michael Malak (JIRA)" <ji...@apache.org> on 2013/02/14 18:49:13 UTC

[jira] [Commented] (HIVE-3528) Avro SerDe doesn't handle serializing Nullable types that require access to a Schema

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

Michael Malak commented on HIVE-3528:
-------------------------------------

I've tried the latest Avro SerDe from GitHub, and it allows me to write NULLs with a simple schema, but not with anything involving STRUCTs.  If a STRUCT contains NULLable fields, or the entire STRUCT is NULLable (optional), Hive throws exceptions.  Should I create new JIRA item(s)?
                
> Avro SerDe doesn't handle serializing Nullable types that require access to a Schema
> ------------------------------------------------------------------------------------
>
>                 Key: HIVE-3528
>                 URL: https://issues.apache.org/jira/browse/HIVE-3528
>             Project: Hive
>          Issue Type: Bug
>          Components: Serializers/Deserializers
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>              Labels: avro
>             Fix For: 0.11.0
>
>         Attachments: HIVE-3528.1.patch.txt, HIVE-3528.2.patch.txt
>
>
> Deserialization properly handles hiding Nullable Avro types, including complex types like record, map, array, etc. However, when Serialization attempts to write out these types it erroneously makes use of the UNION schema that contains NULL and the other type.
> This results in Schema mis-match errors for Record, Array, Enum, Fixed, and Bytes.
> Here's a [review board of unit tests that express the problem|https://reviews.apache.org/r/7431/], as well as one that supports the case that it's only when the schema is needed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira