Thanks for pushing this through!
On Wed, Feb 22, 2023 at 10:38 AM Alexey Romanenko <aromanenko....@gmail.com> wrote: > > Hi all, > > As a part of migration the Avro-related classes from Java SDK “core” module > to a dedicated extension [1] (as it was discussed here [2] and here [3]), two > important PRs has been merged [4][5]. Therefore, old Avro-related classes > became deprecated in “core” (still possible to use but not recommended) and > all other Beam modules, that depended on them, switched to use > "extensions/avro” instead. > > We did our best to make this change smooth, compatible and not breaking but, > since it was one of the oldest part of “core”, then everything, > unfortunatelly, is possible and we probably could miss something despite of > all efforts. So, considering that, I’d like to ask community to run any kind > of tests or pipelines that utilise, for example, AvroCoder or AvroUtils or > any other related Avro classes and check if new changes doesn’t break > something and everything works as expected. > > — > Alexey > > [1] https://github.com/apache/beam/issues/24292 > [2] https://lists.apache.org/thread/mz8hvz8dwhd0tzmv2lyobhlz7gtg4gq7 > [3] https://lists.apache.org/thread/47oz1mlwj0orvo1458v5pw5c20bwt08q > [4] https://github.com/apache/beam/pull/24992 > [5] https://github.com/apache/beam/pull/25534 > >
