cyq89051127 opened a new pull request #10656: [FLINK-15221][Table SQL / 
API]supporting exactly_once semantic for kafka table api
URL: https://github.com/apache/flink/pull/10656
 
 
   
   ## What is the purpose of the change
   
   *supporting exactly_once semantic for kafka table api*
   
   
   ## Brief change log
   
     - *adding a config "connector.semantic" which indicates the semantic we 
choose using a connector and validator it in Kafkavalidator*
     - *changing the interface by adding semantic parameter of 
createKafkaTableSink of KafkaTableSourceSinkFactoryBase*
     - *adding a meber semantic in KafkaTableSink and Kafka011TableSink*
     - *changing the constructor of KafkaTableSink and Kafka011TableSink*
     - *adding a method to set semantic in Kafka.java*
     - * adding some test methods*
     - * adding the description of semantic of kafka connector in  connect.md 
and connect.zh.md*
   
   
   ## Verifying this change
   
   This change is already covered by existing tests add new added tests in  
KafkaTableSourceSinkFactoryTestBase.
   
   
   ## 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)`: (yes)
     - The serializers: ( no )
     - The runtime per-record code paths (performance sensitive): (no)
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
     - The S3 file system connector: (no)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (yes)
     - If yes, how is the feature documented? (docs)
   
   

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


With regards,
Apache Git Services

Reply via email to