Prioritizing Results in Autocomplete Search
TLDR Sachyya and Digamber discuss issues with ordering of results for multi-collection auto-complete searches. Kishore Nallan suggests using a dynamic filtering feature but notes that behaviour might not be optimal if user input varies.
Apr 08, 2022 (19 months ago)
Sachyya
10:29 AM
Kishore Nallan
10:30 AMSachyya
10:40 AMwe have results like
1. Adele
2. Bring Me the horizon
When I search "adele someone like me", it shows "Bring Me the Horizon". I want "Adele" to be shown.
Kishore Nallan
10:44 AM
Digamber
04:05 PMThere are two collections Artists and Songs
the Artist is : Adele and the Song is Adele - Woman like me
When we type Adele Woman Like Me
The result for Adele does not show up / returned for Artist Adele
Rather we’re getting a different result - it almost seems like the last word is prioritized over the first.
Kishore Nallan
04:12 PMIn any case when Typesense does not find all tokens in the query, it tries to drop tokens from right to left and then left to right until results are found. This behavior might be resulting in the ordering you notice.
Digamber
04:27 PMDigamber
04:27 PMDigamber
04:27 PMKishore Nallan
04:30 PMWe might have to parameterise this behavior but what if people put the artist last?
Digamber
04:33 PM
Typesense
Indexed 2786 threads (79% resolved)
Similar Threads
Typesense Performance with Large Datasets & Custom Sort
krok inquires about Typesense's performance on large datasets and custom sorting. Kishore Nallan explains that Typesense is optimized for this scenario using pagination and text relevance.
Adjusting Text Match Score Calculation in TypeSense
Johannes wanted to modify the Text Match Score calculation in TypeSense to improve search results returns. With counsel from Jason and Kishore Nallan, various solutions were proposed, including creating a Github issue, attempting different parameters, and updating Docker to a new version to resolve the matter.
Phrase Search Relevancy and Weights Fix
Jan reported an issue with phrase search relevancy using Typesense Instantsearch Adapter. The problem occurred when searching phrases with double quotes. The team identified the issue to be related to weights and implemented a fix, improving the search results.
Performance Characteristics of Filtering Search Results
Oskar queries the performance difference in filtering search results. Jason clarifies how filters work and provides performance improvement suggestions like increasing vCPUs and sharding the collection. Kishore Nallan explains filter IDs and document ID matching. The thread concludes with discussions on performance tradeoffs in filter implementation.
Moving from Algolia to Typesense: Questions and Answers
Juan sought advice from Kishore Nallan about moving from Algolia to Typesense, handling MultiSearch, setting parameters, checking imported documents, and a specific syntax query.