laskoviymishka opened a new issue, #1086: URL: https://github.com/apache/iceberg-go/issues/1086
Follow-up from #1069, open question. #1069 hard-errors on `next-row-id` / `encryption-keys` in v1/v2 metadata. None of the reference clients do this — Java reads `next-row-id` only when `formatVersion >= 3` and defaults otherwise, has no version guard on `encryption-keys` at all; PyIceberg and iceberg-rust both drop unknown fields. So we're the only one that rejects here. Doesn't bite today because v3 isn't widely deployed. Once downgrade tooling shows up, a v2 file with stray v3 fields reads everywhere except Go. Strict surface has value (mis-versioned metadata is by definition wrong, and it catches our own writer if it ever leaks v3 fields), but forward-compat is also a spec goal. If we keep it strict, a code comment near `rejectV3OnlyFields` capturing the intentional divergence would help future readers not read it as a parity bug. -- 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]
