Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc(bigquery): add table create sample using integer range partitioning #9478

Merged
merged 4 commits into from
Nov 6, 2019

Conversation

tswast
Copy link
Contributor

@tswast tswast commented Oct 15, 2019

This code sample doubles as a system test for integer range partitioning features. Follow-up to #9477

@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label Oct 15, 2019
This code sample doubles as a system test for integer range partitioning
features.
@tswast tswast force-pushed the bq-range-partitioning-samples branch from 846b60c to e1f6921 Compare October 18, 2019 16:47
@tswast tswast changed the title doc(bigquery): add code samples for integer range partitioning doc(bigquery): add table create sample using integer range partitioning Oct 18, 2019
@tswast tswast marked this pull request as ready for review October 18, 2019 16:47
@tswast tswast requested review from a team and shollyman October 18, 2019 16:47
@plamut plamut added type: docs Improvement to the documentation for an API. api: bigquery Issues related to the BigQuery API. labels Oct 22, 2019
Copy link
Contributor

@plamut plamut left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, please just blacken the changes (the lint check fails).

I noticed that table range partitioning info is not presented anywhere in the GCP control panel, but that's not a client library issue.

@tswast tswast requested a review from plamut October 24, 2019 22:44
Copy link
Contributor

@plamut plamut left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As discussed offline - even if not necessary, it is a good idea to include the sample in the Sphinx docs, too.

@tswast tswast requested a review from plamut October 25, 2019 22:38
@plamut
Copy link
Contributor

plamut commented Nov 4, 2019

@shollyman Is there anything that you might want to add here before merging?

Thanks!

Update: Seems like no, merging then. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: bigquery Issues related to the BigQuery API. cla: yes This human has signed the Contributor License Agreement. type: docs Improvement to the documentation for an API.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants