DanielLeens commented on issue #13132: URL: https://github.com/apache/seatunnel/issues/13132#issuecomment-6657732821
Thanks for isolating this lifecycle boundary. I checked current `dev` (`3cb9efc2a15223372bc1f87a92d027845a8ca800`): `TransformFlowLifeCycle.open()` still catches a transform `open()` exception, logs it, and continues the loop. That violates the startup contract described here, so a focused fix is welcome. Please keep this separate from the task-wide cleanup work in #12231 / #12391 and make the PR prove the following behavior: 1. The original initialization failure reaches the owning task, and no later transform is opened after that failure. 2. Rows cannot be processed after unsuccessful initialization, including an input that produces no rows. 3. Already-opened transform resources are cleaned through their existing owner without replacing the initialization failure when cleanup also fails. 4. Existing successful startup and error-handling-wrapper behavior remain unchanged. Please add focused existing lifecycle-test coverage for first, middle, and last failing transforms, partial cleanup, cleanup failure, and the successful control case. That gives the STIP-44 follow-up a clear, independently reviewable prerequisite. -- 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]
