flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timo Walther (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FLINK-9765) Improve CLI responsiveness when cluster is not reachable
Date Tue, 24 Jul 2018 10:40:00 GMT

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

Timo Walther resolved FLINK-9765.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.6.0
                   1.5.2

Fixed in 1.7.0: 6022225a2b8ddbff7dc0bea9d5ecd55ce0031a9f
Fixed in 1.6.0: 02d8865ce7880a8fc4d98d38640222dddb155956
Fixed in 1.5.2: 860be1dcbc155360c53bb9378d5a49933fbb3809

> Improve CLI responsiveness when cluster is not reachable
> --------------------------------------------------------
>
>                 Key: FLINK-9765
>                 URL: https://issues.apache.org/jira/browse/FLINK-9765
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table API &amp; SQL
>    Affects Versions: 1.5.0
>            Reporter: Timo Walther
>            Assignee: Timo Walther
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.5.2, 1.6.0
>
>
> If the cluster was not started or is not reachable it takes a long time to cancel a result.
This should not affect the main thread. The CLI should be responsive at all times.



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

Mime
View raw message