[
https://issues.apache.org/jira/browse/FLINK-22311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-22311:
-----------------------------------
Labels: pull-request-available stale-major (was: pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Flink JDBC XA connector need to set maxRetries to 0 to properly working
> -----------------------------------------------------------------------
>
> Key: FLINK-22311
> URL: https://issues.apache.org/jira/browse/FLINK-22311
> Project: Flink
> Issue Type: Bug
> Components: Connectors / JDBC
> Affects Versions: 1.13.0
> Reporter: Maciej Bryński
> Priority: Major
> Labels: pull-request-available, stale-major
> Fix For: 1.14.0
>
>
> Hi,
> We're using XA connector from Flink 1.13 in one of our projects and we were
> able to create duplicates of records during write to Oracle.
> The reason was that default MAX_RETRIES in JdbcExecutionOptions is 3 and this
> can cause duplicates in DB.
> I think we should at least mention this in docs or even validate this option
> when creating XA Sink.
> In documentation we're using defaults.
> https://github.com/apache/flink/pull/10847/files#diff-a585e56c997756bb7517ebd2424e5fab5813cee67d8dee3eab6ddd0780aff627R88
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
