Revanth14 opened a new issue, #2167: URL: https://github.com/apache/iceberg-go/issues/2167
### Feature Request / Improvement Follow-up from the #2164 review. iceberg-go writes v2 position delete files with `referenced_data_file` left nil. Readers and conflict validation work out the data file a delete file targets from its `file_path` bounds: when the lower and upper bounds are equal, that path is the target. #2141 showed how fragile this is. Truncated bounds made the lookup fail and fall back to partition scope. #2164 fixed the bounds, but bounds are still the only way to resolve the target. The spec allows `referenced_data_file` on position delete entries whose deletes all point at one data file. Java's `ContentFileUtil.referencedDataFile` checks this field first and uses the bounds only as a fallback. Proposal: when a position delete writer writes deletes for exactly one data file, set `referenced_data_file` to that path. Leave it nil when the file covers more than one data file. Out of scope: deletion vectors (v3), which already require `referenced_data_file`. -- 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]
