Hi Flink community, Could a committer familiar with the Web UI / runtime-web component help review two PRs related to job submission, and advise on the scope of a related Show Plan fix?
Our workflow requires submitting some jobs through the Flink Web UI, including jobs with long program arguments. We currently use Flink 1.x and are also evaluating Flink 2.x. 1. Long program arguments — FLINK-41303 / PR #29764 The Web UI sends job submission parameters in both the JSON request body and the URL query string. With long arguments, the request line exceeds the REST server’s limit, causing submission to fail with: “Unable to load requested file /bad-request.” PR #29764 targets release-1.20 and removes the redundant query parameters, keeping the parameters in the request body. The CI bot reports success. Jira: FLINK-41303 · PR #29764 2. Program argument compatibility with Flink 2.x — FLINK-39310 / PR #27825 This related issue concerns the Web UI’s argument format: it needs to send programArgsList in the JSON request body to match the Flink 2.x REST API. PR #27825 targets master and updates both job submission and plan requests. It was opened on March 25 and remains open. Other users have also reported being affected, with one team switching to REST scripts after upgrading to Flink 2.x. Jira: FLINK-39310 · PR #27825 3. Show Plan with long arguments — include in #29764 or handle separately? As noted in PR #29764, Show Plan has a similar issue: getPlan() in the 1.20 Web UI still sends program arguments as GET query parameters, which can encounter the same request-line length limit. The current PR only changes job submission, so plan preview remains outside its scope. The Flink 1.20 REST API already supports POST /jars/:jarid/plan and recommends passing arguments in the JSON request body. Switching the Web UI’s plan request to this format appears to be a suitable approach. Flink 1.20 REST API documentation Would the community prefer extending PR #29764 to cover Show Plan as well, or keeping it focused on job submission and opening a separate Jira issue and PR for Show Plan? For context, PR #27825 already includes a GET-to-POST change for plan requests on master; this scope question concerns the release-1.20 fix. Relevant earlier dev discussions The earlier REST API discussions also appear relevant: • FLIP-337: Chesnay explicitly noted that the Web UI was using programArgs and would need to be updated to the new parameter. July 18, 2023 discussion • FLIP-350: Proposed removing query parameters from the Jar handlers in favor of request-body parameters, citing argument escaping problems and consistency. July 24, 2023 discussion We would appreciate help reviewing these PRs and clarifying any remaining technical or contribution-process requirements. Guidance on the Show Plan scope and applicable release branches would also be helpful. Please let us know what additional reproduction details or validation would help move these forward. Thank you for your time and help! Best Regards, Liu Rongtong
