You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Robert Kanter (JIRA)" <ji...@apache.org> on 2015/09/04 01:19:46 UTC
[jira] [Comment Edited] (OOZIE-2344) Enabling
'oozie.action.jobinfo.enable' doesn't inject the job information into the
map/reduce job's configuration.
[ https://issues.apache.org/jira/browse/OOZIE-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14730008#comment-14730008 ]
Robert Kanter edited comment on OOZIE-2344 at 9/3/15 11:18 PM:
---------------------------------------------------------------
+1 LGTM
This also affects other action types.
Jenkins has been acting up lately. The change is minimal and I ran a bunch of the ActionExecutor and Main tests locally.
was (Author: rkanter):
+1 LGTM
Jenkins has been acting up lately. The change is minimal and I ran a bunch of the ActionExecutor and Main tests locally.
> Enabling 'oozie.action.jobinfo.enable' doesn't inject the job information into the map/reduce job's configuration.
> ------------------------------------------------------------------------------------------------------------------
>
> Key: OOZIE-2344
> URL: https://issues.apache.org/jira/browse/OOZIE-2344
> Project: Oozie
> Issue Type: Bug
> Reporter: Akshay Rai
> Attachments: OOZIE-2344.001.patch
>
>
> According to OOZIE-1658, enabling 'oozie.action.jobinfo.enable' should inject a property, 'oozie.job.info', into the mapreduce job's configuration containing information of bundle, coordinator, workflow and actions. However, this doesn't seem to be the case.
> To fix this, I think we should make sure to inject this property before the actionConf is written to action.xml.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)