xixipi-lining commented on PR #521:
URL: https://github.com/apache/iceberg-go/pull/521#issuecomment-3160830511
The key difference is that UpdateNameMapping preserves existing name
mappings while adding new ones. For example:
```
// Original: {FieldID: 1, Names: ["foo"]}
// After update: {FieldID: 1, Names: ["foo", "foo_update"]}
```
This maintains backward compatibility by keeping the old name while adding
the new one, rather than replacing it entirely.
If I understand name mappings correctly, they're used to map field names to
field IDs when schemas don't have explicit IDs (like in Arrow schemas). So
preserving existing name mappings during schema evolution is important for
compatibility with existing data files that might reference the old field names.
--
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]
