Skip to content
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

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

gibsondan
Copy link
Member

@gibsondan gibsondan commented Jul 30, 2024

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)

Copy link

github-actions bot commented Jul 30, 2024

Deploy preview for dagit-core-storybook ready!

✅ Preview
https://dagit-core-storybook-cltpeeawb-elementl.vercel.app
https://newfailureevents.core-storybook.dagster-docs.io

Built with commit f06448d.
This pull request is being automatically deployed with vercel-action

@gibsondan gibsondan force-pushed the newfailureevents branch 4 times, most recently from 1dffe88 to da29775 Compare July 30, 2024 18:27
@gibsondan gibsondan changed the title Add ASSET_MATERIALIZATION_FAILURE event Add batch-writable ASSET_MATERIALIZATION_FAILURE event Jul 30, 2024
@gibsondan gibsondan requested a review from prha July 30, 2024 18:28
@gibsondan gibsondan marked this pull request as ready for review July 30, 2024 18:28
@gibsondan gibsondan force-pushed the newfailureevents branch 2 times, most recently from b6de440 to a598183 Compare July 30, 2024 18:55
@gibsondan gibsondan force-pushed the newfailureevents branch 6 times, most recently from 3fcd11c to 677b697 Compare August 9, 2024 15:20
@gibsondan gibsondan changed the base branch from master to eventlogstoragetests August 9, 2024 15:20
Comment on lines 250 to +254
values = self._get_asset_entry_values(event, event_id, self.has_asset_key_index_cols())

if not values:
return

Copy link
Member Author

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

@gibsondan gibsondan force-pushed the newfailureevents branch 3 times, most recently from bd15c13 to 2cacbad Compare August 9, 2024 18:01
@gibsondan gibsondan requested a review from sryza August 9, 2024 19:58
@gibsondan gibsondan force-pushed the eventlogstoragetests branch from e6a803c to 6499e97 Compare August 9, 2024 21:25
@gibsondan gibsondan force-pushed the eventlogstoragetests branch from 6499e97 to 61ac886 Compare August 12, 2024 15:20
Base automatically changed from eventlogstoragetests to master August 12, 2024 17:20
@gibsondan gibsondan changed the title Add batch-writable ASSET_MATERIALIZATION_FAILURE event Add batch-writable PLANNED_ASSET_MATERIALIZATION_FAILURE and PLANNED_ASSET_MATERIALIZATION_SKIPPED events Aug 15, 2024
Copy link
Member

@prha prha left a 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?

Copy link
Member

@schrockn schrockn left a 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.

@gibsondan
Copy link
Member Author

gibsondan commented Sep 3, 2024 via email

@gibsondan gibsondan marked this pull request as draft December 27, 2024 15:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants