You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Rohini Palaniswamy (JIRA)" <ji...@apache.org> on 2015/08/11 22:28:47 UTC
[jira] [Commented] (OOZIE-2228) Statustransit service doesn't pick
bundle with suspend status
[ https://issues.apache.org/jira/browse/OOZIE-2228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14682430#comment-14682430 ]
Rohini Palaniswamy commented on OOZIE-2228:
-------------------------------------------
Can you change the comment message
from
//If bundle is pushed then timestamp will be set.
to
//If bundle is paused then timestamp will be set.
> Statustransit service doesn't pick bundle with suspend status
> -------------------------------------------------------------
>
> Key: OOZIE-2228
> URL: https://issues.apache.org/jira/browse/OOZIE-2228
> Project: Oozie
> Issue Type: Bug
> Reporter: Purshotam Shah
> Assignee: Purshotam Shah
> Attachments: OOZIE-2228-V1.patch, OOZIE-2228-V2.patch, OOZIE-2228-V3.patch
>
>
> {code}
> @NamedQuery(name = "GET_BUNDLE_IDS_FOR_STATUS_TRANSIT", query = "select DISTINCT w.id from BundleActionBean a , BundleJobBean w where a.lastModifiedTimestamp >= :lastModifiedTime and w.id = a.bundleId and (w.statusStr = 'RUNNING' OR w.statusStr = 'RUNNINGWITHERROR' OR w.statusStr = 'PAUSED' OR w.statusStr = 'PAUSEDWITHERROR' OR w.pending = 1)"),
> {code}
> Can be reproduced easily.
> 1. suspend coord, bundle goes to suspend by StatusTransitService.
> 2. resume coord, bundle remains in suspend state.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)