lxy-9602 commented on PR #525:
URL: https://github.com/apache/paimon-cpp/pull/525#issuecomment-6719223128
The code LGTM. I also reproduced a similar issue in Java partial-update with
`partial-update.remove-record-on-delete=true` and DVs disabled:
```text
1. Commit (id=1, a=10, b=20) and compact it into a high-level file.
2. Commit DELETE(id=1).
3. Commit UPDATE_AFTER(id=1, a=30, b=null).
Reading at this point correctly returns (id=1, a=30, b=null).
4. Run a partial compaction that merges only the two newer L0 files,
leaving the older high-level file untouched.
Reading now incorrectly returns (id=1, a=30, b=20).
Reopening the table gives the same incorrect result.
```
The intermediate merge loses the delete boundary, allowing the old `b=20` to
reappear during subsequent merging.
Given that Java also has this issue, perhaps we could adjust the issue and
PR descriptions to clarify that it is a shared defect in the existing merge
semantics. A reference to #524 may be sufficient, without presenting it as an
additional correctness boundary for this realtime feature.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]