-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
[external assets] source assets -> external assets #18217
[external assets] source assets -> external assets #18217
Conversation
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @smackesey and the rest of your teammates on Graphite |
Deploy preview for dagit-core-storybook ready! ✅ Preview Built with commit 5ebeac7. |
94579d5
to
76e746d
Compare
5503f7f
to
33d754c
Compare
76e746d
to
1aa3b00
Compare
33d754c
to
fc5f310
Compare
1aa3b00
to
2efc378
Compare
fc5f310
to
375c613
Compare
2efc378
to
1bfc23d
Compare
ce7dd71
to
dc76212
Compare
e3bb98c
to
8b0fb54
Compare
1625c87
to
1670c1f
Compare
e3772e2
to
0fb2e11
Compare
a8a9ee5
to
db14c71
Compare
db14c71
to
f5c0284
Compare
f5c0284
to
5ebeac7
Compare
d881aa6
to
a1490ca
Compare
36d76b2
to
be3a82e
Compare
be3a82e
to
33f844e
Compare
5ebeac7
to
24d608d
Compare
3233518
to
08255d1
Compare
5b214ac
to
3bfbef8
Compare
3bfbef8
to
05b414b
Compare
Superseded by another stack. |
Summary & Motivation
Internally convert source assets to external assets. This happens at the level of
RepositoryData
-- we do the conversion here instead of inDefinitions
so that conversion works for both@repository
andDefinitions
."Source assets" no longer exist as a concept at the level of
ExternalAssetNode
, but still exist over the GQL API to keep the representation in Dagster UI constant. A newisExternal
field is also added to GQL asset nodes.A caveat is that
auto_observe_interval_minutes
can not be perfectly translated to an auto-materialize policy, because there is no way to capture "every N minutes" exactly as a cron expression (andAutoMaterializeRule.materialize_on_cron
is the closest option available). I used a mapping that gets us pretty close though where we round to the nearest minute/hour/day for the number of minutes.How I Tested These Changes