Idris, It seems that the FileSystem used by prepare sections should use the configuration of the action. If this is not the case, please file a JIRA for it.
Also, how are you planing to handle <fs> actions? they are run in the oozie server itself. Thx On Wed, Dec 19, 2012 at 8:33 PM, Idris Ali <[email protected]> wrote: > Hi, > > I have build a new filesystem (s4) by extending Amazon's s3n FS. > I could ship the required jars by copying it to lib folder of the workflow > application in HDFS. > > However, the job which runs on TT needs to be aware of new FS* > *(fs.s4.impl), > this can be set in > the configuration section of workflow action, which works fine with oozie > actions. > > But for the "prepare" tag - delete in action, it wont work, and throws > exception, as the config is not set with property > fs.s4.impl. One way to avoid this is to set this property in in > core-site.xml in every node, but that is not desirable. > > Thanks, > -Idris > > > > On Tue, Dec 18, 2012 at 8:52 PM, Alejandro Abdelnur <[email protected] > >wrote: > > > Hi Idris, > > > > What is exactly your usecase? What properties you want to set? > > > > Do you know that you can configure Oozie to use the hadoop site.xml files > > for a particular cluster. Would this be enough for your use case? > > > > Thx > > > > > > On Sun, Dec 16, 2012 at 6:46 PM, Idris Ali <[email protected]> wrote: > > > > > Hi, > > > > > > Currently, Configuration section is not present in prepare tag of > > > workflow.xsd. > > > Ideally, we should be able to pass hadoop configuration to prepare tag > > > (delete, mkdir , etc) > > > > > > In the FileSystemsActions.java in delete and mkdir methods, we should > be > > > able to add additional configurations dynamically to new new > > configuration. > > > > > > Thanks, > > > -Idris > > > > > > > > > > > -- > > Alejandro > > > -- Alejandro
