Issue with Typesense Search and Special Characters

gab

Hi, Whenever I do a search with a special character ex: q=")", documents are returned but some fields are wrong: all string fields that are not facets fields are returned undefined. String fields that are not facets fields are welle returned. Other fields are also well returned. It seems to be a bug. I can reproduce easily on my typesense cloud instance (v0.24.1.rc9)

Kishore Nallan

Can you please try on 0.24.1 GA? `0.24.1.rc9` is pre-release RC build on 0.24.1

gab

Ok I have just updated to 0.24.1 locally but I still have the same issue

gab

In addition to my previous notes, this issue is occuring whatever collections I'm querying

gab

I found that when there is no match at all (`matchLevel === 'none'`), `_highlightResult.value` (which is an object built from typesense client library) contains a string `"undefined"`. I don't know if it is because of wrong server response or wrong client parsing from Typsense client library. I'm using Typesense `v1.5.3`

gab

Jason Is it a known issue in typesense-js ?

Jason

gab `_highlightResult` is added by the typesense-instantsearch-adapter library, not typesense-js. Could you try upgrading to the latest version of the adapter?

gab

Ok I will give a try to go from `2.6.0` to `2.7.0`

gab

Jason There is still the same behavior with latest typesense-instantsearch-adapter library. Also this behavior can be seen on your interface ``

gab

Man just have to type for instance `+` or `)` in the search query field

gab

Jason

This message contains interactive elements.

Jason

Could you open the network inspector in the browser dev console, then do the search, look for a request to multi_search and then copy-as-curl and DM it to me?

Jason

Thank you!

Jason

This is a bug on the typesense-server side. We fixed a variation of this issue in a recent RC build of 0.25.0. Can we upgrade you to this build?

gab

Ok Thanks let's do this, can you also confirm me the exact version so I can align our local Docker image ?

Jason

Going to queue up an upgrade to `0.25.0.rc44`

gab

Does it makes sense to align our env with `0.25.0.rc41` ? It is the latest published Typesense docker tag I can find.

Jason

Yeah all the updates since then have been with vector search related features

Jason

But we’ll also publish docker tag for `0.25.0.rc44` shortly

Kishore Nallan

Let me publish rc44

Kishore Nallan

Published, please use that.

Jason

Cloud cluster upgrade just completed - I no longer see the issue. Could you confirm as well?

gab

Yep as far as I can see from typesense cloud interface it is now fixed. I will check on our production env where I had to apply some hack to not display the undefined value. Thanks a lot

gab

Kishore Nallan thanks :+1: