Skip to content
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

Merged

Conversation

Danielle9897
Copy link
Member

@Danielle9897 Danielle9897 commented Oct 7, 2024

Related issue:
https://issues.hibernatingrhinos.com/issue/RDoc-3052/Document-breaking-change-for-search-query-with-wildcards


  1. There is a new panel called Searching with wildcards in article: "Full-Text Search with Index"
    which includes detailed explanations + examples
  2. The 6.0 breaking changes page is updated
  3. This pr also contains some minor text fixes for other files under 6.0
    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

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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member Author

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.
Copy link
Member

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).

Copy link
Member Author

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 ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

@ppekrol ppekrol merged commit a9d6a5a into ravendb:master Oct 14, 2024
1 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants