You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "TisonKun (Jira)" <ji...@apache.org> on 2019/09/05 02:42:00 UTC

[jira] [Commented] (FLINK-13961) Remove obsolete abstraction JobExecutor(Service)

    [ https://issues.apache.org/jira/browse/FLINK-13961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16923003#comment-16923003 ] 

TisonKun commented on FLINK-13961:
----------------------------------

Hi [~kkl0u] I'd like to work on this issue. Please assign the issue to me if there is no more concern. I'm going to start progress once FLINK-13946 resolved since there would be several conflicts and FLINK-13946 is almost done.

> Remove obsolete abstraction JobExecutor(Service) 
> -------------------------------------------------
>
>                 Key: FLINK-13961
>                 URL: https://issues.apache.org/jira/browse/FLINK-13961
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Client / Job Submission
>    Affects Versions: 1.10.0
>            Reporter: TisonKun
>            Priority: Major
>             Fix For: 1.10.0
>
>
> Refer to Till's comment
> The JobExecutor and the JobExecutorService have been introduced to bridge between the Flip-6 MiniCluster and the legacy FlinkMiniCluster. They should be obsolete now and could be removed if needed.
> Actually we should make used of {{MiniClusterClient}} for submission ideally but we have some tests based on MiniCluster in flink-runtime or somewhere that doesn't have a dependency to flink-client; while move {{MiniClusterClient}} to flink-runtime is unclear whether reasonable or not. Thus I'd prefer keep {{executeJobBlocking}} for now and defer the possible refactor.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)