[
https://issues.apache.org/jira/browse/SLING-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756656#comment-13756656
]
Carsten Ziegeler commented on SLING-3028:
-----------------------------------------
Ok, so what about keeping failed jobs and adding a configuration to a queue
whether successful jobs should be kept as well - this can be used as a first
configuration option, to keep the number of jobs kept to a minimum.
We'll then enhance the job manager api to query for failed and successful jobs
- I think we can use the already existing api of the JobManager and just need
to add two values to the QueryType enumeration. The same api can be used to
delete these jobs permanently from the repository.
We might need a new method to reschedule a failed job.
So let's think about the api to set the progress and give log statements
> 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
