Hello! First of all, thanks again for all the inc...
# community-help
g
Hello! First of all, thanks again for all the incredible work you’re doing with Typesense — we really love the tool and everything you ship! We’ve run into an issue with facet counts. Specifically: • When a user selects a facet, the actual number of returned results differs from the facet count “estimate” shown beforehand. • For example, a facet might display count: 148, but once applied, the total number of matching documents is higher : 153. Any thoughts ? I read this : https://typesense.org/docs/guide/faqs.html#how-do-i-get-facet-counts-for-values-that-users-have-not-filtered-on but the screenshot is from the typesense UI so I guess it should be reliable, nah ? Thanks a lot !
k
Check the answer to "Why do I sometimes get more results when adding filters?" on the same page.
g
ok so : https://typesense.org/docs/guide/faqs.html#why-do-i-sometimes-get-more-results-when-adding-filters Got it so everyone got the same issue @Kishore Nallan? https://support.algolia.com/hc/en-us/articles/4406975248145-Why-are-my-facet-and-hit-counts-not-accurate What would you recommend in order to test the
Copy code
max_candidates
param ? I guess in typesense cloud (the online UI) we have
max_candidates=4
default and I can test a query with a
1000
value to see what's going on ?
k
Yeah you can use that and it should mostly bring the counts close
I also recommend not showing counts for total hits found. None of the major ecommerce search engines like Amazon do (because of the same problem)