You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/07/13 07:42:00 UTC

[jira] [Commented] (FLINK-9499) Allow REST API for running a job to provide job configuration as body of POST request

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

ASF GitHub Bot commented on FLINK-9499:
---------------------------------------

Github user zentol commented on the issue:

    https://github.com/apache/flink/pull/6142
  
    Sorry that I'm addressing this PR so late.
    
    Unfortunately I have to reject it as we've established that any non-path/query parameters are submitted as a simple JSON payload instead, like the `SavepointTriggerRequestBody`.


> Allow REST API for running a job to provide job configuration as body of POST request
> -------------------------------------------------------------------------------------
>
>                 Key: FLINK-9499
>                 URL: https://issues.apache.org/jira/browse/FLINK-9499
>             Project: Flink
>          Issue Type: Improvement
>          Components: REST
>    Affects Versions: 1.3.2
>            Reporter: Esteban Serrano
>            Assignee: Esteban Serrano
>            Priority: Minor
>              Labels: pull-request-available
>
> Based on [this|https://ci.apache.org/projects/flink/flink-docs-release-1.3/monitoring/rest_api.html#submitting-programs] documentation, the REST API provides a way to submit a request for running a Flink job. The POST request must include the job configuration information as query parameters using the documented parameter names ("program-args", "entry-class", "parallelism", etc.) 
> Depending on the job parameters, the full URL for the POST request can reach a size that is over the maximum size (currently at 4096 bytes) of what is allowed by the configuration of Netty. To overcome this, it would be useful to allow users to provide the job configuration not only as query parameters but also as POST parameters. 
> For the most part, it is the "program-args" parameter that can make the URL grow in size based on the needs of the developer and the job. All other attributes should be pretty constant.  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)