Feat: add partitioning for ducklake databases#5030
Merged
Conversation
treysp
force-pushed
the
trey/ducklake-partitioning
branch
from
1fe603c to
b3756fc
Compare
izeigerman
approved these changes
Jul 26, 2025
treysp
force-pushed
the
trey/ducklake-partitioning
branch
from
b3756fc to
af86b9f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
DuckDB does not natively support partitioning, but the ducklake extension does.
The extension requires partitioning to be set via
ALTERafter table creation.This PR updates the DuckDB adapter to execute that
ALTERif the table is in a ducklake catalog. For other catalog types, partitioned_by is ignored.