You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Kostas Kloudas (Jira)" <ji...@apache.org> on 2019/09/17 12:17:00 UTC
[jira] [Commented] (FLINK-14096) Merge NewClusterClient into
ClusterClient
[ https://issues.apache.org/jira/browse/FLINK-14096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16931372#comment-16931372 ]
Kostas Kloudas commented on FLINK-14096:
----------------------------------------
Hi [~Tison], this is a big change and although it seems reasonable to do it at some point, I believe there should be a public discussion in the user and dev ML.
As we discussed earlier, according to [~Zentol], there may be people programming against the cluster client itself and this will break their code.
> Merge NewClusterClient into ClusterClient
> -----------------------------------------
>
> Key: FLINK-14096
> URL: https://issues.apache.org/jira/browse/FLINK-14096
> Project: Flink
> Issue Type: Sub-task
> Components: Client / Job Submission
> Reporter: TisonKun
> Assignee: TisonKun
> Priority: Major
> Fix For: 1.10.0
>
>
> With the effort under FLINK-10392 we don't need the bridge class {{NewClusterClient}} any more. We can just merge {{NewClusterClient}} into {{ClusterClient}} towards an interface-ized {{ClusterClient}}.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)