Expoze Dummy03/01/2023, 4:33 PM
Zach03/01/2023, 7:12 PM
op as a graph-backed asset, with the results of the QC checks being your asset. Then the GreatExpectations asset graph could depend on the asset you want to QC.
Another idea (might be a little more of a hack) that I personally haven't tried before would be to use the new `root_input_manager` abstraction to load the asset by just embedding the same logic the upstream asset's IOManager uses to load the asset's value. This wouldn't be recognized as a dependency between the op and the asset by Dagster, which may or may not be what you want (the graph-backed asset approach would show your
asset as stale every time you materialized the upstream, which may or may not be what you want).
Other than that I don't think there's a Dagster-native way to load an asset from an op, but I think it's a feature that's on the Dagster team's radar as it comes up pretty regularly.
sandy03/01/2023, 10:11 PM
Expoze Dummy03/03/2023, 4:19 PM
. I'll see if this will work 🙂
Terry Dontje04/17/2023, 2:47 PM