Iceberg v3 support via duckdb iceberg extension?

[C-Loftus]

Thank you for the amazing work on GeoLibre!

I was wondering what folks thought about adding support for Iceberg v3 with its geo types via GeoLibre. Although Iceberg would typically be used for datasets far beyond the size that could be visualized in the browser, some organizations use it moreso as a way for tracking updates to Parquet files with Geo data. In such a scenario its size would be feasible to visualize as another integration in Geolibre.

This would obviously add another dependency within duckdb so no worries if it is out of scope!

[C-Loftus]

There's a good chance I could likely assist on this as well if you'd like! I did a fair bit of work on the geo support within iceberg-go so I feel I know the format fairly well at this point

[giswqs]

Thank you for the suggestion. I have not used iceberg yet. Can the dependency be lazy loaded? Do you know how much file size increase to the releases with the new dependency?

Alternatively, it can be added as an external plugin. https://plugins.geolibre.app

[C-Loftus]

Thanks for your reply!

I am not sure if this would be considered lazy loaded, but you install the extension via the following commands.

INSTALL iceberg;
LOAD iceberg;

This install could be deferred until the user selects iceberg layer as an option.

I checked the extension file size locally and on macos it is around 32MB.

du -h ~/.duckdb/extensions/*/*/iceberg.duckdb_extension
 32M	/Users/cloftus/.duckdb/extensions/v1.5.2/osx_arm64/iceberg.duckdb_extension
 32M	/Users/cloftus/.duckdb/extensions/v1.5.4/osx_arm64/iceberg.duckdb_extension

I would be happy to investigate a plugin if you think it would be a better fit!

[giswqs]

@C-Loftus Please feel free to submit a PR to implement it in GeoLibre using lazy INSTALL iceberg; LOAD iceberg.

[C-Loftus]

Great will do thanks for your response on this! I am going to wait until I get one or two more PRs merged in upstream iceberg-go (apache/iceberg-go#1569) to round out the geo support that way I can generate some simple test fixtures and ensure the duckdb extension has parity across iceberg implementations