[
https://issues.apache.org/jira/browse/OOZIE-949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13448641#comment-13448641
]
James Kinley commented on OOZIE-949:
------------------------------------
Thanks Alejandro,
I've added this for the launcher job too, so now you can set 'mapred.job.name'
and 'oozie.launcher.mapred.job.name'.
When testing locally with 'mapred.job.name' set, and despite the mapreduce job
finishing successfully, the workflow is marked as failed because of the
following check in:
{{org.apache.oozie.action.hadoop.MapReduceActionExecutor#end}}
// TODO this has to be done in a better way
if (!runningJob.getJobName().startsWith("oozie:action:")) {
throw new ActionExecutorException(ActionExecutorException.ErrorType.FAILED,
"MR001",
"ID swap should have happened in launcher job [{0}]",
action.getExternalId());
}
Why do we need to do this check?
> 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
> Labels: patch
> Fix For: trunk
>
> Attachments: OOZIE-949.patch
>
>
> Give user the ability to set {{mapred.job.name}} in their workflow 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
