Document versions accumulate over time. For example, every publish action creates one new version. Given enough time this often causes millions of often unneeded versions. To counteract this amassment of versions the Version Store schedules a job based on a cron expression to declutter the situation. We call this job execution version decluttering. Refer to the Version Store Configuration for all configuration options.
A version is considered obsolete if one of the following conditions is met:
- The number of versions per document is exceeded.
- The maximum age of a version is exceeded.
You can configure both conditions on a global level and on a node type level. On a document level you also have the ability to overwrite the maximum number of versions using the property sophora:maxVersionsToKeep. By default no such limit is set.
The maximum number of versions via the property sophora:maxVersionsToKeep has to be smaller than the global or node type level.
