-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[do not merge] Provide upstream asset materialization events to currently materializing asset #18916
Conversation
Current dependencies on/for this PR:
This stack of pull requests is managed by Graphite. |
dc32768
to
1922411
Compare
bb786c6
to
e3d8b45
Compare
70b8610
to
9051a62
Compare
7b3e547
to
d225e92
Compare
56a2790
to
047325b
Compare
cc86d44
to
482da77
Compare
047325b
to
75d69d2
Compare
482da77
to
bf99217
Compare
75d69d2
to
b7aba1e
Compare
bf99217
to
7c09193
Compare
b7aba1e
to
3f1cf4e
Compare
7c09193
to
8bd5fe7
Compare
3f1cf4e
to
19eee0e
Compare
8bd5fe7
to
41070f0
Compare
19eee0e
to
963ec15
Compare
963ec15
to
1141833
Compare
Deploy preview for dagit-storybook ready! ✅ Preview Built with commit 1141833. |
Deploy preview for dagit-core-storybook ready! ✅ Preview Built with commit 1141833. |
Summary & Motivation
Piggybacks on the data version computations to maintain a dictionary of the latest
AssetMaterialization
for all of the upstream dependencies for a materializing asset. This allows us to provide the asset materialization for an upstream asset in the compute function. In turn this provides access to metadataHow I Tested These Changes