Remove query to information_schema.schemata in BigQuery catalog generation

[drewbanin]

Describe the feature

See here: https://stackoverflow.com/questions/59891634/how-can-i-give-others-permission-to-read-my-information-schema-schemata-in-bigqu

Sounds like some dbt users are having issues running the catalog query generated by dbt because they lack permissions to see all of the datasets in a given project, and BigQuery lacks the kinds of granular permissioning constructs we'd expect to see from a database.

dbt currently uses the information_schema.schemata table solely to find the location for datasets referenced in a dbt project.

As a workaround, we can do one of the following:

• Remove the subquery that hits information_schema.schemata and stop producing a location in the catalog
• Remove the subquery that hits information_schema.schemata and instead grab the location from the BQ API after the information schema queries have completed
• Run the query that hits the schemata table as a separate statement, joining the results in memory (like we do on Redshift):

https://github.com/fishtown-analytics/dbt/blob/d2760d5a494b81f6d477a67738ecdc37facdd5ec/plugins/redshift/dbt/include/redshift/macros/catalog.sql#L231-L241

Describe alternatives you've considered

• We could do nothing here and advise folks to use the permissioning workaround described in this Stackoverflow posts

Additional context

BigQuery

Who will this benefit?

BigQuery users with nontrivial permissioning needs