IssueTracker

**Description**

Users are currently experiencing an inconsistent use with the Terraform implementation of the Google Cloud BigQuery API. Wherein, when you’re creating or modifying a view from another table, the descriptions from the table are dropped.

If you were to insert a new column, the new column is added, but description is blank - for all columns, not just the one which was added.

When a user wants to update both View and Schema in the same request the description gets dropped. As in the example listed in the issue adding a column such as:

{
+ description = "Test Description"
+ mode = "NULLABLE"
+ name = "NUMBER"
+ type = "INTEGER"
},

And then checking again on the column will print out no description is available for the schema.

{
   "name": "NUMBER",
   "type": "INTEGER",
   "mode": "NULLABLE"
  }


**Steps to Reproduce the Issue**

- Add new column to SQL and schema
- Run <terraform apply>. The plan displayed is correct with the expected changes to both SQL and schema
- New column is added, but descriptions are not.

**Current Workaround for the Issue**

The workaround is to run `terraform apply` twice, which will add now the descriptions to the already modified table.
If you don't modify the view definition, it will be corrected the 2nd time the tooling executes.

Which despite of not being complex, the insertion of data shouldn't produce this drop of information. It could result in a big loss of data to those unprepared.


There are currently some other forums discussing this issue:
- https://github.com/hashicorp/terraform-provider-google/issues/16647
- https://github.com/hashicorp/terraform-provider-google/issues/12616