Robert Kanter created OOZIE-2644: ------------------------------------ Summary: Skip queuing Notification Commands when there's nothing to notify Key: OOZIE-2644 URL: https://issues.apache.org/jira/browse/OOZIE-2644 Project: Oozie Issue Type: Improvement Affects Versions: 3.1.3 Reporter: Robert Kanter Fix For: 4.4.0
When you use the [Workflow|https://oozie.apache.org/docs/4.2.0/WorkflowFunctionalSpec.html#a5_Workflow_Notifications] or [Coordinator|https://oozie.apache.org/docs/4.2.0/CoordinatorFunctionalSpec.html#a15._Coordinator_Notifications] Notification features, Oozie can end up queuing up a lot of {{WorkflowNotificationXCommand}} and {{CoordActionNotificationXCommand}}. This happens even if there's no notification configured on the job (which I imagine is most of the time); in this case, the {{execute}} method simply does nothing. This is wasteful and clogs the queue up. We should change the code so that it doesn't queue up one of these Commands unless there's actually a URL to notify. It would also be nice if we could combine the code more between the two, but that might be tricky because of the parenting. -- This message was sent by Atlassian JIRA (v6.3.4#6332)