Note: dbt-fusion support in Elementary is still in beta, as is dbt-fusion itself. Please see below a list of features that are not yet implemented.
Upgrading to dbt-fusion
As a part of the migration to dbt-fusion, it is required to remove deprecated syntax from various areas of the dbt project, and YAMLs in particular. Specifically for tests the following are important:- Test arguments must be encapsulated under an
arguments
field. - Configuration fields such as
meta
,tags
orseverity
must be encapsulated under aconfig
field. - Recommended (but not a must) - change the
tests
field todata_tests
to conform with the current dbt guidelines.
Supported Elementary capabilities
Most of the main capabilities of the Elementary dbt package are supported in Fusion, including:- Anomaly detection tests.
- Schema tests.
- Artifacts collection.
- Python tests.
- JSON schema tests.
- The missing dbt-fusion features listed below.
Missing features in dbt-fusion
In addition to the above, there are some features that are currently missing from dbt-fusion, and therefore are not yet available in the Elementary package. For each one of the issues below, we’ve included a link to the dbt-fusion github repository - please upvote these features if they are important to you!- Tests with error status are not being reported - If a test fails “normally” (e.g. not_null fails on rows with null values), Elementary will report it as expected with a “fail” status. However, if there is a compilation error / any error that comes before the actual test query (“error” status in dbt-core), it will currently be missing.
- Source freshness results are not reported
- Exposure artiracts are not reported
- Group artifacts are not reported
- Compiled code is missing from dbt artifact tables
- Failed row count is missing from dbt artifact tables