I have an issue after upgrading Typesense (Cloud) to 0.20. I have a “slug” field in an index for a blog. Looking up a specific post doesn’t work anymore since the upgrade to 0.20, and this relates to the length of the slug (words separated by hyphens). Anything longer than two words makes the query fail. Any query parameter I should add, or changes to the index I can make?

Hi Martin, could you give me an example of a search query (with all the search parameters used) that fails? Also, when you say "fails" does it return a non-200 HTTP error code or does it not return any results?

200 status but zero results.

As a test, could you remove all the hyphens in the search query and try searching as one long word?

When I shorten the query to a partial slug

open-access

I get three results.

So we currently drop all special characters when indexing and when searching. So

open-access-may-become-mandatory...

will get indexed as

openaccessmaybecomemandatory...

. Not ideal, but we plan to fix this in an upcoming release, so you can customize how special characters are indexed.

Yes. And the UI gives me the slug rather than for example the ID (a uuid).

Could you try setting slug as a faceted field, and then using filter_by:

slug:=slug-with-hyphens

?

Sure. But need to update schema, so needs a moment. Is

filter_by

better here than

query_by

?

Yeah, if you're looking for an exact match and for a single record, filter_by is a better approach

I'm able to reproduce this issue. There was indeed a regression on v0.20. The fix is easy enough and I can produce a RC build for you to test locally. If that goes fine, we can upgrade your cluster to the RC version. Does that sound good?

Thanks @Kishore Nallan but using

filter_by

, as suggested by @Jason Bosco fixes the issue for me.

Ok, sounds good. 👍

But thanks for looking into this. This might also affect others upgrading to 0.20.