danny0405 opened a new pull request #12919:
URL: https://github.com/apache/flink/pull/12919


   … data from Kafka
   
   ## What is the purpose of the change
   
   Supports read/write with SQL using schema registry avro format.
   
   **The format details**
   
   _The factory identifier (or format id)_
   
   There are 2 candidates now ~
   
   `avro-sr`: the pattern borrowed from KSQL JSON_SR format [1]
   `avro-confluent`: the pattern borrowed from Clickhouse AvroConfluent [2]
   
   Personally i would prefer avro-sr because it is more concise and the 
confluent is a company name which i think is not that suitable for a format 
name.
   
   **The format attributes**
   
   Options | required | Remark
   -- | -- | --
   schema-string | true | avro schema string used for (de)serialization
   schema-registry.url | true | URL to connect to schema registry service
   schema-registry.subject | false | Subject name to write to the Schema 
Registry service, required for sink
   
   
   ## Brief change log
   
     - Add `avro-sr` read/write row data format
     - Add tests
   
   
   ## Verifying this change
   
   Added tests.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): no
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: no
     - The serializers: no
     - The runtime per-record code paths (performance sensitive): no
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: no
     - The S3 file system connector: (yes / no / don't know) no
   
   ## Documentation
   
     - Does this pull request introduce a new feature? yes
     - If yes, how is the feature documented? not documented
   


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

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


Reply via email to