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

Add support for range partitioning in BigQuery #5723

Conversation

modular-magician
Copy link
Collaborator

@modular-magician modular-magician commented Feb 19, 2020

Currently only time partitioning is supported.

Release Note Template for Downstream PRs (will be copied)

#5239

bigquery: Support for range-based partitioning in BigQuery tables has landed. Fixes https://github.com/terraform-providers/terraform-provider-google/issues/5239.

Derived from GoogleCloudPlatform/magic-modules#2890

* Add support for range partitioning in BigQuery

Currently only time partitioning is supported.

* Remove the nested fields since they aren't necessary

* Fix compilation errors

Signed-off-by: Modular Magician <magic-modules@google.com>
@modular-magician modular-magician merged commit dd13564 into hashicorp:master Feb 19, 2020
@sid0911
Copy link

sid0911 commented Mar 5, 2020

Team, range_partitioning is not working for me. Could you please help to resolve this issue ?

Error: Unsupported block type

on bigqtable.tf line 51, in resource "google_bigquery_table" "bq_tables_rgpt":
51: range_partitioning {

Blocks of type "range_partitioning" are not expected here.

@ghost
Copy link

ghost commented Mar 21, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!

@ghost ghost locked and limited conversation to collaborators Mar 21, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants