[
https://issues.apache.org/jira/browse/HELIX-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14057726#comment-14057726
]
Hudson commented on HELIX-416:
------------------------------
UNSTABLE: Integrated in helix #1256 (See
[https://builds.apache.org/job/helix/1256/])
[HELIX-416] Support recurring scheduled tasks (kanak: rev
0f79187d31c8769a668ba81f8bcc5e5831c659da)
* helix-core/src/main/java/org/apache/helix/task/WorkflowContext.java
* helix-core/src/main/java/org/apache/helix/task/WorkflowConfig.java
* helix-core/src/main/java/org/apache/helix/task/TaskDriver.java
* helix-core/src/main/java/org/apache/helix/task/TaskRebalancer.java
* helix-core/src/main/java/org/apache/helix/task/beans/WorkflowBean.java
* helix-core/src/main/java/org/apache/helix/task/TaskConstants.java
* helix-core/src/main/java/org/apache/helix/task/Workflow.java
* helix-core/src/main/java/org/apache/helix/task/ScheduleConfig.java
* helix-core/src/main/java/org/apache/helix/task/TaskUtil.java
> Make the task framework more extensible
> ---------------------------------------
>
> Key: HELIX-416
> URL: https://issues.apache.org/jira/browse/HELIX-416
> Project: Apache Helix
> Issue Type: Improvement
> Reporter: Kanak Biscuitwala
> Assignee: Kanak Biscuitwala
>
> The current task framework is good for the use case where we want to run
> identical tasks according to a target resource's assignment. However,
> realistically, we want things like:
> - Each task partition can correspond to a different task
> - Some task groups shouldn't have a status corresponding to them; they should
> be able to take on additional task partitions dynamically
> - There should be some notion of independence, in that a target resource (or
> lack thereof) can say that arbitrary task partitions can be assigned to
> arbitrary live participants
> This is a pretty involved undertaking, so this will encompass some subtasks.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
