#7448 Fix _total=accurate by counting resultIterator iterations and prefetching all if an accurate count is requested #7449
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Search results totalCount is set based on the number of items in the results iterator so that it always equals the number of results in the search results set. To make this work, we'll prefetch the entire search if an accurate count is requested along with the search.
If the user requested only a count and nothing else, then we still execute the dedicated COUNT query.
While the total count will always be accurate, Im not sure whether this would be too slow of an approach, particularly if the search would cover a very large number of results.
Fixes #7448