-
-
Notifications
You must be signed in to change notification settings - Fork 16
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.
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
Add write support to pg_analytics
#107
Comments
After an initial investigation, it looks like we can use DuckDB replacement scans, which allow you to register a custom callback to fire if DuckDB tries to read a table that doesn't exist in DuckDB. So if the user tries to COPY a Postgres table to S3, we can
|
After the merge at duckdb/duckdb-rs#370, we can utilize the complete DuckDB C API to solve this ticket. |
Great find -- Here is the PR: duckdb/duckdb-rs#381 |
@Weijun-H this just got merged, 5 days ago! This would be a really wonderful PR. Write support is our most requested feature. |
/take |
Really excited to see this feature. thanks! |
What feature are you requesting?
This feature would enable users to write data to AWS S3, GCS and Azure Blob Storage. This would primarily be helpful for tiering data off to minimize cost. At first, we would only want to support the main file formats and object stores, not the open table formats like Delta Lake and Iceberg
Why are you requesting this feature?
Enable users to tier data off to AWS S3 and others easily
What is your proposed implementation for this feature?
Needs proper investigation. DuckDB has capabilities for this which we would need to expose properly.
Full Name:
Philippe Noël
Affiliation:
ParadeDB
The text was updated successfully, but these errors were encountered: