[
https://issues.apache.org/jira/browse/OOZIE-949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13433196#comment-13433196
]
James Kinley commented on OOZIE-949:
------------------------------------
The reason for this is I have a workflow which is triggered multiple times with
different input, and each workflow has many parallel sub-workflows / actions
making it difficult to see what is going on in the job tracker. If I could set
the job names I could make it clearer to see what's going on in the jt rather
than having to go back through the Oozie GUI.
I could simply pull out:
bq. String jobName = XLog.format("oozie:action:T={0}:W={1}:A={2}:ID={3}",
getType(), context.getWorkflow().getAppName(), action.getName(),
context.getWorkflow().getId());
bq. actionConf.set("mapred.job.name", jobName);
Into its own method which could check whether the job name has already been set
and if it has, don't override it.
> Allow the user to set 'mapred.job.name'
> ---------------------------------------
>
> Key: OOZIE-949
> URL: https://issues.apache.org/jira/browse/OOZIE-949
> Project: Oozie
> Issue Type: Improvement
> Components: action, core
> Affects Versions: 3.1.3
> Reporter: James Kinley
> Priority: Minor
> Fix For: trunk
>
>
> Give user the ability to set {{mapred.job.name}} in their Oozie job
> configuration and not have Oozie override it in
> {{JavaActionExecutor#submitLauncher()}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
