Got it. actualTime() should be quite close to the workflow start time, a few seconds most. Are you seeing big differences?
On Tue, Sep 18, 2012 at 1:50 PM, Eduardo Afonso Ferreira <[email protected]> wrote: > Alejandro, > > I wanted some date variable/function that identified when the workflow > started. > It looks to me that actualTime() is not when it started, but when it was > created by the coordinator. I'm attaching a screengrab that shows a list of > jobs created to run in the future when the nominal time is reached. You can > see that the creation date is the same for many of them and that's what the > actualDate() will be, at least that's what I see when I use it. > > Is there anything I can use at the coordinator.xml level or at the > workflow.xml level to indicate when the workflow really started? > > Thank you. > Eduardo. > > ________________________________ > From: Alejandro Abdelnur <[email protected]> > To: [email protected]; Eduardo Afonso Ferreira <[email protected]> > Sent: Tuesday, September 18, 2012 4:26 PM > Subject: Re: Oozie coordinator currentTime()? > > Eduardo, > > actualTime() is when the coordinator action was started, the > corresponding workflow job is started at the same time. > > I'm not sure what currentTime() would be in that case, would provide an > example? > > Thx > > On Tue, Sep 18, 2012 at 12:33 PM, Eduardo Afonso Ferreira > <[email protected]> wrote: >> Hi there, >> >> I can't find, but I think this is a valid need. I see the following >> functions: >> >> ${coord:actuaTime()} >> >> UTC date corresponding to when the job was created by oozie. >> >> ${coord:nominalTime()} >> >> UTC date corresponding to when the job should start. >> >> Do we have something like this: >> >> ${coord:currentTime()} >> >> UTC date corresponding to when the job starts. >> >> Actual time is not as useful as currentTime. Since that's not available, >> how could I know in coordinator.xml when the job started? >> >> Thank you. >> Eduardo. > > > > -- > Alejandro > > -- Alejandro
