Package org.exoplatform.addons.documents.cleanup.util


package org.exoplatform.addons.documents.cleanup.util
  • Classes
    Class
    Description
    Single definition of the physical drive layout swept by cleanup campaigns (scan roots, drive-root depths) and of the cleanup-wide static constants.
    Pure, JCR-free evaluation of the cleanup candidate criterion: a node under an excluded path prefix is never a candidate DELETE: created AND last modified older than the campaign period, and content size above the floor PURGE_VERSIONS: the file owns at least one PURGEABLE version — see CleanupCriterionEvaluator.selectVersionsToRemove(java.util.Map<java.lang.String, java.lang.Long>, java.lang.String, java.lang.String, org.exoplatform.addons.documents.cleanup.model.CleanupParams, long) for the union of the age rule and the count rule that defines the removal set — and the size of that removal set is above the floor An exemption (exo:cleanupExemption mixin) is deliberately NOT evaluated here: an exempted node still qualifying by these criteria is emitted as an exempted-flagged CleanupCandidate, so it stays visible as 'Kept' in every campaign.
    Single definition of the throughput ETA of a cleanup worker, shared by the dry-run scan and the execution purge — the two workers used to carry the very same arithmetic verbatim, so a change (or a regression) in one of them silently diverged from the other.
    Single definition of the owner display name of a cleanup item, shared by the REST DTO builder and the CSV report so the exported name and the one shown in the UI can never disagree.
    Single definition of the revalidation-outcome to item-state mapping, shared by the freshness refresh (observation glue) and the execution-time revalidation so both stay strictly identical.
    The ONE definition of what an item's action reclaims, in Java.
    Renders a purge failure into the compact diagnostic persisted in the item's FAILURE_DETAIL column — never a full printStackTrace.