feat: support storage policy in table details and create matview quick action#563
Open
emrberk wants to merge 5 commits into
Open
feat: support storage policy in table details and create matview quick action#563emrberk wants to merge 5 commits into
emrberk wants to merge 5 commits into
Conversation
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.
Two related changes around retention on Enterprise.
Matview generator:
Create materialized viewon a table withSTORAGE POLICY(...)was throwing an error. The generator now projects each clause into the matview's partition unit (DAY → DAYS, MONTH → MONTHS, YEAR → YEARS), preserves thetoParquet ≤ dropNative ≤ dropLocal ≤ dropRemoteorder, and ladder-bumps the terminal clause so the matview retention outlives the source. TTL is floored at the partition unit with the same logic.Table details drawer: The drawer now surfaces storage policy:
ttlValue !== 0).Test plan
STORAGE POLICY(...)→Create materialized view→ resulting DDL validates on Enterprise (months-based, monotonic).