-
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
Add batch-writable PLANNED_ASSET_MATERIALIZATION_FAILURE and PLANNED_ASSET_MATERIALIZATION_SKIPPED events #23327
base: master
Are you sure you want to change the base?
Conversation
Deploy preview for dagit-core-storybook ready! ✅ Preview Built with commit f06448d. |
1dffe88
to
da29775
Compare
b6de440
to
a598183
Compare
3fcd11c
to
677b697
Compare
values = self._get_asset_entry_values(event, event_id, self.has_asset_key_index_cols()) | ||
|
||
if not values: | ||
return | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
possible point of discussion - I am not currently updating the "last_run_id" or "last_materialization_timestamp" columns on this new event type, although i certainly could (both of those columns are currently updated on planned and materialization events)
It looks like the main place we use the timestamp column is in the context of wipes
bd15c13
to
2cacbad
Compare
e6a803c
to
6499e97
Compare
2cacbad
to
43bdc22
Compare
6499e97
to
61ac886
Compare
43bdc22
to
c3087c3
Compare
c3087c3
to
7a9b38e
Compare
7a9b38e
to
41c0a54
Compare
41c0a54
to
f06448d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why did you decide to keep PlannedAssetMaterializationFailure
rather than just PlannedMaterializationFailure
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are you planning on merging this? Just cleaning up my PR queue.
I am planning to merge this, yes. I was planning to get the stack working
end-to-end before doing so and got pulled into some other things.
…On Tue, Sep 3, 2024 at 6:23 AM Nick Schrock ***@***.***> wrote:
***@***.**** commented on this pull request.
Are you planning on merging this? Just cleaning up my PR queue.
—
Reply to this email directly, view it on GitHub
<#23327 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACAPJCYT7I5TD447724AD4TZUWL2DAVCNFSM6AAAAABLVJFYEOVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDENZXGE2DSMZYGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Summary & Motivation
Doesn't actually add any write callsites yet, but provides the class and storage adjustments needed to write this event from either user code or a daemon.
How I Tested These Changes
BK (had to adjust the various TestEventLogSTorage subclasses to be able to access the instance)