Preserve untargeted Nested siblings during ClickHouse TTL mutation
After a Nested-field TTL, reconcile sibling arrays outside the intended mutation scope. Check that required business values survived separately from CHECK TABLE success before allowing further mutations.
Integrity does not define change scope
Values outside an approved TTL target must survive independently of table-integrity status. Truthound Core can compare prepared sibling arrays with a pre-mutation reference before accepting a completed mutation. [1, 2, 3]
CHECK TABLE misses a sibling loss
ClickHouse issue #129426 reports 26.10.2.103-stable clearing n.b=[x,y] when an expired TTL is applied only to n.a, while CHECK TABLE returns 1. The report also supplies a Cloud control. Readability and an integrity flag do not establish application-level sibling preservation. [1]
Trace fields by row identity
Track n.a and n.b separately by row ID before and after TTL. If untargeted n.b becomes empty, pause subsequent mutations and investigate affected keys. Preserve array order and escaping when preparing any comparison token. [1, 3]
x|y must not become empty
Define n.b=[x,y] and approve TTL only for n.a. The illustrative lossless token x|y is the expected sibling state. x|y passes; empty fails because it removes values outside the approved change even when the table remains readable. [1, 3]
Trust the reference and encoding
ColumnPairValidator in Truthound Core Python SDK 3.3.2 compares prepared non-null sibling tokens with ==. The operator supplies trustworthy pre-mutation data and unambiguous serialization. The SDK does not repair TTL storage or Nested offsets. [1, 2, 3]
Investigate from retained source
Use retained source or backup data to investigate the affected keys and verify a supported mutation path in a controlled table. A general CHECK TABLE success cannot replace that row-level comparison. [1, 3]
Keep the intended field scope
Keep the mutation’s intended field scope with the result. This lets an operational review identify an overbroad change without claiming that every readable part has preserved all business values. [1, 3]
Application conditions
Prepare TTL-targeted and untargeted arrays by row ID using lossless representations.
Alternatives
Investigate affected keys from retained source and test a supported mutation in control.
Limitations
CHECK TABLE success does not prove untargeted sibling preservation.
Evidence
- Event checked
- Subject checked
- Modified
