zhangshenghang commented on PR #10306: URL: https://github.com/apache/seatunnel/pull/10306#issuecomment-5230812129
Addressed the latest maintainer blockers in head `da827df05222dcb230c96603fb3894da279c7fbd`:\n\n- Kept the default JDBC path unchanged: SQLState `22xxx`/`23xxx` now only fails fast into row-error handling when a `RowErrorCollector` is attached; otherwise the normal `max_retries` path remains.\n- Reworked terminal outcome retention so only active in-flight probes are remembered after drain, instead of retaining all successful rows.\n- Clarified threshold-counter semantics in docs and added focused action/stage-scope coverage.\n- Documented the `MultiTableState.serialVersionUID` source in the PR description and kept the old-shape restore test.\n\nLocal verification run:\n\n- `./mvnw spotless:apply`\n- `git diff --check`\n- `./mvnw -pl seatunnel-api -DskipIT -Dtest=MultiTableSinkWriterTest -DfailIfNoTests=false test`\n- `./mvnw -pl seatunnel-connectors-v2/connector-jdbc -DskipIT -Dtest=JdbcOutputFormatTest -DfailIfNoTests=false test`\n- `./mvnw -pl seatunnel-engine/seatunnel-engine-s erver -DskipIT -Dtest=ErrorHandlerTest,SinkFlowLifeCycleErrorOutcomeTest -DfailIfNoTests=false -Dmaven.compiler.useIncrementalCompilation=false test`\n\nThe current-head GitHub checks have started; waiting for the new Build result now. -- 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]
