Open philippemnoel opened 2 months ago
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 https://github.com/duckdb/duckdb-rs/issues/370, we can utilize the complete DuckDB C API to solve this ticket.
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: https://github.com/duckdb/duckdb-rs/pull/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
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