JAEKWANG97 opened a new issue, #13132:
URL: https://github.com/apache/seatunnel/issues/13132

   ## Problem
   
   `TransformFlowLifeCycle.open()` catches an exception from `t.open()`, logs 
it, and continues the loop. It can return normally even though a transform 
failed to initialize. Later transforms can still open, and startup failure is 
hidden from the caller.
   
   This prevents transforms from reliably requiring successful initialization 
before row processing.
   
   ## Expected behavior
   
   - Propagate a transform-open failure to the owning task and stop startup.
   - Prevent row processing after failed initialization, including jobs with no 
input rows.
   - Clean up resources allocated during startup through their existing owners. 
Preserve the initialization failure if cleanup also fails.
   - Keep successful startup and existing transform interfaces compatible.
   
   ## Suggested validation
   
   Extend existing engine lifecycle tests with a transform whose `open()` 
throws. Cover first, middle, and last positions; assert failure propagation and 
no subsequent row processing. Also check successful startup, error-handling 
wrappers, partial-resource cleanup, and cleanup failures.
   
   The catch-and-continue path was confirmed by source inspection. No runtime 
reproduction or Maven/E2E result is claimed here.
   
   ## Scope and references
   
   This is the startup-failure prerequisite requested for STIP-44. Task-wide 
teardown is tracked separately in #12231 and PR #12391.
   
   - Review request: 
https://github.com/apache/seatunnel/issues/13099#issuecomment-6594148302
   - Startup loop at inspected dev commit: 
https://github.com/apache/seatunnel/blob/2eccdc412a6dce28fe0f80b5d26973737fa876d7/seatunnel-engine/seatunnel-engine-server/src/main/java/org/apache/seatunnel/engine/server/task/flow/TransformFlowLifeCycle.java#L126
   - Separate task teardown work: https://github.com/apache/seatunnel/pull/12391
   


-- 
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]

Reply via email to