Abacn commented on PR #25602:
URL: https://github.com/apache/beam/pull/25602#issuecomment-1441749252

   > @Abacn Thanks for fixing this but I doubt that we can simply remove it for 
now. IINM, if user code depends only on `beam-sdks-java-core` module and not on 
`beam-sdks-java-extensions-avro` (which is rather default case for now since 
this extension is quite new) and it leverages `AvroSchemaIOProvider` then it 
will fail in runtime. That is why I preferred to keep two versions of this 
loader for a period of deprecation. CC: @mosche
   
   Hi @aromanenko-dev thanks for the comment. Yes this is the case. For users 
only using released artifacts it does not have problem because the expansion 
service jar is a shadowJar:
   
https://mvnrepository.com/artifact/org.apache.beam/beam-sdks-java-extensions-schemaio-expansion-service/2.45.0


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to