Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update bigquery-configs.md #6297

Merged
merged 3 commits into from
Oct 16, 2024
Merged

Update bigquery-configs.md #6297

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
4f71cf4
Update bigquery-configs.md
culley-hippo Oct 15, 2024
d6e6d74
Update bigquery-configs.md
mirnawong1 Oct 16, 2024
0e26e5f
Merge branch 'current' into patch-2
mirnawong1 Oct 16, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 7 additions & 9 deletions website/docs/reference/resource-configs/bigquery-configs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -265,7 +265,7 @@ If your model has `partition_by` configured, you may optionally specify two addi

</File>

### Clustering Clause
### Clustering clause

BigQuery tables can be [clustered](https://cloud.google.com/bigquery/docs/clustered-tables) to colocate related data.

Expand All @@ -286,7 +286,7 @@ select * from ...

</File>

Clustering on a multiple columns:
Clustering on multiple columns:

<File name='bigquery_table.sql'>

Expand All @@ -303,11 +303,11 @@ select * from ...

</File>

## Managing KMS Encryption
## Managing KMS encryption

[Customer managed encryption keys](https://cloud.google.com/bigquery/docs/customer-managed-encryption) can be configured for BigQuery tables using the `kms_key_name` model configuration.

### Using KMS Encryption
### Using KMS encryption

To specify the KMS key name for a model (or a group of models), use the `kms_key_name` model configuration. The following example sets the `kms_key_name` for all of the models in the `encrypted/` directory of your dbt project.

Expand All @@ -328,7 +328,7 @@ models:

</File>

## Labels and Tags
## Labels and tags

### Specifying labels

Expand Down Expand Up @@ -373,8 +373,6 @@ models:

</File>



<Lightbox src="/img/docs/building-a-dbt-project/building-models/73eaa8a-Screen_Shot_2020-01-20_at_12.12.54_PM.png" title="Viewing labels in the BigQuery console"/>

### Specifying tags
Expand Down Expand Up @@ -434,7 +432,7 @@ The `incremental_strategy` config can be set to one of two values:
### Performance and cost

The operations performed by dbt while building a BigQuery incremental model can
be made cheaper and faster by using [clustering keys](#clustering-keys) in your
be made cheaper and faster by using a [clustering clause](#clustering-clause) in your
model configuration. See [this guide](https://discourse.getdbt.com/t/benchmarking-incremental-strategies-on-bigquery/981) for more information on performance tuning for BigQuery incremental models.

**Note:** These performance and cost benefits are applicable to incremental models
Expand Down Expand Up @@ -673,7 +671,7 @@ select ...

</File>

## Authorized Views
## Authorized views

If the `grant_access_to` config is specified for a model materialized as a
view, dbt will grant the view model access to select from the list of datasets
Expand Down
Loading