Initialize OpenIVM metadata once per catalog - #16
Closed
lunstb wants to merge 1 commit into
Closed
Conversation
Author
|
drive-by ai slop, i let codex go off on its own seeing if openivm could improve ingestion for a project and then it decided to make this pr. I have not read it, would need to actually spend some time understanding architecture here lol |
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
1 participant
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
Creating every materialized view reruns the same system-table DDL; in a ten-view Starling-shaped pipeline that consumed 1.45s of 2.59s. We probe the current metadata schema and run migration DDL only when it is missing or stale, while retaining per-view stale-row and duplicate-name preflight.
Verification
test/sql/metadata.test: 143 assertionsEXCEPT ALL