Open mukkachaitanya opened 1 year ago
https://github.com/confluentinc/schema-registry/pull/1873 introduced the option to scrub invalid schema names, but the storage connectors can't take advantage of it as it's not an exposed config.
Expose the option to be configured. A lucrative alternative here would be instead to have a passthrough, say formatter.avro.* which let through all of AvroDataConfig options instead of exposing them one by one.
formatter.avro.*
AvroDataConfig
Problem
https://github.com/confluentinc/schema-registry/pull/1873 introduced the option to scrub invalid schema names, but the storage connectors can't take advantage of it as it's not an exposed config.
Solution
Expose the option to be configured. A lucrative alternative here would be instead to have a passthrough, say
formatter.avro.*
which let through all ofAvroDataConfig
options instead of exposing them one by one.Does this solution apply anywhere else?
If yes, where?
Test Strategy
Testing done:
Release Plan