-
Notifications
You must be signed in to change notification settings - Fork 40
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
[SPIKE/RESEARCH]:Add Duck DB support #1138
Comments
@jlaneve has built a provider for DuckDB on https://github.com/astronomer/airflow-provider-duckdb which is released on https://pypi.org/project/airflow-provider-duckdb/ |
Thank you @kaxil for sharing it. I have also started exploring it, I have a branch in our airflow repo for now but a bit of testing https://github.com/astronomer/airflow/tree/duckdb_provider |
Duckdb doesn't seem to be part of external dialects of Sqlachemy: https://docs.sqlalchemy.org/en/20/dialects/ Also there is one library( https://pypi.org/project/duckdb-engine/ ) which acts as SQLAlchemy driver for DuckDB but this is not maintained well. In this case, all the methods for the base databases have to be overridden as is no SQLAlchemy support. This would increase the time for implementation and the tests. |
There is an issue already on duckdb: duckdb/duckdb#305 |
This is a PR on duckdb-engine for SQLAlchemy support for 2.0 But its very old |
Used duckdb-engine for SQLALchemy driver as per discussion in https://astronomer.slack.com/archives/C03868KGF2Q/p1675274903489399 |
# Description ## What is the current behavior? <!-- Please describe the current behavior that you are modifying. --> Currently Duckdb is not supported with astro-sdk-python <!-- Issues are required for both bug fixes and features. Reference it using one of the following: closes: #ISSUE related: #ISSUE --> closes: #1130 closes: #1138 ## What is the new behavior? <!-- Please describe the behavior or changes that are being added by this PR. --> - Add duckdb support - Add the tests - Update the documentation - Add example DAG ## Does this introduce a breaking change? No ### Checklist - [x] Created tests which fail without the change (if possible) - [x] Extended the README / documentation, if necessary --------- Co-authored-by: Tatiana Al-Chueyr <tatiana.alchueyr@gmail.com> Co-authored-by: Julian LaNeve <lanevejulian@gmail.com>
No description provided.
The text was updated successfully, but these errors were encountered: