You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Victor Saar (JIRA)" <ji...@apache.org> on 2013/09/03 15:32:53 UTC

[jira] [Commented] (SLING-3028) Support for progress tracking of jobs

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

Victor Saar commented on SLING-3028:
------------------------------------

bq. I have the tendency to keep failed jobs forever - but have an API to retry or remove them. A scheduled configuration might always lead to the problem that failed jobs are removed before someone took an action.

+1

But still, as Jeff and I mentioned already, it would be useful to keep jobs even if they succeeded. Having to come up with something else for that scenario (e.g. a separate log) kind of defeats the purpose of this whole issue;).
                
> 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