You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just upgraded to 26.0 and had to rollback to 0.25.2. I couldn't find anything in the docs about this. But when I'm searching against many fields with infix: "always" and at least one field doesn't have it enabled it will fail with "Could not find field in the infix index. Make sure to enable infix search by specifying "infix": true in the schema."
Steps to reproduce
Add two fields, only one with infix search.
Perform a search against the two fields with infix: "always"
Expected Behavior
To perform the infix search only in the fields with infix search, as with the 0.25.2 version.
Actual Behavior
An error.
Metadata
Typesense Version:
26.0
OS:
Docker image
P.S.: I love typesense!
The text was updated successfully, but these errors were encountered:
solvingproblemswithtechnology
changed the title
Regression "Make sure to enable infix search by specifying" when only part of the fields have the infix index enabled
Bug in 26, 0.25.2 working fine: "Make sure to enable infix search by specifying" when only part of the fields have the infix index enabled
Apr 16, 2024
Description
I just upgraded to 26.0 and had to rollback to 0.25.2. I couldn't find anything in the docs about this. But when I'm searching against many fields with infix: "always" and at least one field doesn't have it enabled it will fail with "Could not find
field
in the infix index. Make sure to enable infix search by specifying"infix": true
in the schema."Steps to reproduce
Add two fields, only one with infix search.
Perform a search against the two fields with infix: "always"
Expected Behavior
To perform the infix search only in the fields with infix search, as with the 0.25.2 version.
Actual Behavior
An error.
Metadata
Typesense Version:
26.0
OS:
Docker image
P.S.: I love typesense!
The text was updated successfully, but these errors were encountered: