[
https://issues.apache.org/jira/browse/FLINK-17500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17101541#comment-17101541
]
Ufuk Celebi commented on FLINK-17500:
-------------------------------------
[~zhuzh] Good points. I would agree to keep the JobGraph an internal API and
don't make any guarantees about compatibility here. As indicated by the
proposed configuration option keys I consider this internal configuration only.
(In our use case we strictly tie the JobGraph to the Flink version and don't
re-use it across job executions.)
> 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)
