Hello, I'm new to using oozie and I've been trying to figure out how to use the output of an action as the input of the next action in Oozie. I'm actually coming from using traditional ETLs, where the output of one Step can be used as arguments in the next Step. My question is whether the following points are possible with Oozie: Use the output of one action as the input of the next action Let a subsequent action be executed "n" times according to the output of the first action. Like sub jobs or something. Actually, in order to know if this is possible, we are trying to run a very basic dump example where we read and insert with two hive actions, one for read a table and another one to write. Something like the following example created with Hue Oozie Editor. <workflow-app name="Workflow" xmlns="uri:oozie:workflow:0.5"> <start to="hive-04f4"/> <kill name="Kill"> <message>Error al realizar la acción. Mensaje de error [${wf:errorMessage(wf:lastErrorNode())}]</message> </kill> <action name="hive-04f4" cred="hive2"> <hive2 xmlns="uri:oozie:hive2-action:0.1"> <job-tracker>${jobTracker}</job-tracker> <name-node>${nameNode}</name-node> <jdbc-url>jdbc:hive2://host:10000/default</jdbc-url> <script>${wf:appPath()}/hive-04f4.sql</script> </hive2> <ok to="hive-1c24"/> <error to="Kill"/> </action> <action name="hive-1c24" cred="hive2"> <hive2 xmlns="uri:oozie:hive2-action:0.1"> <job-tracker>${jobTracker}</job-tracker> <name-node>${nameNode}</name-node> <jdbc-url>jdbc:hive2://host:10000/default</jdbc-url> <script>${wf:appPath()}/hive-1c24.sql</script> <param>fecha=${fecha_insercion}</param> <param>registro=${now}</param> </hive2> <ok to="End"/> <error to="Kill"/> </action> <end name="End"/> </workflow-app>
... View more
