[ 
https://issues.apache.org/jira/browse/FLINK-41303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18136449#comment-18136449
 ] 

sanqingleo commented on FLINK-41303:
------------------------------------

I would like to work on this. Could a committer please assign this to me?

> Web UI job submission fails with long program arguments
> -------------------------------------------------------
>
>                 Key: FLINK-41303
>                 URL: https://issues.apache.org/jira/browse/FLINK-41303
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / Web Frontend
>    Affects Versions: 1.16.3, 1.17.2, 1.18.1, 1.19.3, 1.20.5
>         Environment: Flink 1.20.1
>            Reporter: sanqingleo
>            Priority: Major
>         Attachments: image-2026-11-02-20-35-13-871.png
>
>
> Hi,
> We use Flink web UI to submit  a new job. And it fails when the program 
> arguments are long.
> The dashboard shows {color:#FF0000}"Unable to load requested file 
> /bad-request."{color}
> {color:#FF0000}!image-2026-11-02-20-35-13-871.png|width=512,height=206!{color}
>  
> JarService#runJob sends the parameters in the JSON body and repeats them as
> query parameters. The REST server limits the request line to{color:#FF0000} 
> 4096 bytes{color}, so
> long arguments exceed the limit even though the body alone would be 
> accepted.We will use json text to express our job, so parameters are so many, 
> and it exceeds 4096 limit.
>  
> I have seen the  source code and commits.{color:#FF0000} I found that the 
> query parameters were added in FLINK-9499 so that the UI also worked 
> with{color}
> {color:#FF0000}the legacy handlers, which ignored the JSON body. Those 
> handlers were removed{color}
> {color:#FF0000}in FLINK-10551, and JarRunHandler prefers the body{color}, so 
> the UI no longer needs
> to send them.
> Sending the same request with the parameters in the body only succeeds.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to