[
https://issues.apache.org/jira/browse/FLINK-7791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16200261#comment-16200261
]
ASF GitHub Bot commented on FLINK-7791:
---------------------------------------
Github user tillrohrmann commented on a diff in the pull request:
https://github.com/apache/flink/pull/4802#discussion_r144007707
--- Diff:
flink-clients/src/main/java/org/apache/flink/client/program/ClusterClient.java
---
@@ -684,6 +688,29 @@ public void stop(final JobID jobId) throws Exception {
}
/**
+ * Lists the currently running jobs on the cluster.
+ *
+ * @return future collection of running jobs
+ * @throws Exception if no connection to the cluster could be
established
+ */
+ public CompletableFuture<Collection<JobDetails>> listJobs() throws
Exception {
--- End diff --
I'm wondering whether the `ClusterClient` should issue a synchronous
operation instead of a asynchronous operation (simply waiting on the futures
completion). So far all the `ClusterClient` operations are blocking and wait
for the completion. Not entirely sure which is more intuitive to use for the
user. Of course the asynchronous variant gives more freedom.
> Integrate LIST command into REST client
> ---------------------------------------
>
> Key: FLINK-7791
> URL: https://issues.apache.org/jira/browse/FLINK-7791
> Project: Flink
> Issue Type: Sub-task
> Components: Client, REST
> Affects Versions: 1.4.0
> Reporter: Chesnay Schepler
> Assignee: Chesnay Schepler
> Fix For: 1.4.0
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
