Hi Typesense team, We are implementing e-commerce search using Typesense. The product catalogues usually have hundereds of different properties many of which are only relevant for subset of the catalogue. We've found that search results often return too many facets, making the UI cluttered. Our solution: - After each search, filter returned facets using a configurable ratio relative to the total number of documents found - Only display facets that appear in at least X% of search results (e.g. "only display the facet if at least 50% of the results have given property") - Sort filtered facets by count (most frequent first) This makes search results much cleaner. The implementation is pretty straightforward - just a post-processing step after the search. Currently, we have an interceptor service between the UI and Typesense that does this logic. I imagine this is pretty common problem, do you think this is a good solution? Would this be something that could potentially be considered to be implemented into typesense core? E.g. adding

min_facet_occurrence_ratio

faceting parameter to the search endpoint?

CC: @Kishore Nallan

Interesting idea! Could you open a GitHub issue with this feature request, so we can track interest?

Sure, here it is https://github.com/typesense/typesense/issues/2455