Establish the authority of Doris DETAIL before images
Reconcile a DETAIL changelog's before value with independent historical evidence before using it for retractions. Retain history settings and the update path without presenting source analysis as an observed execution.
An operation label is insufficient
A changelog that did not record old values cannot authorize retractions merely by labeling a row UPDATE_BEFORE. Truthound Core can compare prepared before values with independently retained update history. [1, 2, 3]
The unexecuted source prediction
Doris issue #70278 analyzes master with historical values disabled and predicts DETAIL emitting after values as before images for partial updates. The report and source-review follow-up explicitly did not run the SQL or a Flink job; runtime output and downstream impact remain predictions at the cited revision. [1]
Check history and write shape
Check historical-value configuration before using DETAIL for retractions. Retain independent old and new values and compare emitted operation/value pairs. Full-row upsert and partial-update controls exercise different paths and should remain separate. [1, 3]
The old 10 versus new 20 fixture
Define an illustrative update old=10,new=20, saving 10 before the update. Expected UPDATE_BEFORE value=10. Output 10 passes; 20 fails because it retracts the new value instead of the previous one. The independent history, not the emitted pair, establishes the reference. [1, 3]
The SDK cannot create history
ColumnPairValidator in Truthound Core Python SDK 3.3.2 compares prepared non-null before and expected-old columns. The operator captures change events and historical evidence. The SDK does not create missing history or turn source analysis into runtime reproduction. [1, 2, 3]
A replacement baseline alternative
Use a consumer mode that needs no old-row retraction or verify a properly prepared history-enabled replacement table and baseline. The follow-up says the setting cannot simply be altered in place at that revision; missing old images cannot be reconstructed from these rows. [1, 3]
Valid numbers can be wrong old values
A valid number inside the normal range can still be the wrong before image. Preserve value provenance and operation semantics so an apparently well-formed change record does not silently corrupt a retracting aggregate. [1, 3]
Application conditions
Prepare history configuration and independent old/new partial-update operation values.
Alternatives
Verify a nonretracting mode or a history-enabled replacement table with a fresh baseline.
Limitations
Do not claim that changelog or the SDK reconstructs unrecorded old images.
Evidence
- Event checked
- Subject checked
- Modified
