3 upvotes, 0 direct replies (showing 0)
View submission: Update on COLO switchover -- bug fixes, reindexing and more
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"}`
There's nothing here!