Hello Dirk
Are you perhaps defining this notification.url property in a common xml config
file which your parent workflow as well as sub-workflows refer to? That could
be the only explanation of this occurring. If not, yes you were thinking right
- explicitly override the property in your sub-workflow action to not have the
parent's value. I'm not a 100% sure if there is empty string handling for
configuration properties but worth trying.
On Friday, February 20, 2015 12:13 AM, Daems Dirk <[email protected]>
wrote:
Hi,
I have a root workflow starting multiple sub-workflows. For the root workflow,
I have specified an endpoint on which I want Oozie to notify me of status
modifications (property oozie.wf.workflow.notification.url). This works,
however the child sub-workflows are also sending notifications to this endpoint
although I didn't propagate the configuration (<propagate_configuration/>) to
them.
Indeed, the configuration of the submitted sub-workflow also contains the
oozie.wf.workflow.notification.url property with the endpoint which I specified
for the root workflow.
Is this expected behavior as this is not clear to me when reading the Oozie
workflow functional specification?
Is there a way to change this behavior? Maybe explicitly clearing the value of
this property in the sub-workflow action?
Thanks,
Dirk
VITO Disclaimer: http://www.vito.be/e-maildisclaimer
