Try our conversational search powered by Generative AI!
AI OnAI Off
Inaccurate terms count on filters
By default it only generates the facet on the first 10 results, you can change this by passing in request.Size parameter i.e.
.TermsFacetFor(x => x.ClassificationDetails.OfficeCategories, request => { request.Size = 100; })
Documentation: Terms facets (optimizely.com)
Edited,
Mar 27, 2023 14:49
Yes, this is what I am reffering to when I am saying "size of terms facet". So if I f.ex pass 20 as the size for the ParentCategory, what I see in the results is that the count on the facet result (TermsFacet) are correct on the first filters, but from around filter 14-20 the count is incorrect. But if I increase the size in the request to f.ex 30, the count on these filters is corrected and its now filters 24-30 that are incorrect.
Mar 27, 2023 19:41
Find 13.5.2
When using client.Search<ISearchProduct>.TermsFacetFor I noticed the count on the last terms facets are inaccurate. It can vary from just 1 up to 30 and the wierd part is that if I increase the size of the terms facet from f.ex 20 to 25 the count of the first 20 filters is now correct, but then the count on the last "new" filters can be wrong again. On the cases where the count only differ a couple I have checked the index and don't see anything wierd in the index.