IssueTracker

This will create a feature request which anybody can view and comment on.

Please describe your requested enhancement. Good feature requests will solve common problems or enable new use cases.

What you would like to accomplish:

Clustering Billing Export tables is officially allowed.

The document https://cloud.google.com/billing/docs/how-to/export-data-bigquery-tables warns, "Don't modify these tables, such as by adding a column or manually re-creating the tables." However, it is unclear whether clustering the tables is considered as the modification mentioned by the document. Some users want a thorough investigation so that they can use clustered column(s) with guarantees.

In detail, there may be 3 scenarios regarding the clustered table:

1. Change from non-clustered to clustered
2. Change clustered column(s)
3. Change from non-clustered to clustered and then update the table (https://cloud.google.com/bigquery/docs/creating-clustered-tables#modifying-cluster-spec)

I’d appreciate it if you could specify which of the 3 scenarios are allowed or refrained from.

How this might work:

• Users can set clustered column(s) in Billing Export tables without any concern.

If applicable, reasons why alternative solutions are not sufficient:

• Some users want to optimize costs by clustering the table, which doesn’t have alternatives or workarounds.

Other information (workarounds you have tried, documentation consulted, etc):

• Reportedly, just clustering a Billing export table doesn’t seem harmful.