Member since
09-15-2020
5
Posts
1
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1982 | 09-17-2020 01:17 AM |
09-17-2020
01:17 AM
1 Kudo
Hi Alex, I've resolved the issue. I had been using the wf:X() in the wrong place. Initially I had added an argument for the shell action like ${user} and then set $wf:user() as the value of that argument when submitting the workflow. I replaced ${user} with the Expression Language Function and the value was resolved automatically and when submitting the workflow I wasn't asked to provide a value for the argument 🙂
... View more
09-16-2020
02:21 AM
Thanks Alex, I'm aware that the action name can easily be changed when writing an Oozie workflow using the raw XML. However this doesn't appear possible in the Hue workflow editor... I had hoped that I might just be able to write the XML myself in a simple text editor and then import into Hue, but from what I've found, Hue isn't capable of importing the XML.
... View more
09-15-2020
05:07 AM
I have a shell action node that is able to send notifications to a chat application and can be used as a transition route if another action node in the workflow fails. What I'd like to be able to do, is use wf:user() and wf:lastErrorNode() in that notification. My idea was to pass these values to my shell script as arguments, but when I place 'wf:X()' as the argument to my shell action node, it doesn't resolve to anything and just gives me the raw string as the argument. Is there a way to use these in a shell action node?
... View more
Labels:
- Labels:
-
Apache Oozie
09-15-2020
02:29 AM
Rather than using the automatically generated names that are given to action nodes i.e. shell-12ba, I would like to be able to set the name myself. Is this possible? If so how?
... View more
Labels:
- Labels:
-
Apache Oozie