[
https://issues.apache.org/jira/browse/SLING-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13794543#comment-13794543
]
Stefan Seifert commented on SLING-3028:
---------------------------------------
i commented on the seperate ticktes. for the other points:
* 7a-7c: you are right, these transition states would be a different state view
from the point of the consumer pov, not from the engine pov. so we do not need
to consider it in the JobState enum as discussed in SLING-3169. if we required
it we could add it later on, but lets start with the current API and make it
not too complicated for now.
* 8: you already created SLING-3171
* 9: i've created SLING-3172 for it
* 10: i've created SLING-3173 for it
done for this ticket
> Support for progress tracking of jobs and keeping jobs
> ------------------------------------------------------
>
> Key: SLING-3028
> URL: https://issues.apache.org/jira/browse/SLING-3028
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Reporter: Victor Saar
> Assignee: Carsten Ziegeler
> Labels: jobs
> Fix For: Extensions Event 3.3.0
>
> 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 was sent by Atlassian JIRA
(v6.1#6144)
