[
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-unassigned pull-request-available pull-requests-available
stale-minor (was: auto-unassigned pull-request-available
pull-requests-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.
> 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: Minor
> Labels: auto-unassigned, pull-request-available,
> pull-requests-available, stale-minor
>
> 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.7#820007)
