You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@helix.apache.org by "Kanak Biscuitwala (JIRA)" <ji...@apache.org> on 2014/04/28 23:19:26 UTC
[jira] [Updated] (HELIX-422) Workflow shouldn't be a requirement
for tasks
[ https://issues.apache.org/jira/browse/HELIX-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kanak Biscuitwala updated HELIX-422:
------------------------------------
Description: We should be able to specify requirements for a task, even if not within the confines of a workflow. Alternatively, we should make it easier to make a single-job workflow. (was: We should be able to specify requirements for a task, even if not within the confines of a workflow.)
> Workflow shouldn't be a requirement for tasks
> ---------------------------------------------
>
> Key: HELIX-422
> URL: https://issues.apache.org/jira/browse/HELIX-422
> Project: Apache Helix
> Issue Type: Sub-task
> Reporter: Kanak Biscuitwala
> Assignee: Kanak Biscuitwala
>
> We should be able to specify requirements for a task, even if not within the confines of a workflow. Alternatively, we should make it easier to make a single-job workflow.
--
This message was sent by Atlassian JIRA
(v6.2#6252)