[
https://issues.apache.org/jira/browse/SLING-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13759089#comment-13759089
]
Mike Hummel commented on SLING-3028:
------------------------------------
Hi, if you implement this feature. It would be a option to remember the last
modify time. The last time the progress was changed. This is the last 'sign of
live' and it can be used by humans to decide to stop or not.
Keep failed jobs depends in the use case. Some jobs are called very often and
it's ok if they fail. The result of is often a full queue of dead jobs and the
admin is not able to see the really important things. A log entry would be ok.
It should be configurable in some way or the job itself should give a hint for
that.
> 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
>
> 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
