[
https://issues.apache.org/jira/browse/FLINK-12499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-12499:
-----------------------------------
Labels: pull-request-available stale-major (was: pull-request-available)
> JDBCAppendTableSink support retry
> ---------------------------------
>
> Key: FLINK-12499
> URL: https://issues.apache.org/jira/browse/FLINK-12499
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / JDBC
> Reporter: FaxianZhao
> Priority: Major
> Labels: pull-request-available, stale-major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> JDBCOutputFormat will try to restart the whole job while it catch any
> SQLException depend on the Restart Strategy.
> So, the network spike is a terrible thing for streaming job which has a jdbc
> sink. Sometimes one more try will save it.
> Currently, the common case for streaming job delivering messages
> at-least-once is to run idempotent queries, retry more than once is
> acceptable.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
