[
https://issues.apache.org/jira/browse/SLING-9985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17246012#comment-17246012
]
Dan Klco commented on SLING-9985:
---------------------------------
Good point, yes. In fact, I think it would make sense to create a separate "JCR
Repository Maintenance" bundle and pull out the maintenance jobs for running
the DataStore Garbage Collection and SegmentStore Compaction tasks out of Sling
CMS as well as a Felix HealthCheck to make sure that the jobs have run and are
successful.
That way any downstream implementation could leverage these features.
I'll start working on that in the whiteboard.
> CMS - Add Version Cleanup Job
> -----------------------------
>
> Key: SLING-9985
> URL: https://issues.apache.org/jira/browse/SLING-9985
> Project: Sling
> Issue Type: Improvement
> Components: App CMS
> Affects Versions: App CMS 0.16.2
> Reporter: Dan Klco
> Assignee: Dan Klco
> Priority: Major
> Fix For: App CMS 1.0.2
>
>
> Currently, versions created in Sling CMS don't get automatically purged which
> can cause excessive repository growth if not cleaned up. The job should
> support deleting older versions based on a limit on the number of versions
> and removing versions on deleted resources after a specified time period.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
