1 upvotes, 1 direct replies (showing 1)
View submission: Update on COLO switchover -- bug fixes, reindexing and more
Could you rephrase "cheaper"?
It isn't a term I'm personally familiar with in a professional context (granted, my degree is in Computer Science, not Data Science).
I'm assuming you are saying that `total_results` returns only the count it would return given the limit of returnable items specified, and therefore would at most equal the limit. Whereas `track_total_hits=true` would result in it returning the actual total number of results, not just the limit of the items it would return at a time.
Thanks for the sticky update. It clarifies things and consolidates answers to the questions flying about.
Comment by s_i_m_s at 19/12/2022 at 23:39 UTC
3 upvotes, 0 direct replies
Cheaper as in it is less processor/resource intensive, it takes less time for the server to generate an estimate than it does to give an exact count.
`total_results` was the old field it's not valid anymore, it was supposed to be equal to the total results not an estimate.
The new field looks like `{"total":{"value":10000,"relation":"gte"}` when maxed out at 10k results but appears to be the same as the exact count below 10k.
Adding `track_total_hits=true` results in an exact count instead like `{"total":{"value":28462,"relation":"eq"}`