[
https://issues.apache.org/jira/browse/BEAM-6058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689270#comment-16689270
]
Maximilian Michels commented on BEAM-6058:
------------------------------------------
AFAIK _all_ job-related configuration is assembled upon JobGraph creation. The
flink-conf.yaml on the cluster is only relevant for configuring the cluster
itself and for reading environment information (e.g. default parallelism). I
agree that this distinction is not always clear.
[~thw] [~angoenka] How about adding the config to the Jobserver parameters?
That would make the configuration explicit and avoid confusion with where the
config is located or loaded. We clearly need a way to specify the config and
I'm not sure whether the environment variable is the way to go because that is
primarily a way to set it from the bash scripts of the Flink CLI.
> Support flink config directory for flink runner.
> ------------------------------------------------
>
> Key: BEAM-6058
> URL: https://issues.apache.org/jira/browse/BEAM-6058
> Project: Beam
> Issue Type: Bug
> Components: runner-flink
> Reporter: Ankur Goenka
> Assignee: Ankur Goenka
> Priority: Major
> Time Spent: 5h
> Remaining Estimate: 0h
>
> Give user option to use flink configuration from a config directory.
> Earlier we only used jars to submit flink jobs which by default picks the
> cluster flink properties.
> Portability uses remote environment to submit flink job. In Remote
> execution, flink uses the client config instead of the cluster config. This
> require us to submit the custom flink properties via flink client.
> Suggestion is to read the flink config from a flink configuration folder and
> set them to the environment.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
