[
https://issues.apache.org/jira/browse/OOZIE-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14066169#comment-14066169
]
Shwetha G S commented on OOZIE-1319:
------------------------------------
Previously, LAST_ONLY was running the latest ready action. The gap was that it
was picking up even the old ready instances after that. So, I thought just
skipping the old instances in CoordActionReadyXCommand would complete the
feature. But the current implementation changes the meaning of LAST_ONLY to run
only the latest nominal time(makes sense in case of backlog, but the backlog is
in waiting actions which will happen probably because of materialisation delays
which is internal to oozie?)
Anyways, now that its implemented already, Is there a usecase for the current
implementation of LAST_ONLY. If there is, I will add another enum which
executes latest ready action and discards the rest. If there is no usecase, can
we modify LAST_ONLY to run the latest ready action?
Depending on what we decide, I will create the jira accordingly. Let me know.
Thanks
> "LAST_ONLY" in execution control for coordinator job still runs all the
> actions
> -------------------------------------------------------------------------------
>
> Key: OOZIE-1319
> URL: https://issues.apache.org/jira/browse/OOZIE-1319
> Project: Oozie
> Issue Type: Bug
> Reporter: Bowen Zhang
> Assignee: Robert Kanter
> Fix For: trunk
>
> Attachments: OOZIE-1319.patch, OOZIE-1319.patch, OOZIE-1319.patch,
> OOZIE-1319.patch, OOZIE-1319.patch, OOZIE-1319.patch, OOZIE-1319.patch,
> oozie-1319.patch
>
>
> In execute() of CoordJobGetReadyActionsJPAExecutor.java, once we retrieve the
> top item from a "LIFO" query result, we do not discard or delete the
> remaining items from the result list. As a result, the next time execute() is
> invoked, we will be retrieving the next item in line. Consequently, LAST_ONLY
> strategy will also execute all ready actions for a given coordinator job,
> making it no different than LIFO.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
