[
https://issues.apache.org/jira/browse/FLINK-10520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16673505#comment-16673505
]
Huide Yin commented on FLINK-10520:
-----------------------------------
I wonder if `state.savepoints.dir:` specified as the default savpoint path in
your flink-conf.yaml file?
`target-directory` is must have for specify the target location for saving
savepoint
`cancel-job` is must since there's no separate `cacnel` request defined here:
https://ci.apache.org/projects/flink/flink-docs-stable/monitoring/rest_api.html
> 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)
