geoHeil07/09/2022, 10:08 AM
models: target: # Config indicated by + and applies to all files under models/example/ example: +materialized: view
directory to an asset group - which is colliding with my manual mapping 1) when the names are different 2) when they are the same as it is only allowed to set the group once.
which should both show up in dagit as asset groups named foo and bar and a
directory with a sub folder also for models specific to foo and bar how can I get the respective python and DBT assets to show up in the same asset group?
sandy07/11/2022, 3:01 PM
owen07/11/2022, 4:42 PM
geoHeil07/11/2022, 8:53 PM
is translated to an implicit asset group which may or may not exist - even when not specifying any additional keys when loading the DBT assets.
owen07/11/2022, 11:44 PM
, in dagit, this would show up as a source asset without a definition (basically just some grey text, rather than a box), and this key would not be associated with any asset group -- is that matching up to what you're seeing or is something else happening?
geoHeil07/12/2022, 5:40 AM
both times. In such a case then even though the data is flowing in a DAG from a-z the lineage will be broken and a source asset will be created. Assuming my assetgroup foo with prefix bar is writing data to a database in schema bar then the source.yaml is bar.mytable but dagit right now would also expect this to be in asset group bar.