You would put something equivalent instead of the NN. For example, when running against the local filesystem, you’d do: <name-node>file:////</name-node> I agree that its not exactly clear.
In any case, lets keep the discussion for this on OOZIE-1695 (which you created) to keep it all in one place. On Thu, Feb 13, 2014 at 1:23 PM, Jay Vyas <[email protected]> wrote: > Thanks mona: > > But... what if we are running oozie without HDFS (i.e. on S3Filesystem, > GlusterFileSystem, or any other file system which has no NameNode )? This > is clearly supported (see OOZIE-426). > > > On Thu, Feb 13, 2014 at 3:04 PM, Mona Chitnis <[email protected]> > wrote: > > > Oozie is coupled with Map-reduce framework and uses HDFS as one of the > > supported filesystems. Oozie will load your workflow definition from the > > HDFS location so NN required. > > If you use xml namespace version 0.4 and higher, you can use a <global> > > tag to specify common params such as NN/JT/configuration for all your > > actions. > > > > ‹Mona > > > > On 2/13/14, 11:47 AM, "Jay Vyas" <[email protected]> wrote: > > > > >Is a nameNode a required element for plain java or mapreduce oozie > > >actions? > > >It seems so, but im not sure why: > > > > > > oozie job -oozie http://localhost:11000/oozie -config job.properties > > -run > > >Error: E0701 : E0701: XML schema error, cvc-complex-type.2.4.a: Invalid > > >content was found starting with element 'configuration'. One of > > >'{"uri:oozie:workflow:0.1":name-node}' is expected. > > > > > >It seems like the namenode should be an optional parameter, since > > >according > > >to https://issues.apache.org/jira/browse/OOZIE-426, OOZIE is written > > >directly against the file system API, without any coupling to HDFS/. > > > > > > > > >-- > > >Jay Vyas > > >http://jayunit100.blogspot.com > > > > > > > -- > Jay Vyas > http://jayunit100.blogspot.com >
