Iterating over multi-page job results failed #145
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
scrollToken -> pageCursor
hvt
changed the title
sserrata
approved these changes
Apr 2, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
scrollToken -> pageCursor
Description
The job result iterator used the (probably deprecated) response's
page.scrollTokenvalue. This PR changes that according to the current docs (and prod implementation).Motivation and Context
Iterating over multiple pages (i.e. multiple
/query/v2/jobResults/*requests) does not work.How Has This Been Tested?
Just locally, no idea if the test suite tests this, probably CI finds out.
Types of changes
Checklist