https://dagster.io/ logo
#ask-community
Title
# ask-community
f

fred

08/15/2022, 10:59 AM
Hi! I’m a new user, taking the example project for a spin locally (v.1.0.3). I ran into some issues: 1. The
snowflake__recommender__comment_stories
step fails consitently with an error :
Copy code
dagster._core.errors.DagsterExecutionLoadInputError: Error occurred while loading input "comments" of step "snowflake__recommender__comment_stories":
The above exception was caused by the following exception:
dagster._check.CheckError: Invariant failed. Description: Can't load partitioned inputs
What could be the reason for this? 2. I’ve been trying to produce the “upstream changed” indicator to show up but have thus far failed. I have tried: • causing a Snapshot ID by changing metadata about the assets (succesfully caused ID change) and making code changes (did not cause ID change) • Re-materialized upstream assets AFTER materializing the downstream ones (both within an asset group, and between groups) • Running with and without the dagster-daemon. How does the “Upstream changed” indicator trigger?
🤖 1
Regarding 2. I think I figure it out. The issue is that the upstream changed indicator is not supported for partitioned dependencies. After materializing
activity_daily_stats
the
activity_forecast
showed the indicator correctly. The obvious followup question is then of course, why arent partitioned assets supported?
s

sandy

08/15/2022, 7:17 PM
for (2), I don't think there's a fundamental reason for it, but it can require fetching a lot of data, so we've been hesitant to add it until we can make sure the performance will be reasonable. there are also some semantic questions about when it's appropriate to show the indicator. I filed an issue to track this: https://github.com/dagster-io/dagster/issues/9374
for (1), that looks like a bug. thanks for catching this. here's a fix: https://github.com/dagster-io/dagster/pull/9375
f

fred

08/16/2022, 12:32 PM
Awesome, thanks @sandy for the quick actions!
4 Views