C-Loftus opened a new issue, #1569: URL: https://github.com/apache/iceberg-go/issues/1569
_Creating this mainly as an issue to track progress / dependencies in external repos._ Currently in iceberg-go geo data can be read / written, but the parquet logical type labeling is wrong leading to issues like this for query engines: https://github.com/duckdb/duckdb-iceberg/issues/1175 The iceberg schema shows geometry and the physical byte array type is correct but the parquet logical type isn't resolving the logical type mapping from the geo extension type. I have added logic in arrow-go to fix this. It created a new interface for resolving logical type <-> physical type for an arrow extension type. - [x] https://github.com/apache/arrow-go/pull/1028 - [x] https://github.com/apache/arrow-go/pull/969 - [x] https://github.com/apache/arrow-go/pull/960 And then in geoarrow-go I haev implemented the interfaces: - https://github.com/geoarrow/geoarrow-go/pull/5 - https://github.com/geoarrow/geoarrow-go/pull/6 Outstanding tasks: - Once https://github.com/geoarrow/geoarrow-go/pull/6 is merged and arrow-go has its version bumped, I will create a PR to bump the arrow-go version in geoarrow-go and then the arrow-go version in iceberg-go will need to be bumped. -- 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]
