Change retention of a truncate time partition - #6113
Conversation
roborivers
left a comment
There was a problem hiding this comment.
Cbuild submission: Success ✓.
Regression testing: Success ✓.
The first 10 failing tests are:
triggersc_latency
timepart_retention_alter
consumer_non_atomic_default_consumer_generated **quarantined**
builtin_ruleset
sc_downgrade [timeout] **quarantined**
ALTER TABLE <name> PARTITIONED BY TIME|MANUAL RETENTION <n> resizes a truncate partition's shard count without recreating the partition: increasing preserves all existing data, decreasing discards the oldest data down to the new retention. Legacy add&drop partitions still use PUT TIME PARTITION ... RETENTION; using PUT on a truncate partition, or ALTER on a legacy partition, is rejected. Signed-off-by: Dorin Hogea <dhogea@bloomberg.net>
eda8473 to
af1148d
Compare
roborivers
left a comment
There was a problem hiding this comment.
Cbuild submission: Success ✓.
Regression testing: Success ✓.
The first 10 failing tests are:
sc_resume_logicalsc_generated **quarantined**
cdb2jdbc
timepart_retention_alter
consumer_non_atomic_default_consumer_generated **quarantined**
sc_downgrade [timeout] **quarantined**
phys_rep_tiered [timeout]
phys_rep_tiered_nosource_generated [timeout]
phys_rep_tiered_firstfile_generated [timeout]
reco-ddlk-sql [timeout] **quarantined**
roborivers
left a comment
There was a problem hiding this comment.
Cbuild submission: Error ⚠.
Regression testing: Success ✓.
The first 10 failing tests are:
cdb2api_rollback_rc [failed with core dumped]
cdb2jdbc
timepart_retention_alter
consumer_non_atomic_default_consumer_generated **quarantined**
sc_downgrade [timeout] **quarantined**
New syntx:
ALTER TABLE PARTITIONED BY TIME|MANUAL RETENTION
It resizes a truncate partition's shard count without recreating the partition:
Legacy add&drop partitions still use PUT TIME PARTITION ... RETENTION; using PUT on a truncate partition, or ALTER on a legacy partition, is rejected.