Troubleshooting Search Function with Typesense
TLDR Rohan had trouble understanding how search functions in Typesense with email string fields. Kishore Nallan explained the logic of indexing and introduced new features in the 0.22 RC version, advised Rohan to create an issue regarding schema creation errors.
Nov 29, 2021 (23 months ago)
Now when i search with rohan, i get the proper result, but when i search with google i dont get any results. So should i break the string into different parts like "rohan google.com [email protected]" while saving it? Or is there some typesense way of getting around it?
Kishore Nallan06:43 AM
<mailto:[email protected]|[email protected]>will be indexed at
rohangooglecomin Typesense 0.21 since it drops all special characters. So
rohanworks because we support prefix search but not while querying the other words like
In 0.21, you have to break the string into parts before indexing, but in 0.22 RC we have a feature for adding custom separators as part of the collection schema. Check
token_separatorsconfig here: https://github.com/typesense/typesense-website/blob/v0.22.0-docs/docs-site/content/0.22.0/api/collections.md#schema-arguments
Kishore Nallan07:37 AM
Kishore Nallan08:09 AM
/debugend-point to check the TS verison. Regarding the schema, please create an issue on the mongo plugin repo.
Indexed 2779 threads (79% resolved)
Understanding Typesense with Java and MongoDB
Vasudev needed help implementing a Java project with Typesense and MongoDB. Kishore Nallan guided them in designing the project, explaining different methods, providing templates, and responding to error issues. At last, Vasudev successfully implemented the project and expressed gratitude.
Resolving Issues with Infix and Prefix in Query Searches
Daren struggled with searches missing values in production. Jason and Kishore Nallan offered insights and created new features to help solve the problem, which was then tested and deployed by Daren.
Troubleshooting 400 Error When Upgrading Typesense Firestore Extension
Orion experienced a `400` error after updating the Typesense Firestore extension, causing issues with cloud functions. They traced the issue back to a data type conflict in their Typesense collection schema after updating. With help from Jason and Kishore Nallan, they resolved the issue by recreating the collection.