Tim Pickup
12/13/2025, 5:56 PMKishore Nallan
12/13/2025, 6:08 PMbucket_size Instead of buckets - This scales better with variable result sizes, e.g. with bucket_size: 10, you're saying "within every 10 similarly-relevant results, let sales break the tie." This works whether you have 50 results or 5000. So try with: "_text_match(bucket_size: 10):desc,sales_count:desc"
2. You can also add conditional Boosting of the sales count with _eval() as this gives tiered boosts rather than linear ones, which might address your "don't blanket push all sold items" concern. _text_match(bucket_size: 10):desc,_eval([(sales_count:>100):3, (sales_count:>10):2, (sales_count:>0):1]):descTim Pickup
12/13/2025, 8:14 PMTim Pickup
12/13/2025, 8:16 PMTim Pickup
12/13/2025, 8:42 PMTim Pickup
12/13/2025, 8:57 PMKishore Nallan
12/14/2025, 4:19 AMbucket_size this won't be a problem. For e.g. bucket_size: 10 will ensure that you split the results into groups of 10 hits. Also bucketing is applied only to the first 250 hits so it won't extend to the lower quality hits. Don't use buckets , use bucket_size.Tim Pickup
12/15/2025, 5:32 PMAlso bucketing is applied only to the first 250 hitsOh, thanks. I can't see anywhere in the docs it says this. I also don't see anywhere its configurable? I tried changing max page size just in case and didnt seem to help. I seem to get no actual difference in order when I do buckets:10, buckets:2 or not at all š I will need to create a test though to show this I guess