You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (JIRA)" <ji...@apache.org> on 2018/10/10 09:17:00 UTC

[jira] [Assigned] (FLINK-10520) Job save points REST API fails unless parameters are specified

     [ https://issues.apache.org/jira/browse/FLINK-10520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chesnay Schepler reassigned FLINK-10520:
----------------------------------------

    Assignee: Chesnay Schepler

> Job save points REST API fails unless parameters are specified
> --------------------------------------------------------------
>
>                 Key: FLINK-10520
>                 URL: https://issues.apache.org/jira/browse/FLINK-10520
>             Project: Flink
>          Issue Type: Bug
>          Components: REST
>    Affects Versions: 1.6.1
>            Reporter: Elias Levy
>            Assignee: Chesnay Schepler
>            Priority: Minor
>
> The new REST API POST endpoint, {{/jobs/:jobid/savepoints}}, returns an error unless the request includes a body with all parameters ({{target-directory}} and {{cancel-job}})), even thought the [documentation|https://ci.apache.org/projects/flink/flink-docs-master/api/java/org/apache/flink/runtime/rest/handler/job/savepoints/SavepointHandlers.html] suggests these are optional.
> If a POST request with no data is made, the response is a 400 status code with the error message "Bad request received."
> If the POST request submits an empty JSON object ( {} ), the response is a 400 status code with the error message "Request did not match expected format SavepointTriggerRequestBody."  The same is true if only the {{target-directory}} or {{cancel-job}} parameters are included.
> As the system is configured with a default savepoint location, there shouldn't be a need to include the parameter in the quest.



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