JohnEarle opened a new issue, #17833: URL: https://github.com/apache/iceberg/issues/17833
### Apache Iceberg version 1.11.0 (latest release) ### Query engine Trino ### Please describe the bug 🐞 ContentFileParser does not serialize dataSequenceNumber and fileSequenceNumber, and the REST ContentFile schema does not define fields for them. Any file scan task that crosses the REST scan planning API therefore arrives with null sequence numbers on its data file and delete files. Delete files apply only to data files with an equal or smaller data sequence number, so an engine consuming those tasks cannot determine delete applicability at read time. **How I hit it:** I ran an engine's full connector test suite against a REST catalog that implements the scan planning endpoints and opts tables into server-side planning via scan-planning-mode=server. Every DELETE/UPDATE/MERGE-related test failed with a NullPointerException unboxing DeleteFile.dataSequenceNumber() in the merge-on-read read path, while append-only tables were unaffected. Any client that builds reads from REST scan tasks over tables with delete files should reproduce the same way. **Expected:** sequence numbers survive the JSON round trip, the same way the parser already preserves first-row-id (also commit-assigned metadata). ### Willingness to contribute - [x] I can contribute a fix for this bug independently - [ ] I would be willing to contribute a fix for this bug with guidance from the Iceberg community - [ ] I cannot contribute a fix for this bug at this time -- 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]
