Jeff Nawrocki
07/24/2023, 6:45 PMRiccardo Amadio
07/26/2023, 10:31 AMRiccardo Amadio
07/26/2023, 10:32 AMTerry Dontje
07/29/2023, 11:51 PMsandy
08/04/2023, 4:09 PMJeff Nawrocki
08/04/2023, 4:41 PMThomas Weit
08/11/2023, 11:26 AMasset_factory
. Each Expectation Suite is a (partitioned) data asset in dagster.
Inside a custom GreatExpectationIOManager the data assets are materialized via GX SimpleCheckpoint()
and GX validation results are added as run output metadata.
One improvement which is still in progress, is the ability to add upstream dependency for the GX data assets like dbt models or raw files. As GX is in a different code location then our dbt projects, AssetSelection()
does not work. (https://dagster.slack.com/archives/C01U954MEER/p1690985736107259)
Right now the dependency is handled inside asset_factory with deps=AssetKey()
where the AssetKey of the GX Suite just matches the one from the dbt model (without a prefix). Problem is, we load non-prod assets to prod deployments and other way round and can run into incosistent states.
Trying to solve this issue by synchronizing the manifest.json from all our dbt projects to the GX code location and probably creating data assets based on a EnvVar for the specific environment.
As this is all custom, we are interested in your investigation as well @sandy.