[
https://issues.apache.org/jira/browse/OOZIE-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13981526#comment-13981526
]
Robert Kanter commented on OOZIE-1319:
--------------------------------------
The second part of {{handleLastOnly()}} actually retrieves all READY or WAITING
actions already created and sets them to SKIPPED. In other words, when
materializing actions, if it sees any previously materialized actions
READY/WAITING, they'll be set to SKIPPED. So in those two scenarios, I believe
it will actually work correctly.
The only time we need to set an action to SKIPPED is if its READY/WAITING and a
newer action gets materialized. So I think putting the code in
CoordMaterializeTransitionXCommand makes sense with this in mind. I think the
issue now is that it doesn't take into account if we're materializing future
actions or not, in which case, it needs to not do this behavior.
> "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
> Attachments: 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)
