You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Specifically QA: Investigate the need for generate_schema_name #5, also brought up by @hlcianfagna, may need attention in one way or another, possibly by documenting the default behaviour properly, and by providing the information how to change it on your fingertips.
Secondarily, we recommend to diligently scan the genesis patch for relevant TODO and FIXME items, to converge them into creating upstream tickets at crate/crate, or by emphasizing existing ones. This is to drive the feedback cycle towards CrateDB Core.
The CrateDB and dbt documentation page should be improved, specifically outlining caveats and differences when comparing PostgreSQL's capabilities with CrateDB's, and by adding a high-level overview about the feature capabilities of dbt-cratedb2, to get expectations right and visible from the very beginning, aka. »What's Inside«. We made a little start with dbt: Improve entry point page. Absorb community tutorial. cratedb-guide#153, but that's mostly layout and setting the stage.
About
After conceiving it and releasing 0.0.1 and 0.0.2, the code base needs more love on behalf of a few more iterations.
Items
Genesis: Add dedicated "cratedb-configs" page to upstream documentation #7
Genesis: Validate the adapter works well with CrateDB Cloud #8
Submit upstream documentation patch: Platform connections: Add new data platform adapter for CrateDB dbt-labs/docs.getdbt.com#6564
Let's diligently check @hlcianfagna's commits at crate-workbench/dbt-cratedb@main...hlcianfagna:dbt-cratedb2:hlcianfagna/2023MayUpdate, so nothing will get lost that is important to make CrateDB work well with dbt.
Specifically QA: Investigate the need for
generate_schema_name
#5, also brought up by @hlcianfagna, may need attention in one way or another, possibly by documenting the default behaviour properly, and by providing the information how to change it on your fingertips.Secondarily, we recommend to diligently scan the genesis patch for relevant TODO and FIXME items, to converge them into creating upstream tickets at crate/crate, or by emphasizing existing ones. This is to drive the feedback cycle towards CrateDB Core.
The CrateDB and dbt documentation page should be improved, specifically outlining caveats and differences when comparing PostgreSQL's capabilities with CrateDB's, and by adding a high-level overview about the feature capabilities of dbt-cratedb2, to get expectations right and visible from the very beginning, aka. »What's Inside«. We made a little start with dbt: Improve entry point page. Absorb community tutorial. cratedb-guide#153, but that's mostly layout and setting the stage.
Last but not least, feature capabilities aim to be expanded and interoperability wants to be probed, see Enhancement Backlog #4 and QA: Interoperability with dbt ecosystem #6.
Call for Support
Wrapping up needs your support in various degrees, short- and mid-term.
delete+insert
materialization cratedb-examples#784The text was updated successfully, but these errors were encountered: