It sounds like there's a consensus around making Beam core work with either Avro 1.8 or 1.9. It looks like +Tomo Suzuki <suzt...@google.com> actually accomplished this already back in January for BEAM-9144 [1] and a user has run pipelines on Dataflow with Avro 1.9.
Would we need to do anything else to unblock using Confluent Schema Registry 5.5 (BEAM-9330 [2])? [1] https://issues.apache.org/jira/browse/BEAM-9144 [2] https://issues.apache.org/jira/browse/BEAM-9330 On Tue, Oct 13, 2020 at 8:34 AM Piotr Szuberski <piotr.szuber...@polidea.com> wrote: > We are working on IOs dependencies, most of them are pending in PRs right > now. > > Any further thoughts/decisions on moving Avro out of Beam core? > > On 2020/09/21 14:56:16, Cristian Constantinescu <zei...@gmail.com> wrote: > > All the proposed solutions seem reasonable. I'm not sure if one has an > edge > > over the other. I guess it depends on how cautiously the community would > > like to move. > > > > Maybe it's just my impression, but it seems to me that there are a few > > changes that are held back for the sake of backwards compatibility. If > this > > is truly the case, maybe we can start thinking about the next major > version > > of Beam where: > > - the dependency report email (Beam Dependency Check Report (2020-09-21)) > > can be tackled. There are quite a few deps in there that need to be > > updated. I'm sure there will be more breaking changes. >
