[
https://issues.apache.org/jira/browse/FLINK-17500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17101410#comment-17101410
]
Zhu Zhu commented on FLINK-17500:
---------------------------------
Agreed that this proposal can make the job submission more flexible.
The only concern is that we will then need to be very careful of JobGraph to
not break compatibility. That means we can hardly change the structure and
default values of JobGraph and its sub-components.
I know that pre-generated jobgraph file is already in use for mesos mode. But I
feel that at the moment we are yet not strictly limited to not change JobGraph.
> Deploy JobGraph from file in StandaloneClusterEntrypoint
> --------------------------------------------------------
>
> Key: FLINK-17500
> URL: https://issues.apache.org/jira/browse/FLINK-17500
> Project: Flink
> Issue Type: Wish
> Components: Deployment / Docker
> Reporter: Ufuk Celebi
> Priority: Minor
>
> We have a requirement to deploy a pre-generated {{JobGraph}} from a file in
> {{StandaloneClusterEntrypoint}}.
> Currently, {{StandaloneClusterEntrypoint}} only supports deployment of a
> Flink job from the class path using {{ClassPathPackagedProgramRetriever}}.
> Our desired behaviour would be as follows:
> If {{internal.jobgraph-path}} is set, prepare a {{PackagedProgram}} from a
> local {{JobGraph}} file using {{FileJobGraphRetriever}}. Otherwise, deploy
> using {{ClassPathPackagedProgramRetriever}} (current behavior).
> ---
> I understand that this requirement is pretty niche, but wanted to get
> feedback whether the Flink community would be open to supporting this
> nonetheless.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
