Keep the search engine configured on an index when deploying index definitions - #5950
Merged
Merged
Conversation
…finitions (#5946) * Keep the search engine configured on an index when deploying index definitions Operators migrating indexes from Corax to Lucene in RavenDB Studio store the search engine in the index configuration. ServiceControl deployed its index definitions without it, so RavenDB built a side-by-side replacement that fell back to the database default, which is Corax for databases created before 6.20. Unless the index was locked, every start-up reset migrated indexes back to Corax. Index definitions are now deployed carrying over the search engine configured on the existing index (or on its pending replacement). A migrated index no longer needs to be locked, still receives definition changes, and a pending Corax replacement created by earlier versions is discarded at start-up. ---- * Create new indexes with Lucene and respect search engines set in code Indexes that don't exist on the server yet are now created with the Lucene search engine pinned on the index, also in existing databases that still default to Corax. A search engine set explicitly in an index definition, through SearchEngineType or Configuration, takes precedence over the one on the server. Expand the comments to explain why the search engine has to be resolved before deploying the index definitions. --------- Co-authored-by: Ramon Smits <ramon.smits@gmail.com> (cherry picked from commit 53e287d)
mauroservienti
approved these changes
Oct 5, 2026
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
2 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.
Backport to
release-6.21of:Fixes:
Cherry-pick of 53e287d, no conflicts. The
IndexSetupTestspass on this branch: Audit 13/13, Primary 1/1.See #5946 for the problem, the fix and the verification of the upgrade paths.