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

Better default partition granularity on BigQuery #196

Closed
nj1973 opened this issue Jun 11, 2024 · 1 comment · Fixed by #207
Closed

Better default partition granularity on BigQuery #196

nj1973 opened this issue Jun 11, 2024 · 1 comment · Fixed by #207
Assignees
@nj1973
Labels
enhancement New feature or request
Milestone
2024-07 Release

Comments

@nj1973
Copy link
Collaborator

nj1973 commented Jun 11, 2024

On BigQuery we default to 'D' daily partitions. That doesn't really make much sense. We should default to 'M' instead.

We could also think about making this adaptive. If the frontend RDBMS is partitioned on the same column then why not look at the gaps between high values and estimate whether to use 'D', 'M' or 'Y'.
@nj1973 nj1973 added the enhancement New feature or request label Jun 11, 2024
@nj1973 nj1973 self-assigned this Jul 5, 2024
@nj1973 nj1973 added this to the 2024-07 Release milestone Jul 5, 2024
@nj1973 nj1973 linked a pull request Jul 5, 2024 that will close this issue
feat: Change default BigQuery date partition granularity to M #207
Merged
@nj1973
Copy link
Collaborator Author

nj1973 commented Jul 5, 2024

I've decided against making the granularity adaptive for this issue, just get that better default in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nj1973 nj1973

Labels
enhancement New feature or request
Projects
None yet
Milestone
2024-07 Release
Development

Successfully merging a pull request may close this issue.

feat: Change default BigQuery date partition granularity to M gluent/goe
1 participant
@nj1973