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

Virag Kothari commented on OOZIE-1146:
--------------------------------------

+1
                
> FileSystem used by prepare sections should use the configuration of the action
> ------------------------------------------------------------------------------
>
>                 Key: OOZIE-1146
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1146
>             Project: Oozie
>          Issue Type: Bug
>          Components: action, workflow
>    Affects Versions: 3.2.0, 3.2.1
>         Environment: Oozie 3.2.2, Hadoop cdh3u3
>            Reporter: Shaik Idris Ali
>            Assignee: Rohini Palaniswamy
>              Labels: action, delete, prepare
>             Fix For: trunk, 4.0.0
>
>         Attachments: OOZIE-1146-1-branch4.patch, OOZIE-1146-1.patch
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> We should be able to propagate configurations to prepare section (delete, 
> mkdir) of action in workflow xmls.
> Though the configuration section is available per action, it is not available 
> in for prepare tags:
> A simple use-case is to support custom filesystem by configuring the 
> filesystem impl class in configuration, but delete prepare action is not 
> aware of configuration set in action xml.
> Ex:<action name="myfirstHadoopJob">
>         <map-reduce>
>             <job-tracker>foo:9001</job-tracker>
>             <name-node>bar:9000</name-node>
>             <prepare>
>                 <delete path="hdfs://foo:9000/usr/tucu/output-data"/>
>             </prepare>
>             <job-xml>/myfirstjob.xml</job-xml>
>             <configuration>
>                 
> <property><name>fs.s4.impl</name><value>org.apache.grid.fs.s4fs.NativeS4FileSystem</value></property>
>             .....
> I think this can be fixed in FileSystemsActions.java

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to