#community-help

Issues with Typesense Server compared to Algolia on DataTables.API

TLDR Hudio was concerned about a search issue with Typesense's handling of special characters compared to Algolia. Jason clarified this and promised improvements in future updates.

26mo

Join the chat

Jul 14, 2021 (26 months ago)

Photo of md5-17a3a044615b1dd1794425fcdb2b9a13

Hudio

03:43 PM

I am running some test on a self hosted Typesense server before deploying it to replace the Algolia server that is currently used. Is there a reason why when searching API a result such as DataTables.API is not returned by Typesense but is by Algolia.

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

04:07 PM

Typesense currently removes special characters, so DataTables.API gets indexed as DataTablesAPI. If you replace special characters with spaces then you’ll get the result you’re looking for. We plan to allow this special character handling to be configurable shortly.

Typesense

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

Indexed 2764 threads (79% resolved)

Join Our Community Manage subscription

Similar Threads

Typesense Alternative for Algolia Recommend & Retrieving Search Requests

Nop asked for a Typesense alternative to "Algolia Recommend". Kishore Nallan suggested using vector search feature. Additionally, Kishore Nallan recommended using the stats API endpoint to get search request counts.

6mo

Ongoing Typesense Update Discussion

James requested an update for a Typesense issue, which Jason clarified was underway, mentioning improved relevance and the introduction of query rules.

24mo

TypesenseInstantsearchAdapter and Algolia Query

Jordan had issues with utilizing Algolia's helper method after creating the TypesenseInstantsearchAdapter. Jason clarified that this adapter is unnecessary with Autocomplete.js. The correct approach is to use the typesense-js library directly.

18mo