You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@helix.apache.org by "Lei Xia (JIRA)" <ji...@apache.org> on 2016/08/26 22:29:21 UTC

[jira] [Closed] (HELIX-616) Change JobQueue to be subclass of Workflow instead of WorkflowConfig.

     [ https://issues.apache.org/jira/browse/HELIX-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lei Xia closed HELIX-616.
-------------------------
    Resolution: Fixed

> Change JobQueue to be subclass of Workflow instead of WorkflowConfig.
> ---------------------------------------------------------------------
>
>                 Key: HELIX-616
>                 URL: https://issues.apache.org/jira/browse/HELIX-616
>             Project: Apache Helix
>          Issue Type: Bug
>            Reporter: Lei Xia
>            Assignee: Lei Xia
>
> Currently, JobQueue is subclass of WorkflowConfig instead of Workflow.  It is not possible for client to create an initial queue with jobs in it.  It has to call create() to create an empty queue, and call enqueue() to add job to the queue. The problem is once create() call returns, the queue is already starts to run, if the queue is recurrent queue, the initial schedule run of the queue contains empty job set.



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