Styxis
Company
Knowledge

Keep net-zero rewrites from erasing a Doris offset snapshot key

A same-value rewrite can still require the earlier row in an offset-based snapshot. Test the effect of net-delta elimination against keys fixed at that offset while preserving the report's unexecuted-scenario scope.

No change does not mean absence

No net change does not mean a key was absent at the earlier offset. Truthound Core can compare a prepared snapshot key set with an independently retained offset image. [1, 2, 3]

MIN_DELTA and reconstruction

Doris issue #70277 analyzes a MoW snapshot reconstruction where a rewritten current row is newer than the offset and MIN_DELTA suppresses equal endpoints. The report and follow-up have not executed the SQL or IVM refresh. Join-IVM consequences are supported as a possible path, not a measured outcome. [1]

Keep the earlier image

Fix keys present at the consumption offset, then apply an identical rewrite. Compare @snapshot keys with that earlier image. Do not treat ordinary net-delta elimination as proof that a historical before image is unnecessary. [1, 3]

Two keys remain in the past

At the illustrative offset, (1,a) and (2,b) exist. A later identical write of (1,a) leaves expected past keys=1|2. That set passes; set 2 fails because key 1 existed at the offset. Value round trips such as a to b to a require the same historical distinction. [1, 3]

Align offset and expected set

DistinctValuesEqualSetValidator in Truthound Core Python SDK 3.3.2 checks the extracted key column against expected_values. The operator establishes offset alignment and the earlier image. The SDK does not fix snapshot rebuild or incremental-view joins. [1, 2, 3]

Separate net consumption and restoration

Test snapshot restoration separately from net-change consumption, including delete/reinsert and round-trip values. The follow-up says changing stream type does not bypass the hard-coded reconstruction scan, and DETAIL alone is not a complete substitute. [1, 3]

Conceptual does not mean executed

Preserve the unexecuted status of the reported scenario while preparing the acceptance test. A clear conceptual counterexample is useful without claiming that a live deployment has already lost that key. [1, 3]

Application conditions

Prepare the independent offset image and snapshot keys after an identical rewrite.

Alternatives

Keep net-change consumption and snapshot-restoration tests separate.

Limitations

  • Do not present a source-derived possible IVM path as an executed refresh result.

Evidence

Event checked
Subject checked
Modified