[
https://issues.apache.org/jira/browse/FLINK-22018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-22018:
-----------------------------------
Labels: auto-deprioritized-minor auto-unassigned pull-request-available
pull-requests-available (was: auto-unassigned pull-request-available
pull-requests-available stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> 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
> Priority: Not a Priority
> Labels: auto-deprioritized-minor, auto-unassigned,
> pull-request-available, pull-requests-available
>
> 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.20.10#820010)
