[OOZIE-2648] Child jobs shouldn't send callbacks to Oozie

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: trunk
• Fix Version/s: 4.3.0
• Assignee: Abhishek Bafna
• Reporter: Robert Kanter
• Created: 20/Aug/16 03:39
• Updated: 02/Dec/16 21:02
• Resolved: 13/Sep/16 22:16

Description

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.