Replies: 1 comment
-
Not sure if |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Imagine I have an upstream dynamically partitioned asset A and a downstream non-partitioned asset B:
When I'm running locally, I might want to debug asset_b. I'd like to do so by using just one partition of asset_a, which in my case is enough for asset_b to work. However, if I try to materialize asset_b without having materialized all partitions of asset_a I get a FileNotFoundError when dagster tries to read the materializations for all partitions of asset_a. I'd like for dagster to be able to load the specific partition I launched a run for, or at least all available ones, ignoring the ones that aren't available.
I've gone through the documentation, and played a bit with the PartitionMappings to see if I could achieve the desired effect, but I couldn't get it to work.
Does anybody have any ideas?
Beta Was this translation helpful? Give feedback.
All reactions