-
Notifications
You must be signed in to change notification settings - Fork 152
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
Support DuckDB warehouse #1124
Comments
@ntnhaatj How's your progress on this? Were you able to figure out the last few tests? |
duckdb has just released v0.9.0 (which officially has fixed the shadowing name issue in CTE). I tested it in my forked branch, it passed almost of defined tests suite, there are a few tests still failed (3 if I remember correctly) which relate to schema change, just don't have time to fix and finish them. |
that is great news. i encountered today an error message when i tried to test how duckdb-dbt works with elementary and my heart sank when i saw: thanks for the work for this |
Hi @mamonu, my work is currently designed for my specific use case, primarily for data quality reporting. It doesn't guarantee the quality and coverage of all elementary features. |
Hi @ntnhaatj ! Cheers, |
First of all, thank you for your awesome product.
Is your feature request related to a problem? Please describe.
No, this is not motivated by a problem. It's about supporting an additional warehouse that I believe would be highly suitable for data-quality observability.
Why DuckDB?
Would you be willing to contribute this feature?
Yes, I am willing to. I've already started development in my forked repository, and it's functional to a certain expectation. However, a few tests are failing, and I would appreciate your guidance to finalize it.
Current limitation
While working on my forked repo, I encountered some limitations:
The text was updated successfully, but these errors were encountered: