org.apache.druid.server.coordinator.rules

Interface Rule

All Known Implementing Classes:

BroadcastDistributionRule, DropRule, ForeverBroadcastDistributionRule, ForeverDropRule, ForeverLoadRule, IntervalBroadcastDistributionRule, IntervalDropRule, IntervalLoadRule, LoadRule, PeriodBroadcastDistributionRule, PeriodDropBeforeRule, PeriodDropRule, PeriodLoadRule

public interface Rule

Method Summary

Modifier and Type	Method and Description
boolean	appliesTo(DataSegment segment, org.joda.time.DateTime referenceTimestamp)
boolean	appliesTo(org.joda.time.Interval interval, org.joda.time.DateTime referenceTimestamp)
String	getType()
CoordinatorStats	run(DruidCoordinator coordinator, DruidCoordinatorRuntimeParams params, DataSegment segment) DruidCoordinatorRuntimeParams.getUsedSegments() must not be called in Rule's code, because the used segments are not specified for the DruidCoordinatorRuntimeParams passed into Rule's code.

Method Detail

getType

String getType()

appliesTo

boolean appliesTo(DataSegment segment,
                  org.joda.time.DateTime referenceTimestamp)

appliesTo

boolean appliesTo(org.joda.time.Interval interval,
                  org.joda.time.DateTime referenceTimestamp)

run

CoordinatorStats run(DruidCoordinator coordinator,
                     DruidCoordinatorRuntimeParams params,
                     DataSegment segment)

DruidCoordinatorRuntimeParams.getUsedSegments() must not be called in Rule's code, because the used segments are not specified for the DruidCoordinatorRuntimeParams passed into Rule's code. This is because DruidCoordinatorRuntimeParams entangles two slightly different (nonexistent yet) abstractions: "DruidCoordinatorHelperParams" and "RuleParams" which contain params that only DruidCoordinatorHelpers and Rules need, respectively. For example, ReplicationThrottler needs to belong only to "RuleParams", but not "DruidCoordinatorHelperParams". The opposite for the collection of used segments. See https://github.com/apache/druid/issues/7228