You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by st96d045 <gi...@git.apache.org> on 2018/06/08 16:23:54 UTC

[GitHub] flink pull request #6142: [FLINK-9499] Allow POST parameters to be used for ...

GitHub user st96d045 opened a pull request:

    https://github.com/apache/flink/pull/6142

    [FLINK-9499] Allow POST parameters to be used for submitting run job …

    Enable users of the REST API to submit requests for running a FLINK job using a POST operation but instead of only using URL query parameters for setting job config parameters, users can now submit job config using POST parameters using a multipart request. This change removes the limitation on long URLs that would otherwise be rejected due to a limit in the URL size.   

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/st96d045/flink master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/6142.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #6142
    
----
commit db7d27bdda9c88b39eed94570fb661be6a54511d
Author: Esteban Serrano <st...@...>
Date:   2018-06-08T16:11:27Z

    [FLINK-9499] Allow POST parameters to be used for submitting run job in REST API

----


---

[GitHub] flink pull request #6142: [FLINK-9499] Allow POST parameters to be used for ...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

    https://github.com/apache/flink/pull/6142


---

[GitHub] flink issue #6142: [FLINK-9499] Allow POST parameters to be used for submitt...

Posted by zentol <gi...@git.apache.org>.
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`.


---