You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Aaron Dixon (Jira)" <ji...@apache.org> on 2020/01/16 02:46:00 UTC

[jira] [Commented] (BEAM-8388) Update Avro to 1.9.1 from 1.8.2

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

Aaron Dixon commented on BEAM-8388:
-----------------------------------

I'd like to add a vote to this ticket with some context:

My org must use Avro 1.9.x (due to some Avro schema resolution issues resolved in 1.9.x) so downgrading Avro is not possible for us.

Beam 2.16.0 is compatible with our usage of Avro 1.9.x – but upgrading to 2.17.0 we are broken as 2.17.0 links to Java classes in Avro 1.8.x that are not available in 1.9.x.

So we are stuck on 2.16.0 until Beam can eliminate the hard dependency on 1.8.x. I see that there is [this now closed PR|[https://github.com/apache/beam/pull/9779]] that hoped to address this.

Would shading Avro (maven-shade-plugin) be an option for Beam here - so that clients could use their own version of Avro. (For context, for us, we use Avro to parse events from a KafkaIO source; it would be perfectly fine if Beam internally used a shaded 1.8.x version to do its own coding/serde.)

> Update Avro to 1.9.1 from 1.8.2
> -------------------------------
>
>                 Key: BEAM-8388
>                 URL: https://issues.apache.org/jira/browse/BEAM-8388
>             Project: Beam
>          Issue Type: Improvement
>          Components: io-java-avro
>            Reporter: Jordanna Chord
>            Assignee: Jordanna Chord
>            Priority: Major
>   Original Estimate: 24h
>          Time Spent: 3h 20m
>  Remaining Estimate: 20h 40m
>
> Update build dependency to 1.9.1



--
This message was sent by Atlassian Jira
(v8.3.4#803005)