tracking issue: Bump arrow-go / geoarrow-go versions to add logic type resolution for geo extension types

[C-Loftus]

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: duckdb/duckdb-iceberg#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.

• fix(parquet/pqarrow): Change interface name for arrow type on read for extension types arrow-go#1028
• feat(parquet/pqarrow): Read support for extension types / geo arrow-go#969
• feat(parquet/schema): Wire up logical type functionality for writing geo types arrow-go#960

And then in geoarrow-go I have implemented the necessary associated read/write interfaces:

• Parquet logical type write support geoarrow/geoarrow-go#5
• Add read support for geoarrow extension types from Parquet reader geoarrow/geoarrow-go#6

Outstanding tasks:

• Once 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.

[twuebi]

Thanks for the work @C-Loftus!

When trying to read Trino 483 written Geo, I hit a bunch of bumps along the way:

#1599
#1598
apache/arrow-go#1051
apache/arrow-go#1052

[C-Loftus]

Thank you likewise @twuebi and for that context!

If there is anything that needs to be done in geoarrow-go it could be useful to coordinate here. However it looks like from the PR's you linked it is mainly in the iceberg-go / arrow-go side of things?