This repository was archived by the owner on Nov 11, 2020. It is now read-only.
Add functionality that allows eagerCursor(true) on query builders #41
+195
−6
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.
When used it will return a different type of cursor that eagerly fetches all documents when you start iteration instead of one document per iteration. So it loads all data in to memory before starting iteration.
Without eager cursor:
With eager cursor:
This will tie in to #40 where we have retry functionality. In order to benefit from retries on cursors, you will have to use an eager cursor so that the data fetching is all done before iteration starts so that if a cursor error happens you can try again with a new cursor.