You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
If an issue is assigned to a user, that user is claiming responsibility for the issue.
Customers working with a Google Technical Account Manager or Customer Engineer can ask them to reach out internally to expedite investigation and resolution of this issue.
After require_partition_filter is false, the materialzied view is created successfully.
Once the materialized view is created with false, require_partition_filter can be set to true.
Steps to reproduce
terraform apply
set require_partition_filter to false
terraform apply -> created successfully
set require_partition_filter to true
terraform apply -> updated successfully
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered:
Community Note
Terraform Version & Provider Version(s)
Terraform v1.9.7
on linux_amd64
Affected Resource(s)
google_bigquery_table
Terraform Configuration
Debug Output
No response
Expected Behavior
The materialized view is created successfully.
Actual Behavior
The error below occurred.
After require_partition_filter is false, the materialzied view is created successfully.
Once the materialized view is created with
false
,require_partition_filter
can be set totrue
.Steps to reproduce
terraform apply
require_partition_filter
tofalse
terraform apply
-> created successfullyrequire_partition_filter
totrue
terraform apply
-> updated successfullyImportant Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: