qinghui-xu commented on issue #15313: URL: https://github.com/apache/iceberg/issues/15313#issuecomment-4143611777
Dropping only `key` or `value` or both fields from `map` without dropping `map` field itself will lead to failure (there are tests in `TestSchemaUpdate` ensuring this). > Why would dropping them explicitly be better than just dropping the whole thing? It's not necessarily "better" than just dropping map field itself. But I feel it's a bit confusing if dropping `map.key` (or `map.value`) is not allowed while I am dropping `map` field itself. When I was implement my tooling, it's just natural to compare to drop whatever is stale from the table and the spec does not seem to suggest otherwise. Or do you think it's preferable to make this explicit in the spec that "key" and "value" columns themselves cannot be dropped in a map field? -- 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]
