Repository navigation
Conversation
…uzzy transpositions and fuzzyMaxExpansions (#12462)
Contributor
|
Tick the box to add this pull request to the merge queue (same as
|
This branch has not been deployed
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
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 two 26.12.1 full-text changes. Neither had a docs PR yet.
fuzzyMaxExpansionsindexed terms (default 50), across the whole type. Adds the newMETADATAkey to the options table, with the SQL and Java ways to set it.Pages:
how-to/data-modeling/full-text-index.adoc: the metadata options table, Phrase Queries, and Fuzzy Queries (new anchorfull-text-index-fuzzy). The old fuzzy example"databaSe"was a case variant, not an edit, so it was replaced.reference/mcp/mcp.adoc: the query-syntax table said phrase order is not enforced. It now gives the in-order rule and the fuzzy cap.