nielifeng commented on issue #10781: URL: https://github.com/apache/seatunnel/issues/10781#issuecomment-5140133731
Verified this against a current `dev` deployment at commit `7e25769` (SeaTunnel `3.0.0-SNAPSHOT`, 3 Masters + 3 Workers). I submitted a minimal invalid HOCON job through `POST /submit-job?format=hocon`: `FakeSource` had `row.num = 1` but intentionally omitted both `schema` and `tables_configs`. Observed result: - HTTP status: `500` - response `status`: `fail` - no `jobId` was created - the response message contained the top-level `FactoryException` and the nested `Caused by: OptionValidationException` - the nested message explicitly identified the missing `tables_configs` / `schema` exclusive-option constraint Post-check: all three Masters reported commit `7e25769`, 3 Workers, 24/24 free slots, and 0 running/pending/failed jobs. This confirms that the root cause is visible in the REST response on current `dev`, consistent with the `ExceptionUtils.getStackTrace(e)` change from #10696. I do not see a remaining dev regression for the behavior reported here; this issue looks ready to mark fixed-in-dev/close. The released 2.3.13 behavior remains the version-specific limitation described above. -- 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]
