[ https://issues.apache.org/jira/browse/HELIX-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14164230#comment-14164230 ]
ASF GitHub Bot commented on HELIX-524: -------------------------------------- Github user dayzzz commented on the pull request: https://github.com/apache/helix/pull/6#issuecomment-58433144 Sorry for the delay. Are there any customers outside the Espresso team? If we are the only customer right now, it would not be too costly to update the implementation with the interface. Making the getProgress into the interface has a good thing that it naturally goes into TaskRunner and we don't need to do something like "instance of ProgressReportingTask" and then call the getProgress, or a subclass of TaskRunner which is specific for ProgressReportingTask and call the 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)