[
https://issues.apache.org/jira/browse/OOZIE-818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13273943#comment-13273943
]
Shwetha G S commented on OOZIE-818:
-----------------------------------
Fixes 3 issues in CoordChangeXCommand:
1. timeunit was not used while calculating previous coord action time in
processLookaheadActions. This caused past actions to be deleted
2. timeunit was not used while calculating last action time in checkEndTime.
This caused wrong validation
3. doneMaterialization was never set after coord change. When endTime was
changed such that actual last action time < endTime <= coordJob.lastActionTime,
coord never moves to terminal status(always remains in RUNNING state)
For the patch committed in trunk with this JIRA ID OOZIE-818 (also available
under the same JIRA ID in Apache ReviewBoard system), I grant license to ASF
for inclusion in ASF works (as per the Apache License ยง5)
> CoordChangeXCommand deletes past coordinator actions
> ----------------------------------------------------
>
> Key: OOZIE-818
> URL: https://issues.apache.org/jira/browse/OOZIE-818
> Project: Oozie
> Issue Type: Bug
> Reporter: Shwetha G S
> Assignee: Shwetha G S
> Priority: Critical
>
> CoordChangeXCommand.processLookaheadActions() doesn't use coord timeunit
> while calculating the action times. So, if the frequency is
> non-minutes(hours, days, months...), setting pause time can delete past coord
> actions
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
