Conversation
This branch has not been deployed
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
1 participant
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.
What kind of change does this PR introduce?
The PR adds ducklake support for duckdb_fdw. Ducklake has reached 'production readiness' as of April this year and there appears to be decent adoption in the ecosystem
Since it supports postgres as a metadata catalog. It's a really powerful combo living in the supabase ecosystem (using supabase storage as the backing data store). The missing piece here is query support in postgres so all analytical queries can be done via the same client.
What is the current behavior?
Currently the fdw is limited to the following services:
What is the new behavior?
Users can add ducklake tables via duckdb_fdw config
Additional context