davidzollo opened a new pull request, #11560: URL: https://github.com/apache/seatunnel/pull/11560
## Purpose This PR continues and supersedes #11116. It preserves @ThorneANN as the author of the original resource-cleanup commit and rebases the work onto the current `dev` head. The Fluss sink writer previously had three lifecycle problems: - partially initialized connections or tables could leak when writer construction failed; - `close()` stopped after the first failure and could skip closing the connection; - INFO logging printed the complete Fluss configuration, including user-provided client settings. ## Changes - close partially initialized resources when construction fails; - preserve the initialization failure as the primary exception and attach cleanup failures as suppressed exceptions; - always attempt to close both the table and connection, preserving failures in close order; - pass the stable Fluss connector identity to `CommonError.closeFailed`; - log only `bootstrap.servers` instead of the full client configuration; - add focused tests for successful shutdown, constructor-failure cleanup, and dual close-failure aggregation. ## Compatibility No configuration option, default value, public API, serialization format, or connector registration changes. The change only strengthens failure cleanup, error reporting, and log redaction. ## Verification - `./mvnw -f seatunnel-connectors-v2/connector-fluss/pom.xml spotless:apply -nsu -Dmaven.gitcommitid.skip=true` — passed - `./mvnw -f seatunnel-connectors-v2/connector-fluss/pom.xml spotless:check -nsu -Dmaven.gitcommitid.skip=true` — passed - Local compile, unit tests, E2E, Docker, and service startup were not run under the SeaTunnel local-verification policy; the current PR head GitHub CI is the functional verification gate. -- 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]
