badalprasadsingh opened a new issue, #2604: URL: https://github.com/apache/iceberg-go/issues/2604
### Apache Iceberg version main (development) ### Please describe the bug 🐞 On a table upgraded from v2 -> v3, a mor "Delete" writes a dv that holds only the new delete, pos-deletes written before the upgrade are not copied into it. Once a data file has a dv, readers skip that file's old pos-delete files, so the rows those files deleted come back, no error is returned. what I mean: with `write.delete.mode=merge-on-read`: 1. v2 table, append ids `1, 2, 3` (one data file) 2. `Delete(id = 1)`: the scan gives `[2 3]` 3. `UpgradeFormatVersion(3)`: the scan still gives `[2 3]` 4. `Delete(id = 2)`: the scan gives `[1 3]`, expected `[3]` the same happens when one pos-delete file covers two data files: files `[1 2]` and `[3 4]`, `Delete(id IN (1, 3))`, upgrade, `Delete(id = 2)` gives `[1 4]`, expected `[4]` -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
