Styxis
Company
Knowledge

RisingWave DELETE after an upsert: inspect prior state before cancelling operations

Deleting a new insertion and deleting an overwrite of an existing row are different state transitions.

The same operation names can mean different transitions

An Insert–Delete pair can describe either a new row or an overwrite of existing state. A final-state Truthound check needs evidence of key presence in the earlier barrier and of the last intended operation. [1, 2, 3]

Source analysis, not an executed reproduction

The public RisingWave analysis notes that a compactor cancelling an upsert Insert and subsequent Delete as a new insertion and removal can leave a row previously delivered downstream. The source explicitly reports inspection and operation tracing without a local build or runtime reproduction. This article likewise does not describe a confirmed operational incident. [1]

An illustrative test with an existing key

If an illustrative key existed previously and its final operation is delete, its final present state must be false. A final present state of false reflects deletion of the existing key. A true state means the earlier barrier’s key remains downstream, violating the completed-delete condition. A test containing only a new key can miss the issue because cancelling both operations still leaves the correct absence. Test keys with and without prior state separately. [1, 3]

The final state Truthound can check

Include keys existing before the barrier and inspect their absence after update followed by delete. Do not report the source-analysis hypothesis as an executed incident reproduction. Truthound Core's ConditionalExpressionValidator can check key survival in the scope whose final operation is delete. It does not establish the compactor's input semantics or execute the reproduction; obtain controlled evidence for the deployed version separately. [1, 2, 3]

Application conditions

Establish existed_before_epoch, final_operation and present_after_epoch for the same key and epoch from prior-barrier records and completed-state reads.

Alternatives

Create separate compactor regression controls for previously existing and newly inserted keys.

Limitations

  • Truthound does not determine compactor input semantics or replace runtime reproduction of a source-derived hypothesis.

Evidence

Event checked
Subject checked
Modified