docs(bigquery): add sample to read from query destination table #9964
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
This sample addresses internal issue 134774673, in which we recieved feedback that it's not clear how to paginate through the results of a query. This sample shows that all completed queries have a destination table, which can be read from with tabledata.list. Note: The client library avoids the extra call to `get_table` if query results are read directly from the QueryJob, but it's confusing to show that we're able to get the schema from a private API call to getQueryResults.
googlebot
added
the
cla: yes
tswast
added
api: bigquery
googlebot
added
the
cla: yes
shollyman
approved these changes
Dec 12, 2019
This was referenced Jan 29, 2020
[CHANGE ME] Re-generated container to pick up changes in the API or client library generator.
#10256
Closed
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.
This sample addresses internal issue 134774673, in which we recieved
feedback that it's not clear how to paginate through the results of a
query. This sample shows that all completed queries have a destination
table, which can be read from with tabledata.list.
Note: The client library avoids the extra call to
get_tableif queryresults are read directly from the QueryJob, but it's confusing to show
that we're able to get the schema from a private API call to
getQueryResults.