DanielLeens commented on issue #12785: URL: https://github.com/apache/seatunnel/issues/12785#issuecomment-6191897382
Classification: I / Zeta REST API contract. The current server code does return a `200` body containing only `jobId` when neither the running nor finished-job maps contain the requested id, so the ambiguity is real. I also verified current consumers in the engine UI, the Python SDK, and the CLI; a status-code change would therefore be an API compatibility decision, not a narrow bug fix. Please do not open a 404 implementation PR yet. First post a short compatibility proposal that records the behavior of those consumers and user-facing REST clients, evaluates an explicit 200 response versus a staged/flagged 404, and specifies EN/ZH API documentation plus migration/release-note treatment. The checkpoint endpoint has related ambiguity, but should remain a separately scoped follow-up unless the proposal proves both contracts can evolve together safely. No exact open PR currently covers this decision. -- 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]
