Refactor AliasOrIndex abstraction. #54394
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport of #53982
In order to prepare the
AliasOrIndex
abstraction for the introduction of data streams,the abstraction needs to be made more flexible, because currently it really can be only
an alias or an index.
AliasOrIndex
toIndexAbstraction
.IndexAbstraction.Type
enum to indicate what aIndexAbstraction
instance is.isAlias()
method that returns a boolean with thegetType()
method that returns the new Type enum.getWriteIndex()
up from theIndexAbstraction.Alias
to theIndexAbstraction
interface.getAliasName()
up from theIndexAbstraction.Alias
to theIndexAbstraction
interface and renamed it togetName()
.IndexAbstraction.Alias
by just checking thegetType()
method.Relates to #53100