Uses of Package
org.exoplatform.addons.documents.cleanup.model
Packages that use org.exoplatform.addons.documents.cleanup.model
Package
Description
-
Classes in org.exoplatform.addons.documents.cleanup.model used by org.exoplatform.addons.documents.cleanup.modelClassDescriptionA file (JCR nt:file node) qualifying for a cleanup action, as computed by a dry-run scan or a revalidation.Outcome of a purge operation (hard delete or versions purge) on one item.Result of re-evaluating a former candidate against the campaign criteria, distinguishing a node that disappeared, one that got exempted, one that no longer qualifies, one still qualifying (candidate != null), and an outcome that could NOT be computed (transient JCR read failure): an unknown outcome must never be mistaken for a spared/gone node — the execution skips the item (never deletes on doubt) and the freshness refresh leaves it untouched.
-
Classes in org.exoplatform.addons.documents.cleanup.model used by org.exoplatform.addons.documents.cleanup.rest.utilClassDescriptionOutcome of a bulk keep / un-keep: how many items were decided, and which ones failed with which reason.Domain model of a cleanup campaign.Domain model of a cleanup campaign item (one candidate file and its lifecycle).Delta between two campaigns' candidate sets, matched by node uuid.One group of a campaign's failed items: the failure message code and how many SKIPPED items carry it, computed by a single grouped aggregate query (the item rows are never loaded).Parameters of a cleanup campaign.One partition of the dry-run scan: the JCR subtree ONE reader thread walks, with its own state, its own path checkpoint and its own counters.Per-UNIT breakdown of a campaign's dry run: the state counts, the deepest attempt any unit has spent, and the units currently in flight.Per-user summary of the currently relevant campaign: their candidates and kept files during the grace period, their outcome once completed.
-
Classes in org.exoplatform.addons.documents.cleanup.model used by org.exoplatform.addons.documents.cleanup.serviceClassDescriptionOutcome of a bulk keep / un-keep: how many items were decided, and which ones failed with which reason.Domain model of a cleanup campaign.Domain model of a cleanup campaign item (one candidate file and its lifecycle).Delta between two campaigns' candidate sets, matched by node uuid.One group of a campaign's failed items: the failure message code and how many SKIPPED items carry it, computed by a single grouped aggregate query (the item rows are never loaded).Parameters of a cleanup campaign.One partition of the dry-run scan: the JCR subtree ONE reader thread walks, with its own state, its own path checkpoint and its own counters.Per-UNIT breakdown of a campaign's dry run: the state counts, the deepest attempt any unit has spent, and the units currently in flight.Per-user summary of the currently relevant campaign: their candidates and kept files during the grace period, their outcome once completed.
-
Classes in org.exoplatform.addons.documents.cleanup.model used by org.exoplatform.addons.documents.cleanup.storageClassDescriptionDomain model of a cleanup campaign.Item aggregates of one campaign (candidate count/bytes, reclaimed bytes, item-rows existence), computed by a single grouped query for a whole campaigns list instead of per-campaign aggregate queries.Domain model of a cleanup campaign item (one candidate file and its lifecycle).A file (JCR nt:file node) qualifying for a cleanup action, as computed by a dry-run scan or a revalidation.One bucket of a campaign comparison (persisting / new / gone): the item count and reclaimable-bytes sum computed by a single set-based aggregate query.One group of a campaign's failed items: the failure message code and how many SKIPPED items carry it, computed by a single grouped aggregate query (the item rows are never loaded).Nodes a scan batch could not EVALUATE, and the first failure that did it.Parameters of a cleanup campaign.Outcome of a purge operation (hard delete or versions purge) on one item.Result of re-evaluating a former candidate against the campaign criteria, distinguishing a node that disappeared, one that got exempted, one that no longer qualifies, one still qualifying (candidate != null), and an outcome that could NOT be computed (transient JCR read failure): an unknown outcome must never be mistaken for a spared/gone node — the execution skips the item (never deletes on doubt) and the freshness refresh leaves it untouched.One partition of the dry-run scan: the JCR subtree ONE reader thread walks, with its own state, its own path checkpoint and its own counters.Per-UNIT breakdown of a campaign's dry run: the state counts, the deepest attempt any unit has spent, and the units currently in flight.
-
Classes in org.exoplatform.addons.documents.cleanup.model used by org.exoplatform.addons.documents.cleanup.utilClassDescriptionDomain model of a cleanup campaign item (one candidate file and its lifecycle).Parameters of a cleanup campaign.Result of re-evaluating a former candidate against the campaign criteria, distinguishing a node that disappeared, one that got exempted, one that no longer qualifies, one still qualifying (candidate != null), and an outcome that could NOT be computed (transient JCR read failure): an unknown outcome must never be mistaken for a spared/gone node — the execution skips the item (never deletes on doubt) and the freshness refresh leaves it untouched.