rkhachatryan opened a new pull request #11061: [FLINK-15782] [connectors/jdbc] 
JDBC sink DataStream API
URL: https://github.com/apache/flink/pull/11061
 
 
   ## What is the purpose of the change
   
   1. expose existing sinks at the datastream level (for users, who don’t need 
exactly-once OR for whom upsert is a better option); existing API shouldn’t 
change (mostly table API)
   2. refactor current code for re-use in a new exactly once JDBC sink
   
   
   ## Brief change log
   
   *(for example:)*
     - *minor changes: (case JDBC -> Jdbc; parameter objects)*
     - *extract connection management from `OutputFormat` to new 
`JdbcConnectionProvider`*
     - *replace `Row` with type parameter*
     - *move Table API specific code (like Tuple2<Boolean, T>) to the 
appropriate classes*
     - *refactor tests*
     - *add DataStream API (facade class)*
     - *add docs*
   
   
   ## Verifying this change
   
   This change is already covered by existing tests, such as *JDBCFullTest, 
JDBCOutputFormatTest, JdbcTableOutputFormatTest*.
   
   ## 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): yes
     - 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