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 #6291

Merged
merged 4 commits into from
Oct 15, 2024
Merged

Update bigquery-configs.md #6291

Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
d7989de
Update bigquery-configs.md
culley-hippo Oct 15, 2024
4feaa36
Merge branch 'current' into patch-1
mirnawong1 Oct 15, 2024
a233e34
Update website/docs/reference/resource-configs/bigquery-configs.md
mirnawong1 Oct 15, 2024
8e8a295
Merge branch 'current' into patch-1
mirnawong1 Oct 15, 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
2 changes: 1 addition & 1 deletion 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 @@ -21,7 +21,7 @@ This will allow you to read and write from multiple BigQuery projects. Same for

### Partition clause

BigQuery supports the use of a [partition by](https://cloud.google.com/bigquery/docs/data-definition-language#specifying_table_partitioning_options) clause to easily partition a <Term id="table" /> by a column or expression. This option can help decrease latency and cost when querying large tables. Note that partition pruning [only works](https://cloud.google.com/bigquery/docs/querying-partitioned-tables#pruning_limiting_partitions) when partitions are filtered using literal values (so selecting partitions using a <Term id="subquery" /> won't improve performance).
BigQuery supports the use of a [partition by](https://cloud.google.com/bigquery/docs/data-definition-language#specifying_table_partitioning_options) clause to easily partition a <Term id="table" /> by a column or expression. This option can help decrease latency and cost when querying large tables. Note that partition pruning [only works]([https://cloud.google.com/bigquery/docs/querying-partitioned-tables#pruning_limiting_partitions](https://cloud.google.com/bigquery/docs/querying-partitioned-tables#use_a_constant_filter_expression) when partitions are filtered using literal values (so selecting partitions using a <Term id="subquery" /> won't improve performance).
mirnawong1 marked this conversation as resolved.
Show resolved Hide resolved

The `partition_by` config can be supplied as a dictionary with the following format:

Expand Down
Loading