-
Notifications
You must be signed in to change notification settings - Fork 25.4k
Remove TSDB feature flag #88585
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove TSDB feature flag #88585
Conversation
Pinging @elastic/es-analytics-geo (Team:Analytics) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am so excited we open up such a great work to our users.
I only hesitate to release Downsampling ILM because it still half-baked. This will be released when #87269 gets merged.
actions.add(RollupIndexerAction.INSTANCE); | ||
actions.add(RollupAction.INSTANCE); | ||
} | ||
actions.add(RollupIndexerAction.INSTANCE); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe adding the rollup actions can move a few lines above in the Arrays.asList()
statement like everything else.
new NamedWriteableRegistry.Entry(XPackFeatureSet.Usage.class, XPackField.ARCHIVE, ArchiveFeatureSetUsage::new) | ||
new NamedWriteableRegistry.Entry(XPackFeatureSet.Usage.class, XPackField.ARCHIVE, ArchiveFeatureSetUsage::new), | ||
// TSDB Downsampling / Rollup | ||
new NamedWriteableRegistry.Entry(LifecycleAction.class, RollupILMAction.NAME, RollupILMAction::new) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SetPriorityAction.NAME, | ||
UnfollowAction.NAME, | ||
RolloverAction.NAME, | ||
ReadOnlyAction.NAME, | ||
IndexSettings.isTimeSeriesModeEnabled() ? RollupILMAction.NAME : null, | ||
RollupILMAction.NAME, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please remove RollupILMAction
completely from here and I will enable it in #87269
SetPriorityAction.NAME, | ||
UnfollowAction.NAME, | ||
ReadOnlyAction.NAME, | ||
SearchableSnapshotAction.NAME, | ||
AllocateAction.NAME, | ||
MigrateAction.NAME, | ||
FreezeAction.NAME, | ||
IndexSettings.isTimeSeriesModeEnabled() ? RollupILMAction.NAME : null | ||
).filter(Objects::nonNull).toList(); | ||
RollupILMAction.NAME |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please remove RollupILMAction
completely from here and I will enable it in #87269
new NamedXContentRegistry.Entry(LifecycleAction.class, new ParseField(RollupILMAction.NAME), RollupILMAction::parse) | ||
); | ||
} | ||
entries.add(new NamedXContentRegistry.Entry(LifecycleAction.class, new ParseField(RollupILMAction.NAME), RollupILMAction::parse)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please remove LifecycleAction
completely from here and I will enable it in #87269
I think I may also need to remove the |
So I spoke with @nik9000 and we agreed that we actually want to keep the feature flag around for now, and just expose different functionalities as and when they're ready. I'll close this PR and open a new one to expose synthetic source |
This commit makes TSDB available in 8.4.0 be default, and removes all references
to the feature flag it was previously hiding behind.