Split delete/70_tsdb.yml for synthetic_id TRUE/FALSE#142932
Merged
burqen merged 3 commits intoelastic:mainfrom Feb 26, 2026
Merged
Split delete/70_tsdb.yml for synthetic_id TRUE/FALSE#142932burqen merged 3 commits intoelastic:mainfrom
burqen merged 3 commits intoelastic:mainfrom
Conversation
burqen
added
>test
Collaborator
|
Pinging @elastic/es-storage-engine (Team:StorageEngine) |
- Original 70_tsdb: skip when cluster has synthetic_id feature - 71_tsdb_synthetic_id_false: explicit synthetic_id false - 72_tsdb_synthetic_id_true: explicit synthetic_id true, synthetic _id Co-authored-by: Cursor <cursoragent@cursor.com>
burqen
force-pushed
the
ap/2026.02.24.synthetic-id-fix-yml-delete-70
branch
from
75b379f to
e389a8d
Compare
16 tasks
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
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.
Same intention and procedure as #142770
Intention is to
delete/70_tsdb.ymlnot fail when enablingindex.mapping.synthetic_idby defaultdelete/70_tsdb.ymlboth with and withoutindex.mapping.synthetic_iddelete/70_tsdb.ymlhas hard coded ids. When enablingindex.mapping.synthetic_id, the id generation changes and those hard coded ids are no longer valid. We completely skip70_tsdbif cluster has synthetic id feature.If the cluster has synthetic id feature we run both and
71_tsdb_synthetic_id_falseand72_tsdb_synthetic_id_true. Both of which are copies of70_tsdbbut withsynthetic_idexplicitly set to false/true. In72_tsdb_synthetic_id_true, the ids are updated to fit the new synthetic ids.