#community-help

Issue with Typesense, Facets, and Special Characters

TLDR Ailish is encountering an issue with Typesense handling of apostrophes versus single quotes. Jason clarified how Typesense handle special characters and requested further specifics from Ailish.

21mo

Join the chat

Apr 11, 2022 (21 months ago)

Photo of md5-7fcbf02da67845f42ef837fd8a989396

Ailish

12:14 PM

Is this a InstantSearch issue? My facets show up separately when there is an apostrophe vs a single quotation mark in the field. The Typesense results do not recognise the difference when I select either or both of these facets, and always shows me the total sum of results (682). So I assume the data is normalised on the Typesense side. However, Algolia document that they also normalise the data, so is it some limitation of faceting? Has anyone experienced this before?

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

05:22 PM

Ailish Typesense only normalizes accented chars into their non-accented versions... It does not do this with apostrophes vs quotes

05:24

Jason

05:24 PM

Could you look at the network tab in your browser's dev console, and share the exact query made to Typesense when you select both filters? And also the response from Typesense?

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 3015 threads (79% resolved)

Join Our Community

Similar Threads

Range Filtering and Faceting Discussion

Phil asked about the requirements for range filtering, which Jason explained does not always require faceting. Discussion about different possibilities with Algolia and Typesense ensued, resulting in Phil successfully utilizing the 'Configure' widget.

28mo

Resolving Typesense Field Setup Issue

em1nos is having an issue running Algolia/InstantSearch adaptation to Typesense due to field attribute disparity. Jason advised checking the attribute in the schema while Kishore Nallan pointed out a typo. Following the corrections, the issue was resolved.

31mo

Comma Escape Issue in Typesense with Instant Search Adapter

Stefan reports issues with comma escaping in Typesense instant search adapter. Kishore Nallan confirms the known issue with no available resolution yet.

34mo