[
https://issues.apache.org/jira/browse/FLINK-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fabian Hueske closed FLINK-3293.
--------------------------------
Resolution: Fixed
Fix Version/s: 1.0.0
Fixed with 934774f0d2005ed93feb3e688d60a06076b94e92
> Custom Application Name on YARN is ignored in deploy jobmanager mode
> --------------------------------------------------------------------
>
> Key: FLINK-3293
> URL: https://issues.apache.org/jira/browse/FLINK-3293
> Project: Flink
> Issue Type: Bug
> Components: YARN Client
> Affects Versions: 0.10.1
> Reporter: Johannes
> Assignee: Johannes
> Priority: Minor
> Fix For: 1.0.0
>
>
> FLINK-2298 introduced a custom name for the job.
> This is ignored when the yarn application is started as part of the job
> submission, e.g.
> flink run -m yarn-cluster -ynm myname
> It is always set using the classname as program name
> flinkYarnClient.setName("Flink Application: " + programName);
> The client get's constructed using
> AbstractFlinkYarnClient flinkYarnClient =
> CliFrontendParser.getFlinkYarnSessionCli().createFlinkYarnClient(commandLine);
> So the name will be parsed correctly, it is just overwritten.
> This should be a fallback, when no name is provided
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
