Preserve historical leaks data across post-processor runs#208
Merged
Conversation
Replace CREATE OR REPLACE TABLE with DELETE+INSERT scoped to the 30-day window so previous leak detection results are retained. The agg table still rebuilds from the full detail table each run.
mdowell12
approved these changes
Mar 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
CREATE OR REPLACE TABLEto rebuild the leaks detail table on every run, wiping all data outside the 30-day computation windowDELETE+INSERTscoped to the window, so historical leak detection results are preservedCREATE TABLE IF NOT EXISTSas an initialization step for new orgs that won't have a leaks table yet to delete from or insert intoKnown issue:
leaks_cadc_south_tahoeThis org's leaks table has an older schema (e.g.
FLOWTIMEinstead ofFLOWTIME_TS) from before column aliases were added to the leaks detection query insnowflake.py. The South Tahoe DAG is not currently running, so this is not a problem. If it's ever reactivated, the old table should be dropped first soCREATE TABLE IF NOT EXISTScan recreate it with the current schema.