Closed cfournie closed 7 years ago
Could you add a supported versions section to the README? Otherwise LGTM
Is s/coordinator/workflow
an issue? Presumably we're unable to use any 0.5 artifacts.
Is s/coordinator/workflow an issue? Presumably we're unable to use any 0.5 artifacts.
oozie-site.xml
states that the schemas that it's using in Oozie 4.1.0 are:
<property>
<name>oozie.service.SchemaService.wf.ext.schemas</name>
<value>
shell-action-0.1.xsd,shell-action-0.2.xsd,shell-action-0.3.xsd,email-action-0.1.xsd,email-action-0.2.xsd,
hive-action-0.2.xsd,hive-action-0.3.xsd,hive-action-0.4.xsd,hive-action-0.5.xsd,sqoop-action-0.2.xsd,
sqoop-action-0.3.xsd,sqoop-action-0.4.xsd,ssh-action-0.1.xsd,ssh-action-0.2.xsd,distcp-action-0.1.xsd,
distcp-action-0.2.xsd,oozie-sla-0.1.xsd,oozie-sla-0.2.xsd
</value>
</property>
We use shell-action-0.3
and email-action-0.2.
at the moment, which are OK. And it accepted a oozie-workflow-0.5
workflow in my integration test.
@kmtaylor-github 👍 / 👎 ?
Submitting a coordinator to oozie 4.1.0 using
xmlns="uri:oozie:coordinator:0.5"
fails with:Out of the box it can't read
uri:oozie:coordinator:0.5
. To fix this, this PR downgrads the schema that its generated coordinators use touri:oozie:coordinator:0.4
. There are only slight differences in available tags (none of which we use):review/ @kmtaylor-github @honkfestival