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

Rishi Kulkarni

07/17/2023, 1:41 PM
Has anyone thought of an idiomatic way to represent persisted objects that are modified during the materialization of multiple assets? For example, a queue that's populated as a side effect of one asset materialization and drained as a side effect of a different asset materialization. I've just been representing this as a Resource, but I was wondering if there was a way to represent this object in a way that would allow me to take advantage of IOManagers, etc.
m

Mycchaka Kleinbort

07/17/2023, 1:42 PM
My first thought: isn't it strange that this asset will be changing during the running of your pipelines? It doesn't seem like something you can just "load" or "save" IOManager-style
c

claire

07/21/2023, 11:09 PM
Hi Rishi. I'd say the most accurate way to represent these "side effect" mutation objects would be in a resource, but unfortunately I don't think you'd be able to use them with IO managers, since it's unclear how these kinds of objects can be persisted