DanielLeens commented on issue #5830: URL: https://github.com/apache/seatunnel/issues/5830#issuecomment-5509300626
Thanks, @Adarsh-Me. The report evidence is from 2.3.3 and the legacy Hazelcast REST path with the Disruptor queue. In current dev, a normal stop request routes through cancelJob, and CoordinatorService integration coverage asserts that the final state becomes CANCELED. Please do not change the terminal status path from the historical report alone. First reproduce it on current dev with the exact queue type, REST endpoint and JSON payload, force and savepoint flags, and the transition from the stop request to the final job state. If it still reproduces, add that focused regression before proposing implementation changes. -- 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]
