You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Jerry He (JIRA)" <ji...@apache.org> on 2017/06/16 21:51:01 UTC

[jira] [Commented] (HBASE-16247) SparkSQL Avro serialization doesn't handle enums correctly

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

Jerry He commented on HBASE-16247:
----------------------------------

A solution for this JIRA is to add/excise more or all Avro types in the current Spark SQL Avro test cases. (The test coverage is not good now.) As long as the tests are in place, we can detect and prevent current or future incompatible handling if we upgrade Avro. 
Then we can close this JIRA.  What do you think [~busbey]?


> SparkSQL Avro serialization doesn't handle enums correctly
> ----------------------------------------------------------
>
>                 Key: HBASE-16247
>                 URL: https://issues.apache.org/jira/browse/HBASE-16247
>             Project: HBase
>          Issue Type: Bug
>          Components: spark
>    Affects Versions: 2.0.0
>            Reporter: Sean Busbey
>             Fix For: 2.0.0
>
>
> Avro's generic api expects GenericEnumSymbol as the runtime type for instances of fields that are of Avro type ENUM. The Avro 1.7 libraries are lax in some cases for handling this, but the 1.8 libraries are strict. We should proactively fix our serialization.
> (the lax serialization in 1.7 fails for some nested use in unions, see AVRO-997 for details)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)