[
https://issues.apache.org/jira/browse/FLINK-17469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Lonergan updated FLINK-17469:
----------------------------------
Description:
We are running multiple jobs on a shared standalone HA Cluster.
We want to be able to provide the job name via the submitting shell script
using a standard system property.
We could of course write Java application code in each job to achieve this by
passing the system property value ourselves to the execute(name) method,
however we want to do this from the env.
---
However, there exists already default job name in
StreamExecutionEnvironment.DEFAULT_JOB_NAME.
Our proposed changed to add a method to StreamExecutionEnvironment...
{code:java}
String getDefaultJobName() {
return System.getProperty("default.job.name",
StreamExecutionEnvironment.DEFAULT_JOB_NAME);
}
{code}
.. and call that method rather than directly accessing
StreamExecutionEnvironment.DEFAULT_JOB_NAME
This change is backwards compatible.
We need this method to evalulate on a job by job basis so for example the
following small amendment to the existing DEFAULT_JOB_NAME value will NOT work
because this will not allow us to vary the value job by job.
{code:java}
class StreamExecutionEnvironment {
static final String DEFAULT_JOB_NAME = System.getProperty("default.job.name",
"Flink Streaming Job"))
}
{code}
was:
We want to be able to provide the job name using a standard system property
"job.name".
We can of course write application code in each job to achieve this by passing
the system property value ourselves to the execute method.
However, there exists already default job name in
StreamExecutionEnvironment.DEFAULT_JOB_NAME.
Our proposed changed to add a method to StreamExecutionEnvironment...
{code:java}
String getDefaultJobName() {
return System.getProperty("job.name",
StreamExecutionEnvironment.DEFAULT_JOB_NAME);
}
{code}
.. and call that method rather than directly accessing
StreamExecutionEnvironment.DEFAULT_JOB_NAME
This change is backwards compatible.
> Support override of DEFAULT_JOB_NAME with system property for
> StreamExecutionEnvironment
> ----------------------------------------------------------------------------------------
>
> Key: FLINK-17469
> URL: https://issues.apache.org/jira/browse/FLINK-17469
> Project: Flink
> Issue Type: New Feature
> Components: API / Core
> Affects Versions: 1.10.0
> Reporter: John Lonergan
> Priority: Trivial
>
> We are running multiple jobs on a shared standalone HA Cluster.
> We want to be able to provide the job name via the submitting shell script
> using a standard system property.
> We could of course write Java application code in each job to achieve this by
> passing the system property value ourselves to the execute(name) method,
> however we want to do this from the env.
> ---
> However, there exists already default job name in
> StreamExecutionEnvironment.DEFAULT_JOB_NAME.
> Our proposed changed to add a method to StreamExecutionEnvironment...
> {code:java}
> String getDefaultJobName() {
> return System.getProperty("default.job.name",
> StreamExecutionEnvironment.DEFAULT_JOB_NAME);
> }
> {code}
> .. and call that method rather than directly accessing
> StreamExecutionEnvironment.DEFAULT_JOB_NAME
> This change is backwards compatible.
> We need this method to evalulate on a job by job basis so for example the
> following small amendment to the existing DEFAULT_JOB_NAME value will NOT
> work because this will not allow us to vary the value job by job.
> {code:java}
> class StreamExecutionEnvironment {
> static final String DEFAULT_JOB_NAME =
> System.getProperty("default.job.name", "Flink Streaming Job"))
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
