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

BigQuery: Support Time Unit Partitioning #7848

Closed
d-torres opened this issue Sep 29, 2020 · 2 comments · Fixed by #8045
Closed

BigQuery: Support Time Unit Partitioning #7848

d-torres opened this issue Sep 29, 2020 · 2 comments · Fixed by #8045
Assignees
Labels
api: bigquery Issues related to the BigQuery API. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@d-torres
Copy link

BigQuery has introduced additional types of time unit partitioning for partitioned tables. Supported values are "HOUR", "DAY", "MONTH", and "YEAR". May we extend support for the new values in the library?

Reference implementations:
Go - googleapis/google-cloud-go#2858
Java - googleapis/java-bigquery#737

@product-auto-label product-auto-label bot added the api: bigquery Issues related to the BigQuery API. label Sep 29, 2020
@quartzmo quartzmo self-assigned this Sep 29, 2020
@quartzmo quartzmo added the type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. label Sep 29, 2020
@quartzmo
Copy link
Member

quartzmo commented Oct 6, 2020

This will require a documentation update. The current docs state:

Currently the only supported value is "DAY".

@shollyman
Copy link

Language in REST reference:

The supported types are DAY, HOUR, MONTH, and YEAR, which will generate one partition per day, hour, month, and year, respectively.

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. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants