jherico opened a new pull request #17360:
URL: https://github.com/apache/flink/pull/17360


   Fix for https://issues.apache.org/jira/browse/FLINK-24379
   
   ## What is the purpose of the change
   
   Add missing components required to use the AWS Glue Schema registry in Table 
connectors.
   
   ## Brief change log
   
     - Added GluSchemaRegistryAvroFormatFactory class and reference to same in 
`flink-formats/flink-avro-glue-schema-registry/src/main/resources/META-INF/services/org.apache.flink.table.factories.Factory`
     - 
   
   ## Verifying this change
   
   This change added tests and can be verified as follows:
   
     - Added test class 
org.apache.flink.formats.avro.glue.schema.registry.GlueSchemaRegistryAvroDeserializationSchemaTest
 based off 
org.apache.flink.formats.avro.registry.confluent.RegistryAvroFormatFactoryTest
     - Verified that the test passed after some work correcting the options 
naming.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): yes
       - Adds internal dependency from flink-avro-glue-schema-registry to the 
table API jars
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: no public API changed
     - The serializers: don't know
     - The runtime per-record code paths (performance sensitive): no
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
     - The S3 file system connector: no
   
   ## Documentation
   
     - Does this pull request introduce a new feature? No?  It's adding an 
existing feature that is present in all the other Avro formats to the AWS Glue 
Avro format
     - If yes, how is the feature documented? JavaDocs, tweaked from the 
similar docs in RegistryAvroFormatFactory
   


-- 
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