Hi Whenever I do a search with a special character ex q= doc typesense #community-help

Hi, Whenever I do a search with a special characte...

gab gab

07/04/2023, 3:43 PM

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)

🙌 1

✅ 1

Kishore Nallan

07/04/2023, 3:48 PM

Can you please try on 0.24.1 GA?

0.24.1.rc9

is pre-release RC build on 0.24.1

gab gab

07/04/2023, 4:11 PM

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

gab gab

07/04/2023, 4:13 PM

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

gab gab

07/04/2023, 5:19 PM

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 gab

07/05/2023, 8:33 AM

@Jason Bosco Is it a known issue in typesense-js ?

Jason Bosco

07/05/2023, 3:04 PM

@gab 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 gab

07/05/2023, 3:07 PM

Ok I will give a try to go from

2.6.0

2.7.0

gab gab

07/05/2023, 3:11 PM

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

<https://cloud.typesense.org/clusters/../documents/search>

gab gab

07/05/2023, 3:11 PM

Man just have to type for instance

in the search query field

gab gab

07/05/2023, 3:14 PM

message has been deleted

Jason Bosco

07/05/2023, 3:14 PM

This message contains interactive elements.

Jason Bosco

07/05/2023, 3:15 PM

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 Bosco

07/05/2023, 3:31 PM

Thank you!

Jason Bosco

07/05/2023, 3:41 PM

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 gab

07/05/2023, 3:45 PM

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

Jason Bosco

07/05/2023, 3:45 PM

Going to queue up an upgrade to

0.25.0.rc44

gab gab

07/05/2023, 3:48 PM

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 Bosco

07/05/2023, 3:50 PM

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

Jason Bosco

07/05/2023, 3:51 PM

But we’ll also publish docker tag for

0.25.0.rc44

shortly

Kishore Nallan

07/05/2023, 3:51 PM

Let me publish rc44

😃 1

Kishore Nallan

07/05/2023, 3:52 PM

Published, please use that.

Jason Bosco

07/05/2023, 3:52 PM

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

gab gab

07/05/2023, 3:53 PM

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

👍 1

gab gab

07/05/2023, 3:55 PM

@Kishore Nallan thanks 👍

👍 1

Open in Slack

Previous Next