[
https://issues.apache.org/jira/browse/FLINK-22239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17319920#comment-17319920
]
Yuan Mei commented on FLINK-22239:
----------------------------------
Possible solution:
Maintain a pool of connections to DB per sink task to simulate multiple xa
transactions per sink task
> Improve support for JdbcXaSinkFunction
> --------------------------------------
>
> Key: FLINK-22239
> URL: https://issues.apache.org/jira/browse/FLINK-22239
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / JDBC
> Reporter: Yuan Mei
> Priority: Major
> Fix For: 1.14.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)
