https://dagster.io/ logo
Title
a

Alex Service

03/09/2022, 4:37 PM
Bit of an edge case here, but if I materialize two partitions of a single
asset_key
between
asset_materialization_fn
triggers, only the latest asset materialization will be returned. It is notable that I’m using
run_key=None
currently
(I set a run_key and behavior doesn’t change)
p

prha

03/10/2022, 1:30 AM
Hi Alex. This is definitely something that we should support. Our initial asset sensor implementation was initially optimized for non-partitioned assets. I think adjusting the asset sensor API to handle multiple materializations should make this a lot easier to handle: https://github.com/dagster-io/dagster/issues/5699
a

Alex Service

03/10/2022, 6:47 PM
I need to be better at my searching before posting here 🙂 Thank you for sharing that
I’ve honestly had a pretty lousy time working with sensors and I think a lot of it has to do with my own expectation that something like an asset sensor would be event-driven rather than a polling loop, which seems to have been that person’s issue as well