You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Marcelo Vanzin (JIRA)" <ji...@apache.org> on 2018/09/05 20:11:00 UTC

[jira] [Commented] (SPARK-24771) Upgrade AVRO version from 1.7.7 to 1.8

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

Marcelo Vanzin commented on SPARK-24771:
----------------------------------------

I ran a couple of our tests that exercise avro and they worked fine with 2.4. They're not comprehensive, though:

- one uses the data source to read / write data, and that shouldn't really be affected by the change
- the other uses {{GenericRecord}}, so it doesn't really use generated Avro types.

So I don't really have a test that can say for sure what will break when you use generated types, which is the part that is explicitly called as being changed in 1.8. I still think it would be good to try to shade Avro 1.8 in the data source, and not expose it to other parts of Spark, but otherwise a strongly worded release note might be ok, although not optimal.

> Upgrade AVRO version from 1.7.7 to 1.8
> --------------------------------------
>
>                 Key: SPARK-24771
>                 URL: https://issues.apache.org/jira/browse/SPARK-24771
>             Project: Spark
>          Issue Type: Sub-task
>          Components: SQL
>    Affects Versions: 2.4.0
>            Reporter: Gengliang Wang
>            Assignee: Gengliang Wang
>            Priority: Major
>              Labels: release-notes
>             Fix For: 2.4.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org