[
https://issues.apache.org/jira/browse/HELIX-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14156118#comment-14156118
]
ASF GitHub Bot commented on HELIX-524:
--------------------------------------
Github user kanakb commented on the pull request:
https://github.com/apache/helix/pull/6#issuecomment-57588016
I like this in general, but I have a couple questions/comments:
* This is an interface change. Is there a way we can provide this
functionality without requiring that all existing task implementations be
rewritten?
* What is the persistence story (if any)? Who calls getProgress?
> 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)
