qinghui-xu commented on PR #15560: URL: https://github.com/apache/iceberg/pull/15560#issuecomment-4124454437
It "always" happens in our case whenever our automated process need to drop a map field (but we only encounter such cases from time to time). In fact our automation compares expected table schema and the current one, and drops / adds fields accordingly. In the case of finding an extra map field, it will also find the extra key and value nested fields, so it tries to drop them altogether. Current implementation does not allow that and throws an exception, and I think it's legitimate to drop nested fields when dropping the parent 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]
