mosche commented on issue #25601: URL: https://github.com/apache/beam/issues/25601#issuecomment-1442132121
> Good point about logging. Though, since these classes are already annotated with @Deprecated annotation. Shouldn't they be automatically added to build log? Or you are talking mostly about runtime logs? Of course I'm talking about runtime ... Users won't ever directly interact with AvroSchemaIOProvider. Because of that they are not going to notice a deprecation warning at build time. > IIUC, AvroSchemaIOProvider should be loaded only if it's used in one of it's dependent modules and it doesn't require direct extensions/avro dependency? This isn't as simple ... AvroSchemaIOProvider exposes Avro sources in Beam SQL / xlang in a rather dynamic way to the user. And currently this works as Avro is still part of core. Once removed, the behavior will suddenly break for users that have successfully used it before unless the Avro extension is always added to the expansion service jar :/ -- 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]
