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

Carsten Ziegeler commented on SLING-3028:
-----------------------------------------

This depends :) If I understand you correctly, you say that you have an ETA for 
each step, right?
The steps are intended to be used when you don't know the eta but you know the 
progress, so for example if you have ten steps to do, you can calculate a 
percentage once each step is finished. Of course assuming that each step takes 
the same time - but that's as good as having a rough ETA.
I've looked at other progress tracker api's and they usually provide both ways
                
> Support for progress tracking of jobs
> -------------------------------------
>
>                 Key: SLING-3028
>                 URL: https://issues.apache.org/jira/browse/SLING-3028
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Victor Saar
>              Labels: jobs
>         Attachments: SLING-3028.patch
>
>
> For long-running jobs, it would be useful to have some means to track 
> progress, which can be shown in a console for the user. This should include 
> the following:
> * ETA
> * Completeness value computed from (optional, defaults to 1.0) max and 
> current value (e.g. 42% or 23/100)
> * Log output stream for detailed progress information
> * Failure reason in case job failed
> AFAICS this requires a few changes to the existing implementation:
> * Jobs need additional support for setting properties, e.g. max and current 
> progress value
> * Jobs need to be kept at least for a while after they completed/failed to 
> give access to failure information/log stream

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to