TLDR gab faced an issue with Typesense when searching with special characters. Jason and Kishore Nallan provided support and identified the issue as a bug. The problem was resolved after upgrading to `0.25.0.rc44`.
Can you please try on 0.24.1 GA? `0.24.1.rc9` is pre-release RC build on 0.24.1
Ok I have just updated to 0.24.1 locally but I still have the same issue
In addition to my previous notes, this issue is occuring whatever collections I'm querying
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`
Jason Is it a known issue in typesense-js ?
gab `_highlightResult` is added by the typesense-instantsearch-adapter library, not typesense-js. Could you try upgrading to the latest version of the adapter?
Ok I will give a try to go from `2.6.0` to `2.7.0`
Jason There is still the same behavior with latest typesense-instantsearch-adapter library.
Also this behavior can be seen on your interface `
Man just have to type for instance `+` or `)` in the search query field
This message contains interactive elements.
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?
Thank you!
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?
Ok Thanks let's do this, can you also confirm me the exact version so I can align our local Docker image ?
Going to queue up an upgrade to `0.25.0.rc44`
Does it makes sense to align our env with `0.25.0.rc41` ? It is the latest published Typesense docker tag I can find.
Yeah all the updates since then have been with vector search related features
But we’ll also publish docker tag for `0.25.0.rc44` shortly
Let me publish rc44
Published, please use that.
Cloud cluster upgrade just completed - I no longer see the issue. Could you confirm as well?
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
Kishore Nallan thanks :+1:
gab
Tue, 04 Jul 2023 15:43:55 UTCHi, 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)