helix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HELIX-589) Delete job API throws NPE if the job does not exist in last scheduled workflow
Date Sun, 05 Apr 2015 20:29:35 GMT

    [ https://issues.apache.org/jira/browse/HELIX-589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14396380#comment-14396380
] 

ASF GitHub Bot commented on HELIX-589:
--------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/helix/pull/22


> Delete job API throws NPE if the job does not exist in last scheduled workflow
> ------------------------------------------------------------------------------
>
>                 Key: HELIX-589
>                 URL: https://issues.apache.org/jira/browse/HELIX-589
>             Project: Apache Helix
>          Issue Type: Bug
>            Reporter: Karthiek
>
> When trying to delete a job from a recurrent job queue, Helix throws NPE if the job does
not exist in last scheduled workflow.
> java.lang.IllegalArgumentException: Could not remove job BackupJob_MailboxDB from DAG
of queue BackupJobQueue_ESPRESSO_CHO_1_SCHEDULED_0
>         at org.apache.helix.task.TaskDriver.removeJobFromDag(TaskDriver.java:411)
>         at org.apache.helix.task.TaskDriver.deleteJobFromScheduledQueue(TaskDriver.java:345)
>         at org.apache.helix.task.TaskDriver.deleteJob(TaskDriver.java:303)
> It is possible for a user to add and immediately delete the job before the next workflow
is scheduled. Helix should accommodate this case and check if the job exists in last scheduled
workflow before trying to delete it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message