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/18 09:54:00 UTC

[jira] [Comment Edited] (FLINK-14113) Remove class JobWithJars

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

Kostas Kloudas edited comment on FLINK-14113 at 9/18/19 9:53 AM:
-----------------------------------------------------------------

[~Tison] I think also [~aljoscha] has some ideas about the whole path from {{Plan}}/ {{StreamGraph}} to {{JobGraph}} so he may have something to say on this topic. But in general I agree that some things are worth consolidating there.


was (Author: kkl0u):
[~Tison] I think also [~aljoscha] has some ideas about the whole path from {{Plan}}/ {{StreamGraph}} to {{JobGraph}} so he may have something to say on this topic.

> Remove class JobWithJars
> ------------------------
>
>                 Key: FLINK-14113
>                 URL: https://issues.apache.org/jira/browse/FLINK-14113
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Client / Job Submission
>            Reporter: TisonKun
>            Priority: Major
>             Fix For: 1.10.0
>
>
> {{JobWithJars}} is a batch-only concept, acts as a POJO consists of {{Plan}} and {{URL}}s of libs. We can
> 1. inline the usage of {{Plan}} and {{URL}}s as we do in streaming case.
> 2. extract static methods into a utility class said {{ClientUtils}}.
> The main purpose here is towards no batch specific concept that doesn't bring too much good.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)