DanielLeens commented on PR #10793:
URL: https://github.com/apache/seatunnel/pull/10793#issuecomment-4968421481
Rechecked the same unchanged head `5059f65b4cb3` after the CI / merge-gate
fact changed.
## Runtime path rechecked
```text
JdbcSinkWriter.write(SeaTunnelRow)
-> tryOpen()
-> JdbcOutputFormat.writeRecord(row)
-> addToBatch(row)
-> batchCount++
-> batch size / interval threshold triggers flush()
Flush phase
-> JdbcOutputFormat.flush()
-> attemptFlush()
-> jdbcStatementExecutor.executeBatch()
-> SQLException
-> findSqlExceptions(e)
-> walk the cause chain
-> for each SQLException, walk nextException as well
-> shouldRefreshExecutor(sqlExceptions)
-> SQLState 08xxx means connection failure
-> statement-closed class/message means the current statement
is invalid
-> fallback to connectionProvider.isConnectionValid()
-> updateExecutor(true)
-> close old statements
-> connectionProvider.reestablishConnection()
-> jdbcStatementExecutor.prepareStatements(newConnection)
-> retry attemptFlush()
```
## Merge conclusion
### Conclusion: source blocker cleared from Daniel's side
1. Blocking items
- None from Daniel's source review on this unchanged head.
2. Current gate
- The current CI signal is now green:
https://github.com/apache/seatunnel/actions/runs/24769088687/job/72470581357
- Daniel only has `READ` permission on this repository, so GitHub may still
show earlier review state and a write-capable maintainer may still need to
handle the final approval / dismissal step.
I do not see a reopened code-side blocker from Daniel on the current head.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
