SEZ9 commented on issue #12785:
URL: https://github.com/apache/seatunnel/issues/12785#issuecomment-6282070416
Thanks @hutiefang76 for the compatibility analysis based on `e2957d27afa29`,
and thanks @wgzhao for picking up the implementation.
To summarize where this lands on the original point (unknown job id → HTTP
200 with an id-only body, which naive clients misread as a healthy job):
- Agreed direction: keep HTTP 200 for this release and add the `found:false`
marker only when neither job map contains the id. Successful payloads stay
unchanged, and no `jobStatus` value is fabricated for a job the server cannot
find.
- An immediate or opt-in 404 is deferred to a later decision with its own
migration notice; it is not part of this change.
- `/jobs/checkpoints/{jobId}` remains out of scope.
@wgzhao, your plan matches the accepted scope. Two small additions for the
PR beyond what you listed: please include the old/new response-shape
compatibility coverage for the clients alongside the
running/finished/unknown/expired test matrix, and a release-note entry
recording the additive field. Please link the PR back here when it is up so we
can verify it against this thread.
<!-- streview-comment:1889 -->
--
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]
