You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Purshotam Shah (JIRA)" <ji...@apache.org> on 2014/05/03 02:15:18 UTC
[jira] [Commented] (OOZIE-1709)
CoordELFunctions.getCurrentInstance() is expensive
[ https://issues.apache.org/jira/browse/OOZIE-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13988462#comment-13988462 ]
Purshotam Shah commented on OOZIE-1709:
---------------------------------------
Tested with multiple timezone. Looks good. Thanks Shwetha for the patch.
> CoordELFunctions.getCurrentInstance() is expensive
> --------------------------------------------------
>
> Key: OOZIE-1709
> URL: https://issues.apache.org/jira/browse/OOZIE-1709
> Project: Oozie
> Issue Type: Bug
> Reporter: Shwetha G S
> Assignee: Shwetha G S
> Fix For: trunk
>
> Attachments: OOZIE-1709-v2.patch, OOZIE-1709.patch
>
>
> {noformat}
> while (current.compareTo(calEffectiveTime) <= 0) {
> current = (Calendar) origCurrent.clone();
> instanceCount[0]++;
> current.add(dsTimeUnit.getCalendarUnit(), instanceCount[0] * dsFreq);
> }
> {noformat}
> This computes current instance wrt coord start and this while loop is expensive for small frequency coords with start time in very past
--
This message was sent by Atlassian JIRA
(v6.2#6252)