19913d85-f662-4518-a9a1-7adc1793dfd4.png){kind=small}
In the context of self-dependant assets, what woul...
# integration-snowflakem
Matt Clarke
06/05/2023, 5:42 PMIn the context of self-dependant assets, what would be the way to make a time-partitioned asset dependant on all past partitions of itself? We are wanting to construct an events table, where in order to calculate events on date t, we need all previous events. I see
AllPartitionMappings
sandy
06/05/2023, 10:09 PMThere isn't currently an explicit way to do this, but if you assign
start_offsetm
Matt Clarke
06/06/2023, 12:58 AMMakes sense, thanks :)
Matt Clarke
06/06/2023, 9:28 PMSomething we noted with this. This asset is downstream of a partitioned observable source asset, and we're seeing
Copy code
<partitions> cannot be materialized because upstream materializations are missing.s
sandy
06/06/2023, 10:54 PMWhere are you seeing that?
m
Matt Clarke
06/06/2023, 11:02 PMI have a daily partitioned observable source asset with a snowflake io manager, and downstream of that I have a self-dependent asset events_table with the partition mapping described above. When I go to materialise the events_table, it warns me that some upstream materialisations are missing
Matt Clarke
06/06/2023, 11:04 PMIf I ignore the warning and run it, it materialises fine so the warning isn’t accurate. In the case of the first partition of the events table, there are no materialisable assets upstream of it (no prior partitions of itself, and only a source asset upstream)
s
sandy
06/06/2023, 11:19 PMGot it - that does sound like a bug in the reporting. I filed an issue to track this: https://github.com/dagster-io/dagster/issues/14662.
m
Matt Clarke
06/06/2023, 11:23 PMThanks :) I’ll put together a minimal example to reproduce the issue tomorrow morning