Please help were blocked from production because a value like 123456 won’t be hit if we query 0123456

By default, Typesense only returns matches where the search term occurs in the beginning of strings (this is called a prefix search) If you want to search in the middle of strings, it’s called an infix search and you can enable it by setting infix:true in the field definition in the collection schema, and then set infix=true as a search parameter

All infix can be prefix?

Just to make sure we’re on the same page, could you update this code snippet, with your schema settings, add a few sample docs and update the search query to replicate the issue? https://gist.github.com/jasonbosco/7c3432713216c378472f13e72246f46b

Ok I commented,

Hi Daren, we might not always be able to support typos at the start of the query because that tend to involve almost all the words in your dataset. Infix index won't help here if you are adding a letter at the start.

hmmm

I'll have to get back to you. Possible to give us a day or so?

Yeah

Copy-pasting the snippet from the GitHub comment here:

export TYPESENSE_API_KEY=xyz

curl "<http://localhost:8108/debug>" \
       -H "X-TYPESENSE-API-KEY: ${TYPESENSE_API_KEY}"


curl "<http://localhost:8108/collections>" \
       -X POST \
       -H "Content-Type: application/json" \
       -H "X-TYPESENSE-API-KEY: ${TYPESENSE_API_KEY}" \
       -d '{
         "name": "numbers",
         "fields": [
           {"name": "handle", "type": "string", infix:true , index:true},
  
         ],
         "default_sorting_field": ""
       }'
       
curl "<http://localhost:8108/collections/companies/documents/import?action=create>" \
        -H "X-TYPESENSE-API-KEY: ${TYPESENSE_API_KEY}" \
        -H "Content-Type: text/plain" \
        -X POST \
        -d '{"id": "1","handle": "23456789"}
            {"id": "2","handle": "9172837237"}'
            
curl "<http://localhost:8108/multi_search>" \
        -X POST \
        -H "Content-Type: application/json" \
        -H "X-TYPESENSE-API-KEY: ${TYPESENSE_API_KEY}" \
        -d '{
          "searches": [
            {
              "collection": "numbers",
              "q": "123456789",
              "query_by": "handle"
            }
          ]
        }'

I took a look into this and we can certainly support this. I'm going to try a few approaches now and figure out the optimized way to achieve this. Will keep you posted.

How’s it going? U don’t have to go crazy on it, algolia only allows 1-2 typos on prefix

Almost there. Writing tests, will clean up, merge and share a build in a day or so.

Sounds good, I will deploy tomorrow night then :)

Hi Daren, I'm done with the changes and I have a build ready for you. Since we are in code freeze for v0.25 release and 0.26 has other unrelated changes, I created a build just with this change on the 0.25 RC branch that we have. Let me know how you deploy Typesense and I can share the build with you.

I’m running it locally on home brew, for production I can see version 0.25.0rc43 in the cloud console. I’d like to test it locally

We typically don’t publish RC builds for mac…

Sure

This particular feature is on

0.25.0.rct46

- this is a build that we would have to upgrade you to from our side. Would you like us to do that?

I’d like to test locally before I do anything

The docker tag is

typesense/typesense:0.25.0.rct46

Working on my end. Will let you know when I’m deployed

Great! Let me know when you’d like to upgrade your cloud cluster to this build.