oliver zaufke

01/11/2023, 4:54 PM
Hi there! Is there an issue with having both an op which explicitly materializes an asset, for which a corresponding software defined partitioned asset also exists?


01/11/2023, 7:10 PM
Hi Oliver - this should work. That op just won't be called if you hit the materialize button on the asset

oliver zaufke

01/12/2023, 8:43 AM
Thx for replying. I was aware of that, but it seems that when I explicitly materialize the asset key from the op with the corresponding software defined asset and I have other assets which are dependent (downstreams) of that asset, they remain stale both after materializing via a sensor/asset_job and manual materialization in dagster gui.
I guess this can be achieved by handing over the appropriate metadata_entries attribute in AssetMaterialization for the PathMetadataValue. I will try that.