ServiceControl 6.20: RavenDB search engine defaults and Corax to Lucene migration - #8477
Draft
ramonsmits wants to merge 1 commit into
Draft
ServiceControl 6.20: RavenDB search engine defaults and Corax to Lucene migration#8477ramonsmits wants to merge 1 commit into
ramonsmits wants to merge 1 commit into
Conversation
…on for ServiceControl 6.20 - New page servicecontrol/ravendb/search-engine.md: default engine per version, how Corax indexes are reported (custom check + start-up warning), when to migrate, per-index and whole-database migration procedures - Upgrade guide 6.19 to 6.20 - Troubleshooting page now links to the canonical procedure instead of duplicating it
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
1 participant
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.
Documents the RavenDB search engine change in ServiceControl 6.20 (Particular/ServiceControl#5833): new databases use Lucene, existing databases keep their engine, and indexes still on Corax are reported via a custom check and a start-up warning.
Changes
servicecontrol/ravendb/search-engine.md(Data Management menu): default engine per version, how Corax indexes are reported, when to migrate, per-index migration procedure (change engine → swap → lock) and the whole-database alternative (DB-level setting + reset), including the rebuild duration / ingestion impact caveats.servicecontrol/upgrades/6.19to6.20.md.servicecontrol/troubleshooting.md: the duplicated Corax → Lucene procedure now links to the canonical page.Notes
FailedMessageViewIndex,MessagesViewIndex) and the RavenDB Studio wording of the search engine / lock controls.