-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/18762/
-----------------------------------------------------------
(Updated April 8, 2014, 1:03 a.m.)
Review request for oozie.
Changes
-------
Updated log message
Bugs: OOZIE-1709
https://issues.apache.org/jira/browse/OOZIE-1709
Repository: oozie-git
Description
-------
CoordELFunctions.getCurrentInstance() has this code:
while (current.compareTo(calEffectiveTime) <= 0) {
current = (Calendar) origCurrent.clone();
instanceCount[0]++;
current.add(dsTimeUnit.getCalendarUnit(), instanceCount[0] *
dsFreq);
}
For coords with smaller frequency and start time in very past, this is very
expensive. On prod, we have seen materialisation of each instance taking few
mins sometimes for coords with 1 min frequency
Diffs (updated)
-----
core/src/main/java/org/apache/oozie/coord/CoordELFunctions.java d73bc7d
core/src/test/java/org/apache/oozie/coord/TestCoordELFunctions.java be35ce4
Diff: https://reviews.apache.org/r/18762/diff/
Testing
-------
UT
Thanks,
shwethags
