[
https://issues.apache.org/jira/browse/FLINK-8632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16371623#comment-16371623
]
ASF GitHub Bot commented on FLINK-8632:
---------------------------------------
Github user GJL commented on a diff in the pull request:
https://github.com/apache/flink/pull/5451#discussion_r169687251
--- Diff:
flink-runtime/src/main/java/org/apache/flink/runtime/rest/handler/job/savepoints/SavepointHandlers.java
---
@@ -109,9 +97,7 @@
* }
* </pre>
--- End diff --
You removed the trigger id from the savepoint response but the Javadoc
still has it:
```
* <pre>
* {
* "status": {
* "id": "COMPLETED"
* },
* "savepoint": {
* "request-id": "7d273f5a62eb4730b9dea8e833733c1e",
* "location": "/tmp/savepoint-d9813b-8a68e674325b"
* }
* }
```
> Generalize SavepointHandlers to be used for other asynchronous operations
> -------------------------------------------------------------------------
>
> Key: FLINK-8632
> URL: https://issues.apache.org/jira/browse/FLINK-8632
> Project: Flink
> Issue Type: Improvement
> Components: REST
> Affects Versions: 1.5.0
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Priority: Major
> Labels: flip-6
> Fix For: 1.5.0
>
>
> We should generalize the {{SavepointHandlers}} to be usable for other
> asynchronous operations as well. The basic idea is that one has a trigger
> handler which triggers an asynchronous operation. This operation returns a
> future which is completed once the operation is done. The trigger handler
> returns a trigger id which can be used to check the status of the operation
> by querying the status handler.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
