[
https://issues.apache.org/jira/browse/OOZIE-3033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16126525#comment-16126525
]
Robert Kanter commented on OOZIE-3033:
--------------------------------------
Doing all of this would be nice (for instance, I'd really like to not have
{{<configuration>}} redefined everywhere), but I'm not sure how we can do it in
a compatible way. We definitely shouldn't change the previous schemas, but
perhaps we can do this for the new schemas we're doing in OOZIE-2687? The
downside is that in the past, users can typically upgrade their schema by
simply changing the version and typically nothing else (e.g.
{{uri:oozie:workflow:0.4}} --> {{uri:oozie:workflow:0.5}}), and this would
change that. Though Oozie 5 might be a good time to make that change.
> Extract workflow action XML schemas to separate xsd-s
> -----------------------------------------------------
>
> Key: OOZIE-3033
> URL: https://issues.apache.org/jira/browse/OOZIE-3033
> Project: Oozie
> Issue Type: Bug
> Affects Versions: 5.0.0
> Reporter: Attila Sasvari
>
> {{oozie-workflow-0.5.xsd}} contains complex type definitions of many actions:
> {code}
> <xs:element name="map-reduce" type="workflow:MAP-REDUCE"/>
> <xs:element name="pig" type="workflow:PIG"/>
> <xs:element name="sub-workflow" type="workflow:SUB-WORKFLOW"/>
> <xs:element name="fs" type="workflow:FS"/>
> <xs:element name="java" type="workflow:JAVA"/>
> {code}
> These should be extracted to separate xsd-s like hive and shell actions
> ({{oozie-default.xml}} is to be updated too).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
