[
https://issues.apache.org/jira/browse/FLINK-22018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17322783#comment-17322783
]
Flink Jira Bot commented on FLINK-22018:
----------------------------------------
This issue is assigned but has not received an update in 7 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> JdbcBatchingOutputFormat should not log SQLException on retry
> -------------------------------------------------------------
>
> Key: FLINK-22018
> URL: https://issues.apache.org/jira/browse/FLINK-22018
> Project: Flink
> Issue Type: Bug
> Components: Connectors / JDBC
> Affects Versions: 1.12.1
> Reporter: Nicolas Deslandes
> Assignee: Nicolas Deslandes
> Priority: Minor
> Labels: pull-request-available, pull-requests-available,
> stale-assigned
>
> JdbcBatchingOutputFormat contains a retry mechanism on potential SQLException
> (usually because of lost connection).
> The retry works perfectly but the exception stack trace (usually useless) is
> logged at ERROR level on every retry.
> I am proposing to just log the retry attempt as a warning
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
