typesense

Hi guys, I am searching the term `5980` in order to retrieve a document with a field value of `pp-nau-5980-1r-001` but it doesn’t find the document. Is this an expected behavior?

<@U02JNHS4FAL> This is indeed expected _default_ behavior, since Typesense only does a prefix search by default. Here's how to allow searches in the middle of strings (aka as infix search): <https://typesense.org/docs/guide/tips-for-searching-common-types-of-data.html#model-numbers-part-numbers-skus>

Hi <@U01NZ4D0LDD>, thank you! I will look into the
```token_separators```
I wish there was a way to update the schema easily..!

In the upcoming version you can change field definitions. We'll be supporting token_separators in a later version

What version supports field definitions updates?

If I want to add
```token_separators```
 I need to reinstall all the collection schema + data right?

But for other field definitions, here's how to change them in place: <https://github.com/typesense/typesense-website/blob/v0.23.0/docs-site/content/0.23.0/api/collections.md#update-or-alter-a-collection>

It cannot be done in the cloud interface, right?

Not at the moment. You can only schedule it for us to do it from our side. Just saw you scheduled an upgrade. Happy to fast track it to now if you'd like

When you link Typesense with Firebase it is crucial to have the possibility to update the schema otherwise it costs you  to trigger the backfill of all the firebase collections..

Oh I see, didn't know this. Good to know now!

We've queued up the upgrade. It should be done in 15 minutes.