[
https://issues.apache.org/jira/browse/FLINK-23876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Khachatryan resolved FLINK-23876.
---------------------------------------
Resolution: Fixed
Merged into master (1.14) as ad104eecaca9cb0189712a6a9044a92bbbddc931
> Remove limitation about JDBC exactly once sink about multiple connections per
> transaction
> ------------------------------------------------------------------------------------------
>
> Key: FLINK-23876
> URL: https://issues.apache.org/jira/browse/FLINK-23876
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / JDBC, Documentation
> Affects Versions: 1.14.0
> Reporter: Roman Khachatryan
> Assignee: Roman Khachatryan
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 1.14.0
>
>
> [https://ci.apache.org/projects/flink/flink-docs-release-1.13/docs/connectors/datastream/jdbc/#jdbcsinkexactlyoncesink]
> says:
> {quote}Attention: In 1.13, Flink JDBC sink does not support exactly-once mode
> with MySQL or other databases that do not support multiple XA transaction per
> connection. We will improve the support in FLINK-22239.
> {quote}
>
> In FLINK-22239, connection pooling was added so this limitation doesn't apply
> anymore.
> So this should be removed or replaced with a list of databases.
> Connection pooling should be enabled explicitly: should list DBs requiring
> this (mysql, postgres) and give an example code.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
