o version as is.
As stated above, I think it's safer to make the avroless version a new
target initially than change core.
> At the same time, extracting Avro as extension in a backwards compatible way
> seems to be the right path forward long term together with a well
> communica
, I think it's safer to make the avroless version a new
target initially than change core.
> At the same time, extracting Avro as extension in a backwards compatible way
> seems to be the right path forward long term together with a well
> communicated deprecation plan.
>
>
>
&g
the
> default Avro version as is.
As stated above, I think it's safer to make the avroless version a new
target initially than change core.
> At the same time, extracting Avro as extension in a backwards compatible way
> seems to be the right path forward long term together with a well
&g
To finally make progress on this topic, I’d suggest starting off with
>> supporting multiple different Avro versions in core (2) but to keep the
>> default Avro version as is.
>>
>> At the same time, extracting Avro as extension in a backwards compatible way
>> s
rds compatible
> *way seems to be the right path forward long term together with a well
> communicated deprecation plan.
>
>
>
> Best,
>
> Moritz
>
>
>
>
>
> *From: *Brian Hulette
> *Date: *Thursday, 12. May 2022 at 23:21
> *To: *dev
> *Subject: *Re:
, 12. May 2022 at 23:21
To: dev
Subject: Re: [DISCUSS] Next steps for update of Avro dependency in Beam
Regarding Option (3) "but keep and shade Avro for “core” needs as v.1.8.2
(still have an issue with CVEs)" Do we actually need to keep avro in core for
any reason? I thought we only had
Hi,
Thanks Alexey for bringing this topic up.
I'd be in favor of 3
Best
Etienne
Le 12/05/2022 à 23:21, Brian Hulette a écrit :
Regarding Option (3) "but keep and shade Avro for “core” needs as
v.1.8.2 (still have an issue with CVEs)"
Do we actually need to keep avro in core for any reason?
Hi everyone,
Sorry in advance for a long email.
TL;DR: Let’s discuss the next steps to update Avro dependency in Beam.
I’d like to come back to this old and quite sensitive topic here which is
Apache Avro version update in Beam. Along the time, we already had several
discussions on this (for e
