C-Loftus opened a new pull request, #2221: URL: https://github.com/apache/iceberg-go/pull/2221
Closes https://github.com/apache/iceberg-go/issues/2193 In https://github.com/apache/iceberg-go/pull/2125#pullrequestreview-5502809355 there was a request to create an issue which decides what to do on geometry -> binary promotion. This would be the case in which someone has geospatial data in binary format in a V2 iceberg table. I had some discussion with other maintainers / community members in the iceberg #dev slack today and came to the conclusion that this promotion should not be allowed. Thus the current behavior stands, I just edited a few comments to make it more explicit. While theoretically possible to implement, the high chance for issues with mismatched/missing geospatial row group stats propagating to issues in query planners. A V2 Iceberg Table or naively written WKB column is likely to lack the proper geospatial row group statistics. As a result, writing other `GEOMETRY` typed info into the same column might cause a mismatch. Either way, it is very likely that old V2 / naively written binary columns would need to be migrated to V3 geometry to properly comply with the spec and have the proper spatial row group stats, so there doesn't seem to be significant benefit to allow this sort of promotion. -- 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]
