[
https://issues.apache.org/jira/browse/OOZIE-2648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15488570#comment-15488570
]
Robert Kanter commented on OOZIE-2648:
--------------------------------------
+1
I'll add an {{\@Override}} during commit.
> Child jobs shouldn't send callbacks to Oozie
> --------------------------------------------
>
> Key: OOZIE-2648
> URL: https://issues.apache.org/jira/browse/OOZIE-2648
> Project: Oozie
> Issue Type: Improvement
> Affects Versions: trunk
> Reporter: Robert Kanter
> Assignee: Abhishek Bafna
> Attachments: OOZIE-2648-00.patch
>
>
> I noticed that all action.xml files end up having
> {{job.end.notification.url}} set to send the callback to the Oozie Server
> when they finish. This makes it so that all child MR jobs have this, and
> send notifications to the Oozie Server. This isn't the end of the world, but
> it's unnecessary, especially if you end up with multiple child jobs (e.g. a
> Hive Action that spawns multiple MR jobs). We should consider only adding it
> to the Launcher Job. The exception to this is the MapReduce Action, where
> the Launcher Job exits early and Oozie directly monitors the MR child; in
> this case, the child should have it and the Launcher should not.
> The call in {{JavaActionExecutor}} to {{injectActionCallback(context,
> actionConf);}} is where this happens.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
