perf: Using an iterator instead of going through all the data #150
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.
@davidrabinowitz Comparing the version 0.9.2-beta with the current one I realized that it was pretty slow when doing limit or show operations. It was due the introduction of the ReadRowsHelper in the version 0.10.0-beta which was iterating over all the results before returning the final iterator, so I wrapped the results in a new iterator, achieving the same retry functionality