laskoviymishka opened a new issue, #1006: URL: https://github.com/apache/iceberg-go/issues/1006
Parent: #589 v3-only fields like `next-row-id` and `encryption-keys` are silently accepted when they appear in a v1 or v2 `metadata.json`. This masks corrupt fixtures and cross-version bugs. Java rejects with a descriptive error per field; iceberg-go should match. Branch on `format-version` during metadata parse and error per forbidden field with a message naming the field and the format version it requires, e.g. `"v3-only field 'next-row-id' present in v2 metadata"`. The set of v3-only fields today is `next-row-id` and `encryption-keys`; if more land later, the same gate covers them. One unit test per gated field — load a v2 metadata.json with the v3-only field injected, assert a clear error. -- 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]
