helix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Francis Unson (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HELIX-416) Make the task framework more extensible
Date Thu, 14 Aug 2014 00:20:12 GMT

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

John Francis Unson updated HELIX-416:

    Sprint: Scrumban #1

> 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

View raw message