Introduce use_doc_values_sparse_index for the elastic/logs track
#740
Conversation
This file contains 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
salvatore-campagna
changed the title
use_doc_values_sparse_index for elastic/logs and tsdb tracksuse_doc_values_sparse_index for elastic/logs and tsdb tracks
salvatore-campagna
changed the title
use_doc_values_sparse_index for elastic/logs and tsdb tracksuse_doc_values_sparse_index for the elastic/logs track
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR introduces a new track parameter that controls the corresponding Elasticsearch setting:
index.mapping.use_doc_values_sparse_index.We will set this parameter for the
elastic/logstrack to evaluate the impact of using a doc values sparse index on thehost.nameand@timestampfields. The goal is to assess its effects on indexing throughput, query latency, and storage footprint. By enabling this parameter in controlled benchmarking environments, we aim to gain insights into its trade-offs and determine the most effective configuration for LogsDB.