[jira] [Updated] (FLINK-12499) JDBCAppendTableSink support retry

["Flink Jira Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-12499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Flink Jira Bot updated FLINK-12499:
-----------------------------------
    Labels: auto-deprioritized-major pull-request-available stale-minor  (was: auto-deprioritized-major 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 Minor but is unassigned and neither itself nor its Sub-Tasks have been updated for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is still Minor, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.


> 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: Minor
>              Labels: auto-deprioritized-major, pull-request-available, stale-minor
>          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.20.1#820001)