Skip to content

[FAQ Bot] NEW: Which is the correct BigQuery Partition Limit: 4000 or 10000? #153

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

Merged
alexeygrigorev merged 1 commit into from
Feb 7, 2026
Merged

[FAQ Bot] NEW: Which is the correct BigQuery Partition Limit: 4000 or 10000? #153

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
13 changes: 13 additions & 0 deletions ...neering-zoomcamp/module-3/045_48ce1d02df_bigquery-partition-limit-4000-10000.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
---
id: 48ce1d02df
question: 'Which is the correct BigQuery Partition Limit: 4000 or 10000?'
sort_order: 45
---

- The current BigQuery partition limit is 10,000 partitions per table (as of 2026). The playlist listing 4,000 is outdated.
- Time-based partitioning implications:
- Daily partitions: 10,000 partitions cover over 27 years of data; 4,000 partitions covered about 11 years.
- Hourly partitions: 10,000 partitions cover about 416 days (a little over a year); 4,000 partitions covered about 166 days.
- Monthly partitioning with the 10,000 limit can cover over 830 years of data.
- Job operations limit: A single job operation (query or load) cannot modify or affect more than 4,000 partitions at once.
- Reference: Cloud BigQuery quotas documentation: https://docs.cloud.google.com/bigquery/quotas#partitioned_tables