[
https://issues.apache.org/jira/browse/FLINK-17500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17098859#comment-17098859
]
Till Rohrmann commented on FLINK-17500:
---------------------------------------
Thanks for proposing this improvement [~uce]. I think this would be a good
improvement. I have two comments:
1. Instead of relying on {{internal.jobgraph-path}} I would propose to make the
selection of the {{JobGraphRetriever}} strategy a separate configuration option
(e.g. {{internal.job-graph-retriever: classpath/file}}) and then have
{{internal.job-graph-retriever.file.path}} or so.
2. Can we unify the mechanism with the {{YarnJobClusterEntrypoint}}? Ideally
the logic to select the right retriever would go into the
{{JobClusterEntrypoint}} and the {{YarnClusterDescriptor}} will simply start
the {{YarnJobClusterEntrypoint}} with the {{FileJobGraphRetriever}}.
> 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)
