happydave1 opened a new issue, #1107: URL: https://github.com/apache/iceberg-go/issues/1107
### Apache Iceberg version None ### Please describe the bug 🐞 `AssignFreshSchemaIDs (schema.go:1366)` renumbers reserved metadata column IDs along with everything else. When a v3 table's `_row_id` ends up at id=3 in the projection, `arrowAccessor.FieldPartner (table/arrow_utils.go:677)` will look up id=3 in file schemas — Java-written files have _row_id at id=MaxInt32-107, so we'd silently read whichever column the Java file has at id=3 instead. There are two ways to solve this issue: Either special-casing reserved ids in `AssignFreshSchemaIDs` or having `NewMetadata` reject metadata columns in the user schema (which matches Java). Both are reasonable. cc @laskoviymishka -- 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]
