You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Yang Wang (Jira)" <ji...@apache.org> on 2019/11/01 02:05:00 UTC
[jira] [Commented] (FLINK-14501) Move
ClusterDescriptor/ClusterSpecification creation from the CustomCommandLine
to a ClusterClientFactory
[ https://issues.apache.org/jira/browse/FLINK-14501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16964531#comment-16964531 ]
Yang Wang commented on FLINK-14501:
-----------------------------------
Glad to see that Jira has been resolved. I will add a FlinkKubernetesCustomCli for active Kubernetes integration based on this.
https://issues.apache.org/jira/browse/FLINK-10936
> Move ClusterDescriptor/ClusterSpecification creation from the CustomCommandLine to a ClusterClientFactory
> ---------------------------------------------------------------------------------------------------------
>
> Key: FLINK-14501
> URL: https://issues.apache.org/jira/browse/FLINK-14501
> Project: Flink
> Issue Type: Sub-task
> Components: Client / Job Submission, Command Line Client
> Affects Versions: 1.9.0
> Reporter: Kostas Kloudas
> Assignee: Kostas Kloudas
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.10.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This issue targets to make the {{ClusterDescriptor}} and the {{ClusterSpecification}} independent from the {{CommandLine}} . Currently this is not the case, as the {{CustomCommandLine}} is responsible for instantiating them.
>
> The correct {{ClusterClientFactory}} can be discovered based on Service Discovery.
>
> This decoupling will enable the further decoupling of the cluster execution from the command line-related code, which apart from unnecessary, it is also a bad separation of concerns. Now the {{CustomCommandLine}} is only responsible for parsing the CLI options to configuration options.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)