Discussion on Filter Limitations in Search Platforms
TLDR Masahiro queries the filter limits in search platforms. Kishore Nallan informs there are no set limits, albeit with potential performance degradation. Alex humorously alludes to testing with 50,000 filters.




Apr 21, 2021 (29 months ago)
Masahiro
11:28 AMMeiliSearch is 10, Algolia is 1000.
Kishore Nallan
11:28 AMMasahiro
11:28 AMKishore Nallan
11:28 AMMasahiro
11:28 AMMasahiro
11:29 AMBut, why?
Masahiro
11:29 AMKishore Nallan
11:30 AM
Kishore Nallan
11:30 AM
Kishore Nallan
11:32 AMMasahiro
11:34 AMKishore Nallan
11:34 AM
Alex
02:53 PMMasahiro
02:54 PMKishore Nallan
02:54 PMMasahiro
02:54 PMAlex
02:54 PM
Typesense
Indexed 2764 threads (79% resolved)
Similar Threads
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.
Issues and Improvements in Typesense with 14 Million Records
Miguel experienced performance issues when using Typesense for large datasets. Jason suggested performance improvements made to Typesense since then and directed them to specific server-side parameters for better handling. Miguel agreed to try again.


Multiple Filters and JSON Requests in Typesense
Manish asked about multiple filter_by arguments, JSON input, and using multisearch. Jason offered typesense documentation links, examples, and how to use JSON formatted requests with multisearch. Ed shared a similar use case.


Network Errors and Duplicate Requests in Typesense
Ethan and Rushil were experiencing more than 300 network errors and duplicate requests from Typesense. After rigorous troubleshooting, Jason identified the issue as an Instantsearch-induced multiple re-rendering and implemented a fix. Multiple requests reduced, but networking errors persisted, suggested to be due to client-side internet connectivity.



Querying with Typesense-Js and Handling Null Values
michtio was querying using typesense-js and receiving fewer results than expected. Kishore Nallan suggested using different query parameters. Further discussion led to the handling of 'null' values and filtering syntax in the search queries. The thread ended with Jason offering migration support from Algolia to Typesense.


