You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@beam.apache.org by "aromanenko-dev (via GitHub)" <gi...@apache.org> on 2023/04/19 14:34:26 UTC

[GitHub] [beam] aromanenko-dev commented on issue #25252: [Task]: [Avro] Stop using Avro in "core"

aromanenko-dev commented on issue #25252:
URL: https://github.com/apache/beam/issues/25252#issuecomment-1514849614

   Hi @bvolpato !
   
   Actually, this task is suspended by the policy that we have for breaking changes in Beam. This one is a part of epic task #24292 where we did quite a lot of progress by introducing a new Avro extension for Java SDK (it was tested and finally should support different Avro versions), transitioning all other modules, that leverages Avro from `core`, to this extension and deprecating Avro-related classed in `core`. Though, we can't just drop an Avro support from core to avoid instant breaking changes, so we need to wait several minor Beam releases (at least three, iirc) and give the user some time to switching and test this new extension.
   
   Do you think you can also start using `extensions/avro` with a more recent Avro version and in this case I think 1.8.2 will be dropped from classpath and won't bring the other out-dated dependencies?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org