[
https://issues.apache.org/jira/browse/BEAM-8388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17016510#comment-17016510
]
Aaron Dixon commented on BEAM-8388:
-----------------------------------
[~suztomo] 2.17.0 references a class `TimestampConversion` that is only in Avro
1.8.x. It appears that the PR you referenced (that didn't get merged) shows the
required change away from using `TimestampConversion`:
[https://github.com/apache/beam/pull/9779/files]
Regarding Ken's comment – wouldn't shading Avro be an apropos solution? This is
a very common approach in dealing with situations like this. (See
[https://maven.apache.org/plugins/maven-shade-plugin/]) In this way Beam could
(internally, for AvroCoder, etc) use whichever Avro version it prefers while
clients could then have direct dependencies on any Avro version and not
conflict with Beam's?
> 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)
