-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RDoc-3052 Document breaking change for search query with wildcards #1919
RDoc-3052 Document breaking change for search query with wildcards #1919
Conversation
When setting a [custom analyzer](../../indexes/using-analyzers#creating-custom-analyzers) in your index to tokenize field content, | ||
then when querying the index, the search terms in the query will be processed according to the custom analyzer's logic. | ||
|
||
The `*` will remain in the terms if the custom analyzer allows it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- except
startsWith
queries likeFran*
:
https://issues.hibernatingrhinos.com/issue/RavenDB-22989/Adjust-Lucene-search-method-startsWith
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
##### Behavior for `6.0` and up: | ||
|
||
Once wildcards are stripped by the analyzer, we no longer add them back before sending the term to the search engine. | ||
The search terms sent to the search engine are solely based on the transformations applied by the analyzer used in the index. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Corax will match the behavior only for newly built indexes (ravendb/ravendb#19337).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@maciejaszyk
if you "reset" the index - will behavior match ?
or - is it only for newly "created" Corax indexes ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
Related issue:
https://issues.hibernatingrhinos.com/issue/RDoc-3052/Document-breaking-change-for-search-query-with-wildcards
Searching with wildcards
in article: "Full-Text Search with Index"which includes detailed explanations + examples
The following are the relevant files to be reviewed:
C#:
@maciejaszyk pls review:
Documentation/6.0/Raven.Documentation.Pages/indexes/querying/searching.dotnet.markdown
Documentation/6.0/Samples/csharp/Raven.Documentation.Samples/Indexes/Querying/Searching.cs
Documentation/6.0/Raven.Documentation.Pages/migration/server/server-breaking-changes.markdown
Node.js:
@ml054 pls review:
Documentation/6.0/Raven.Documentation.Pages/indexes/querying/searching.js.markdown
Documentation/6.0/Samples/nodejs/indexes/querying/searching.js