ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how to create time-unit and integer-range partitioned tables in BigQuery, enable require_partition_filter, and verify partition pruning to lower query costs and avoid full table scans.
When BigQuery tables grow to terabytes, careless queries can explode costs. Partitioning and clustering let you prune data and pay only for what you read.
Learn how to combine BigQuery partitioning and clustering to cut query costs and improve performance, with a concrete web‑events example and verification steps.
Partition BigQuery tables by a DATE or TIMESTAMP column and cluster by filter columns so on-demand queries scan fewer bytes. Verify savings with free dry runs.
Data exfiltration from BigQuery often happens through valid credentials. Learn how to build a VPC Service Controls perimeter that blocks unauthorized access while allowing trusted services through ingress and egress rules.
Create BigQuery ingestion-time partitioned tables with DDL or the bq CLI, query them with the _PARTITIONTIME pseudo column, and verify partition pruning actually reduces bytes scanned.
Learn how BigQuery’s require_partition_filter option forces every query to include a partition predicate, preventing costly full‑table scans and guiding safer, more predictable usage.
A minimal VPC Service Controls design encloses BigQuery and Cloud Storage in one perimeter with corporate CIDR access levels, ingress allow lists, and default egress deny, plus operational checks for violations and policy drift.
Partitioning cuts BigQuery costs for date-filtered queries, but selective filters on tenant or event type need clustering. Here's how to combine both, with a worked example and the trade-offs.
google