Reconcile acknowledged concurrent Iceberg REST changes after commit
When concurrent REST updates each receive a success response, check that fresh table state retains every acknowledged property key. Judge preservation by the identity of the changes rather than the number of successful codes.
Preserved changes matter more than codes
Completion responses need confirmation that accepted changes survive a fresh table load. Truthound Core can compare a prepared acknowledged-property set with the metadata actually retained after concurrent requests. [1, 2, 3]
A concurrent transaction report
Iceberg issue #18758 reports REST fixture 1.10.1 and Hive REST catalogs returning two 200 responses while one same-table change disappears. Single-table and sequential controls differ. The report distinguishes this retry behavior from requirements on tables untouched by a transaction. [1]
Keep two fresh loads
Record table UUID, each requested property, response code, and two later loads. For nonexclusive property changes, reconcile every 2xx-acknowledged key. Guarded snapshots need a separate conflict contract where accepting both may itself be invalid. [1, 3]
writer_a and writer_b
Declare illustrative writer_a and writer_b property changes both acknowledged with 2xx. Expected set=writer_a|writer_b. Both keys pass; writer_a alone fails because the accepted writer_b change is missing. This fixture is not the mutually exclusive empty-main snapshot case. [1, 3]
Set checks do not retry commits
DistinctValuesEqualSetValidator in Truthound Core Python SDK 3.3.2 compares the exported property-key column with the approved set. The operator collects fresh loads and responses. The SDK does not retry transactions or guarantee concurrency control. [1, 2, 3]
Verify endpoints and conflicts
Review a supported single-table endpoint or serialized route, and test appropriate conflict rejection for guarded snapshots. A timeout or failed later load remains inconclusive rather than proof that a change was lost. [1, 3]
Identify the accepted change
The approval artifact should say which change was accepted and which state retained it. A success-code count cannot answer that identity question even when the total number of requests looks correct. [1, 3]
Application conditions
Prepare table UUID, per-request 2xx properties, and two fresh loads.
Alternatives
Verify single-table/serialized paths and appropriate guarded rejection.
Limitations
Mutually exclusive snapshot guards need a conflict contract distinct from preserving two successes.
Evidence
- Event checked
- Subject checked
- Modified
