Pavan-249 opened a new pull request, #18893: URL: https://github.com/apache/hudi/pull/18893
### Describe the issue this Pull Request addresses Part of #14281 (RFC-99 #14263) ### Summary and Changelog Migrate all schema providers in hudi-utilities from Avro Schema to HoodieSchema, plus the post-processor wrapper. Providers migrated to expose getSourceHoodieSchema() / getTargetHoodieSchema(), with the deprecated Avro getSourceSchema() / getTargetSchema() retained as thin bridges for backward compatibility: - FilebasedSchemaProvider - HiveSchemaProvider - SchemaRegistryProvider (also adds the getTargetSchema() bridge, since it reads a distinct target registry URL and must not fall through to the source schema) - SimpleSchemaProvider - JdbcbasedSchemaProvider - ProtoClassBasedSchemaProvider - RowBasedSchemaProvider SchemaProviderWithPostProcessor: HoodieSchema getters are now the primary implementation; the Avro getters are kept as delegating bridges, since this wrapper is the pipeline-wide compatibility boundary for callers still on the Avro API (e.g. BootstrapExecutorUtils, WriterContext). Tests added: TestSimpleSchemaProvider, TestRowBasedSchemaProvider. hudi-sync: no migration needed. There are zero org.apache.avro.Schema usages across the module (it operates on Parquet MessageType, not Avro Schema). ### Impact None. RFC-99 guarantees binary compatibility with Avro in this phase. No on-disk or serialization formats change. ### Risk Level Low. Follows the established RFC-99 pattern. Built locally (hudi-utilities + dependencies) and the schema provider tests pass with 0 checkstyle violations. ### Documentation Update None ### Contributor's checklist - [x] Read through contributor's guide - [x] Enough context is provided in the sections above - [x] Adequate tests were added if applicable -- 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]
