[
https://issues.apache.org/jira/browse/OOZIE-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17365345#comment-17365345
]
Dénes Bodó commented on OOZIE-546:
----------------------------------
This issue is already fixed in scope of OOZIE-817
> OOZIE-129: fs action should allow free order of sub-elements
> ------------------------------------------------------------
>
> Key: OOZIE-546
> URL: https://issues.apache.org/jira/browse/OOZIE-546
> Project: Oozie
> Issue Type: Bug
> Reporter: Angelo K. Huang
> Assignee: Angelo K. Huang
> Priority: Major
>
> According to the xsd [1],
> You can use as many commands as you want in the fs action node, but the
> problem is that they have defined the commands within an xs:sequence tag,
> which means the commands can be used only in a particular order. According to
> the xsd, the sequence of the action has to be delete, mkdir, move and chmod.
> This implies that you cannot have an mkdir after move :-/.
> I don't particularly understand the reasoning behind why it is defined as an
> xs:sequence though.
> Regards,
> Arun
> [1]
> http://yahoo.github.com/oozie/releases/3.0.0/WorkflowFunctionalSpec.html#Oozie_Schema_Version_0.2
> ----------------------------------------------------------------------
> I think the XSD is written in a very rigid form. The user needs to follow
> that order. However, we should relax the constraint by allowing any
> ordering. We could use "xs:choice" in XSD and need to make sure that in the
> execution order too.
> Regards,
> Mohammad
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
