Mailing-List: contact commits-help@helix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@helix.apache.org
Date: Thu, 2 Oct 2014 08:21:34 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: commits@helix.incubator.apache.org
Message-ID: <JIRA.12745148.1412126071000.173564.1412238094358@Atlassian.JIRA>
In-Reply-To: <JIRA.12745148.1412126071000@Atlassian.JIRA>
References: <JIRA.12745148.1412126071000@Atlassian.JIRA>
 <JIRA.12745148.1412126071593@arcas>
Subject: [jira] [Commented] (HELIX-524) add getProgress() to Task interface
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

Github user brandtg commented on the pull request:

    https://github.com/apache/helix/pull/6#issuecomment-57597306
  
    Wait, that stuff's gone now? Ok never mind.
    
    Is persistence of the state of a running task completely necessary? (Like would JMX suffice?)


> add getProgress() to Task interface
> -----------------------------------
>
>                 Key: HELIX-524
>                 URL: https://issues.apache.org/jira/browse/HELIX-524
>             Project: Apache Helix
>          Issue Type: Improvement
>          Components: helix-core
>    Affects Versions: 0.6.4
>            Reporter: Hongbo Zeng
>             Fix For: 0.6.5
>
>
> Add a getProgress to the Task interface, this is very helpful for long running tasks, from which we know the status of a task and see if it's blocked. The return value is a double, ranging from 0 to 1.0, 1.0 indicates a task is finished


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