https://dagster.io/ logo
#ask-community
Title
# ask-community
c

Casper Weiss Bang

01/02/2023, 6:49 AM
It seems i've found a bug. When you press "materialize" on an asset group that both contains partitioned and non partitioned assets, it seems that it materializes the non-partitioned asset in each of the backfills created, meaning the same asset will go through the same materialization for no particular reason.
t

Todd de Quincey

01/02/2023, 8:13 AM
I noted the same behaviour as well
From my understanding though, this isn’t a “bug” per se. Rather a design limitation which I believe the Dagster team are addressing (don’t quote me on that)
👍 1
c

Casper Weiss Bang

01/02/2023, 8:15 AM
right. the end result is the same; it is probably (for everyone) unintended behaviour. least a warning could be written.
blob 100 1
t

Todd de Quincey

01/02/2023, 8:16 AM
When I spoke to the Dagster team, they said that, at present, in situations like this, we need to backfill the partitioned asset on its own, then run it as part of a group. Not ideal, but they are aware of the limitation.
c

Casper Weiss Bang

01/02/2023, 8:17 AM
I ended up splitting it into two different asset groups for ease.
c

claire

01/03/2023, 6:09 PM
Thanks for raising this! This is actually something that will be fixed in the next couple of releases. In the future, backfills will be smarter i.e. for the situation you mentioned only one materialization of a non-partitioned asset will be generated
❤️ 1
🌈 1
t

Todd de Quincey

01/06/2023, 5:32 AM
This appears to be included in the latest release https://dagster.slack.com/archives/C01UC74PQAF/p1672972988388149
c

Casper Weiss Bang

01/09/2023, 9:16 AM
Woo thanks 🙏