[ https://issues.apache.org/jira/browse/FLINK-22239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17324168#comment-17324168 ]
Yuan Mei edited comment on FLINK-22239 at 4/17/21, 5:29 AM: ------------------------------------------------------------ I am reviewing the fix-PR, With FLINK-22311 (a bug report from user using this feature connecting to Oracle), I suggest releasing the feature after we manually test the fix with https://github.com/apache/flink/pull/15627 (along with the failover part) 1. Postgres 2. MySQL 3. Oracle with proper documentation. was (Author: ym): I am reviewing the fix-PR, With FLINK-22311, I suggest releasing the feature after we manually test the fix with https://github.com/apache/flink/pull/15627 (along with the failover part) 1. Postgres 2. MySQL 3. Oracle with proper documentation. > Improve support for JdbcXaSinkFunction > -------------------------------------- > > Key: FLINK-22239 > URL: https://issues.apache.org/jira/browse/FLINK-22239 > Project: Flink > Issue Type: Bug > Components: Connectors / JDBC > Reporter: Yuan Mei > Assignee: Roman Khachatryan > Priority: Major > Labels: pull-request-available > Fix For: 1.13.0 > > > JdbcXaSinkFunction uses Xa protocol/interface to implement exactly-once > guarantee (within each subtask partition). > Xa is a protocol/interface designed for two-phase commit of distributed DBS > (RMs). > XA guarantees that transactional updates are committed in all of the > participating databases, or are fully rolled back out of all of the > databases, reverting to the state prior to the start of the transaction. > Hence some of the dbs that support XA treats XA transaction as global trans, > and some of them does not support multiple global trans (per connection) at a > time, MYSQL for example (see FLINK-21743). > This ticket is a follow-up to address such limitations. -- This message was sent by Atlassian Jira (v8.3.4#803005)