Hi Junaid,
Coordinator job datetimes are always expressed in UTC.
The timezone attribute for the coordinator-app and for datasets is only
used to perform DST adjustments. For example, if you want to run something
always at midnight where midnight may change -/+ 1hr because of a DST
observing timezone.
Regarding your second question, there are 2 EL functions you can use in the
coordinator action section and pass them as parameters to the WF job you
are starting from the coordinator, ${coord:nominalTime()} and
${coord:actualTime()}, the are explained in detail in the spec:
http://oozie.apache.org/docs/3.2.0-incubating/CoordinatorFunctionalSpec.html#a6.7.3._coord:nominalTime_EL_Function
Thx
On Thu, Dec 20, 2012 at 11:50 AM, Junaid Aslam <k.junaid.as...@gmail.com>wrote:
> i am new to oozie and having problem in changing oozie default time zone. I
> am writing oozie coordinator job and have tried to specify timezone like
>
> <coordinator-app name="hello-coord" frequency="${coord:days(1)}"
> start="2009-01-02T08:00Z" end="2009-01-04T08:00Z"
> timezone="GMT+05:30"
> xmlns="uri:oozie:coordinator:0.1">
>
>
> as explained here
>
> http://oozie.apache.org/docs/3.2.0-incubating/CoordinatorFunctionalSpec.html#a4._Datetime_Frequency_and_Time-Period_Representationbut
> it does not work. Can anyone please tell me where do i go wrong?
>
> Secondly, i want to get date time when the oozie workflow starts. Suppose i
> want to run a coordinator job for a past date, say a week ago, that job ran
> for a whole day with frequency of 15 mins. what i want is to have date time
> at the time when the workflow started.
>
> Thank you very much for your precious time
>
--
Alejandro
