Interface RepushCandidateTrigger

All Known Implementing Classes:
VersionStalenessTrigger

public interface RepushCandidateTrigger
RepushCandidateTrigger defines a condition that can independently justify scheduling a store for log compaction via repush.

Unlike RepushCandidateFilter which uses AND logic (all filters must pass), triggers use OR logic: if any trigger returns true, the store is scheduled for compaction (provided all prerequisite filters also pass).

Examples of triggers include version staleness and high duplicate key ratios.

See Also:
  • Method Summary

    Modifier and Type
    Method
    Description
    boolean
    apply(String clusterName, StoreInfo store)
     
  • Method Details