Yes, you are right. The issue happened on EMR 5.22 for us, which comes with
Oozie 5.1.0
I will test a lower version of EMR with Oozie 5.0.0. From the JIRA, it looks
like this issue only happens since Oozie 5.1.0
For us, we are currently using EMR 5.12.2 with Oozie 4.3.0, and everything
works f
What EMR version are you using? Can you confirm you are using Oozie 5.0? I ask
because I encountered a similar problem when we went from Oozie 5.0 to 5.1
while upgrading to EMR 5.22. I believe oozie.jobs.api.generated.xml was added
in Oozie 5.1. See https://issues.apache.org/jira/browse/OOZIE-3
Hi, I am facing a strange issue on Oozie 5.0.
I have an Ozzie application that works fine in the workflow mode.
Here is the only 2 examples line of my oozie properties file:
oozie.wf.application.path=${appBaseDir}/workflow/workflow.xml
#oozie.coord.application.path=${appBaseDir}/workflow/coordin
