Julian Endres created OOZIE-2970:
------------------------------------
Summary: Coordinator calculates wrong year on January 1st when
started in future
Key: OOZIE-2970
URL: https://issues.apache.org/jira/browse/OOZIE-2970
Project: Oozie
Issue Type: Bug
Affects Versions: 4.2.0
Environment: Hadoop HDP 2.5.3
Reporter: Julian Endres
In our coordinator application we use the function combination
coord:formatTime(coord:nominalTime()) a lot to calculate some critical
properties e.g. for SQL statements.
Sometimes we run the Coordinator with a start time and end time in the past (we
are catching up some workflow instances / data sets). Usually this works well
and the values of the properties get calculated correctly.
However, when I was just setting a Coordinator (Timezone is UTC) to start at
2017-01-01T00:00Z, with a frequency of 60 minutes the whole first of January
e.g. the function
${coord:formatTime(coord:nominalTime(),"YYYY-MM-dd'T'HH")}
returned the wrong year for example *2016*-01-01T01, *2016*-01-01T02... and so
on.
On the second of January all the calculations where correct with 2017-01-02T01
etc.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
