Hey folks, I've got a use-case which I'd like to s...
# ask-community
c
Hey folks, I've got a use-case which I'd like to support that involves getting dagster to materialize a particular asset AFTER all other desired assets are materialized. Similar to the
Nothing
input type, is there anything I can do for assets to enforce the materialization ordering that I want?
a
Look at the non_argument_deps keyword argument in the @asset decorator, that works exactly how you described.
t
To back up Andras's recc, here are the docs that show you can use
non_argument_deps
https://docs.dagster.io/guides/dagster/non-argument-deps
c
thank you!
Seems like this arg requires an explicit set of assets that are prerequisites for the asset in question... is there a way to force execution LAST in the DAG?