Add dataset location config to BigQuery profile

[drewbanin]

Feature

Feature description

BigQuery doesn't allow data to be transferred between locations (eg. EU to US). To remedy this, dbt should allow a location config in BigQuery profiles. That value should be supplied when creating datasets here.

This can be implemented by setting the location argument in google.cloud.bigquery.client.Client() as described here. If I understand this correctly, all subsequent API actions will be location-aware. We will know this works when tables fetched from the BQ API have a location attribute that is not None.

The location field should be a parameter in a BigQuery profile.

Who will this benefit?

BQ users with their data in non-US regions.

[jaredlt]

For users googling, this will solve the error you get when dbt run returns Cannot read and write in different locations: source: EU, destination: US

[darrenhaken]

Is this in now, if so how do I add it to my profile?

[drewbanin]

@darrenhaken this is currently unreleased, but will be going out in our Grace Kelly release in January, 2019. You can always consult our Milestones to understand which release a given issue is shipping with. Check the CHANGELOG for links to docs when the code is released

[paulooctavio]

Has the feature already been released?

[jtcohen6]

Definitely! https://docs.getdbt.com/reference/warehouse-profiles/bigquery-profile#dataset-locations