[ 
https://issues.apache.org/jira/browse/OOZIE-872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396334#comment-13396334
 ] 

Alejandro Abdelnur commented on OOZIE-872:
------------------------------------------

Britt,

* Wouldn't make more sense to call it touch and support the unix semantics of 
it 'The touch utility sets the modification and access times of files to the 
current time of day.  If the file doesn't exist, it is created with default 
permissions.' ?
* The patch seems to have several false changes due to reformatting, would you 
please make a patch without such changes?
* We cannot modify a XSD of a release version, we'll need a new XSD, 0.4 for 
this. There are other JIRAs that are adding things to the XSD, the first of 
such JIRAs (this, OOZIE-12, OOZIE-861) should add/wire the new XSD file, and 
the other just modify (until we release we can do that).

Also, I'm adding you as contributor, and I'll assign the JIRA (and OOZIE-861) 
to you, new JIRAs just take ownership. THX!

                
> Support touchz in fs node of oozie worklfow
> -------------------------------------------
>
>                 Key: OOZIE-872
>                 URL: https://issues.apache.org/jira/browse/OOZIE-872
>             Project: Oozie
>          Issue Type: Improvement
>            Reporter: Britt Cyr
>            Priority: Minor
>         Attachments: OOZIE-872.patch
>
>
> My workflow has the need to touch an empty file after all the sub workflows 
> are done. Hadoop supports touchz to create an empty file, but my oozie 
> workflow fails when I give it in the fs node of oozie workflow.
> <action name="touchsuccess">
>         <fs>
>             <touchz path="${DS_OUTPUT_INTERESTCATEGORY}/_SUCCESS"/>
>         </fs> 
>         <ok to="end"/>
>         <error to="kill"/>    
>     </action>
> Right now the only supported options are chmod, move, delete and mkdir. Could 
> we have the support for touchz also?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to