sql: validate row level ttl schedule for insights tables #108911
Closed
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.
This change adds permanent migration to validate and schedule job for
row level TTL for system.txn_exec_insights and system.stmt_exec_insights
tables. It is necessary because RowLevelTTL for those system tables
defined as part of descriptors and isn't started.
Release note (sql change): ensure that row level TTL schedule is
valid and active for
system.txn_exec_insights
andsystem.stmt_exec_insights
tables.
Epic: None
Related to: #104582
Created on top of #104714 PR, only last commit should be reviewed.