Module org.elasticsearch.xcore
Package org.elasticsearch.xpack.core.ilm
Class TimeseriesLifecycleType
java.lang.Object
org.elasticsearch.xpack.core.ilm.TimeseriesLifecycleType
- All Implemented Interfaces:
NamedWriteable,Writeable,LifecycleType
Represents the lifecycle of an index from creation to deletion. A
TimeseriesLifecycleType is made up of a set of Phases which it will
move through. Soon we will constrain the phases using some kinda of lifecycle
type which will allow only particular Phases to be defined, will
dictate the order in which the Phases are executed and will define
which LifecycleActions are allowed in each phase.-
Nested Class Summary
Nested classes/interfaces inherited from interface org.elasticsearch.common.io.stream.Writeable
Writeable.Reader<V>, Writeable.Writer<V> -
Field Summary
FieldsModifier and TypeFieldDescriptionstatic final TimeseriesLifecycleTypeWe define the following actions as read-only, because either they explicitly set an index to be read-only (read-only, downsample, searchable snapshot, shrink) or adding data during their operation could be tricky, like force-merge.static final String -
Method Summary
Modifier and TypeMethodDescriptiongetOrderedActions(Phase phase) getOrderedPhases(Map<String, Phase> phases) static booleanvoidvalidate(Collection<Phase> phases) validates whether the specifiedphasesare valid for this policy instance.static StringValidates that phases don't configure a min_age that is smaller than a previous phase (which can be confusing to users)voidwriteTo(StreamOutput out)
-
Field Details
-
INSTANCE
-
TYPE
- See Also:
-
ORDERED_VALID_PHASES
-
ORDERED_VALID_HOT_ACTIONS
-
ORDERED_VALID_WARM_ACTIONS
-
ORDERED_VALID_COLD_ACTIONS
-
ORDERED_VALID_FROZEN_ACTIONS
-
ORDERED_VALID_DELETE_ACTIONS
-
READ_ONLY_ACTIONS
We define the following actions as read-only, because either they explicitly set an index to be read-only (read-only, downsample, searchable snapshot, shrink) or adding data during their operation could be tricky, like force-merge. Finally, delete is also considered a read-only operation because any data that would be added would be removed asap. These actions are used to determine if we will create a new past backing index in a TSDB to cover documents with older timestamps than the time frame covered by existing indices. -
ACTIONS_CANNOT_FOLLOW_SEARCHABLE_SNAPSHOT
-
-
Method Details
-
writeTo
- Specified by:
writeToin interfaceWriteable- Throws:
IOException
-
getWriteableName
- Specified by:
getWriteableNamein interfaceNamedWriteable
-
getOrderedPhases
- Specified by:
getOrderedPhasesin interfaceLifecycleType- Returns:
- the first phase of this policy to execute
-
shouldInjectMigrateStepForPhase
-
getOrderedActions
- Specified by:
getOrderedActionsin interfaceLifecycleType
-
validate
Description copied from interface:LifecycleTypevalidates whether the specifiedphasesare valid for this policy instance.- Specified by:
validatein interfaceLifecycleType- Parameters:
phases- the phases to verify validity against
-
validateMonotonicallyIncreasingPhaseTimings
Validates that phases don't configure a min_age that is smaller than a previous phase (which can be confusing to users)
-