Allow re-enabling of sparse indexes on @timestamp field in LogsDB #136754
+222
−23
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Once this is merged, we should update the logsdb rally tracks to include the index setting |
|
Pinging @elastic/es-storage-engine (Team:StorageEngine) |
romseygeek
added
the
auto-merge-without-approval
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Updates the relevant IndexVersion so that we can re-enable the
index.mapping.use_doc_values_skippersetting for logsdbnightly runs and see what effect it has.
Also includes changes to the filter-by-filter aggregation optimization
to allow it to inspect doc value skippers as well as points to work out
if it is worth enabling.