Re: Loop Detected in Run time Error oozie-3.3.0-cdh4.2.1

e.xml file. > Disabling this validation is determined by the AND of both of these > properties, so it will be disabled if either or both are set to false and > only enabled if both are set to true (or not > specified). > > — > Mona > > On 8/15/14, 10:36 AM, "KayVajj" va

Loop Detected in Run time Error oozie-3.3.0-cdh4.2.1

Hi, I'm using "oozie-3.3.0-cdh4.2.1". The key structure of my workflow is as below. s(i) -- represents initial nodes. -OK- is ok transition -ERROR- is error transition s(1) -OK- --> s(2) -ERROR- --> N (Notify Node) s(2) -- Forks into F(1)..F(7) For each Forked job F(i) -OK- --> J(join node)

firstNotNull failing

Hi, I have a question regarding the firstNotNull function and in general about undefined variables in oozie. I have the following snippet of code in my oozie workflow mapred.job.queue.name ${firstNotNull(defaultQueue, "default")} I wanted to have the default queue to be c

Launcher MR Job

I understand in oozie each action results in two MR jobs 1) Launcher 2) Action Is there any specific reason for the Launcher Job. Why couldn't oozie kickoff just the Action MR job like we do from a command line? Your answers are appreciated. Thanks Kishore