Kontinuation opened a new pull request, #12667: URL: https://github.com/apache/iceberg/pull/12667
This PR adds support for parsing and serializing geospatial bounds, partially implementing the iceberg geo spec: https://github.com/apache/iceberg/pull/10981. It also resolved remaining review comments in https://github.com/apache/iceberg/pull/12346. 2 spatial predicates were added to operate on geospatial bounds: * `ST_INTERSECTS`: Test if 2 geospatial bounds intersects with each other * `ST_DISJOINT`: The negation of `ST_INTERSECTS`. A new subclass of `BoundPredicate` named `BoundGeospatialPredicate` was added to represent bound geospatial predicates. `BoundGeospatialPredicate` do not support evaluating on WKB encoded geometry/geography values, handling of geospatial predicates were implemented by expression visitors to support metrics evaluation on geospatial bounds. I can divide geospatial bound classes and spatial predicates into 2 PRs, but I'd like to know if my approach of adding geospatial predicates is OK before proceeding. -- 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]
