[
https://issues.apache.org/jira/browse/BEAM-7328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16881442#comment-16881442
]
Romain Manni-Bucau commented on BEAM-7328:
------------------------------------------
Hi,
Is it possible to drop avro from sdk-java-core before that - without package
overlap to keep java >= 8 compatiblity? otherwise upgrading avro in beam means
for users to not upgrade beam since both avro versions are not compatible and
all the industry relies on avro 1.8. Typically
https://lists.apache.org/thread.html/fa3508957fddf19b9ec1546cb1279642f52b807dd5f161e674bdc782@%3Cdev.avro.apache.org%3E
misses S3, Kafka, several metadata reposities solutions and other big data
storages which means upgrading all the ecosystem within less than 5 years
sounds likely not realistic, in particular when it comes to cloud products and
existing storages. However, upgrading beam must be possible (at least for CVE)
so not sure there are much option except doing a release of beam with avro
being an extension/io and no more in core codepath, then only add an avro19
module.
Side note: I know beam loves relocations but it does not work for avro so it is
not an potential workaround.
Romain
> Update Avro to version 1.9.0 in Java SDK
> ----------------------------------------
>
> Key: BEAM-7328
> URL: https://issues.apache.org/jira/browse/BEAM-7328
> Project: Beam
> Issue Type: Improvement
> Components: sdk-java-core
> Reporter: Ismaël Mejía
> Assignee: Ismaël Mejía
> Priority: Minor
>
> Avro 1.9.0 has nice improvements like a reduced size (1MB less) , multiple
> dependencies are not needed anymore (Guava, paranamer, etc) as well as
> cleanups in its APIs to not expose and be tight to Jackson so a worth upgrade.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
