Thanks Alejandro, using flag files isn't an option for me. I'd rather go for a specific action which implements this functionality. This has other drawbacks but probably fits my needs better.
Thank you for your reply, Lars On Mon, May 7, 2012 at 5:41 PM, Alejandro Abdelnur <[email protected]>wrote: > Lars, > > This functionality has not been implemented yet. > > You could modeled it using an input dataset as flag file. > > Thx. > > Alejandro > > On Mon, May 7, 2012 at 3:33 AM, Lars Grote <[email protected]> wrote: > > Hi there, > > I'm using oozie to manage a quite complex set of workflows. Which works > > fine in most cases. > > Currently I'm having a problem with preconditions. I read those specs > > > http://incubator.apache.org/oozie/docs/3.1.3/docs/CoordinatorFunctionalSpec.html#a6.1.1._Coordinator_Application > > There is stated that Oozie is able to react to the "the availability of > new > > dataset instances or other *external events*." > > > > How can I make use of those *external events*? Cause that's the exact > > problem that I'm facing right now. > > Basically what I was hoping for is a precondition tag which just checks > if > > the content is true or false. Cause then > > I would be able to implement the check as EL extension. > > > > as Example: > > <input-events> > > <test>[MY FANCY EL EXPRESSION]</test> > > </input-events> > > > > Is there any way to get this behavior, any workaround or something? > > > > Thanks in advance, > > Lars > > > > -- > Alejandro >
