You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@iceberg.apache.org by "dwilson1988 (via GitHub)" <gi...@apache.org> on 2024/10/23 22:22:41 UTC

[I] Iceberg Extensions [iceberg-go]

dwilson1988 opened a new issue, #183:
URL: https://github.com/apache/iceberg-go/issues/183

   ### Feature Request / Improvement
   
   There are some various table formats that extend Iceberg by allowing additional metadata to be added to various components, for example, [Havasu](https://github.com/wherobots/havasu/tree/main). I (and I'm sure others) would like the ability to to extend metadata such as the table metadata, manifest lists, and manifest entries to read additional metadata. I can't speak for all iceberg extensions, but havasu extends iceberg by adding some additional metadata fields in:
   1. Table Metadata: https://github.com/wherobots/havasu/blob/main/spec.md#table-metadata
   2. Manifests: https://github.com/wherobots/havasu/blob/main/spec.md#manifests
   
   The addition of the geometry bounds on the manifests is primarily for scan planning. It seems like at this point, until Iceberg support for geospatial types is added (which seems like it could be in the [fairly distant future](https://github.com/apache/iceberg/issues/10260)), augmenting scan planning may be a bit far away, but I'd propose that allowing metatadata extensions to table metadata and manifests maybe be worth consideration.
   
   There are probably many ways this could be implemented, and I'm happy to take a stab at it since it's something I personally need on my project. First I wanted to ask if this is within the scope of this project or if you have a recommended path to something like this?
   
   


-- 
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: issues-unsubscribe@iceberg.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org


Re: [I] Iceberg Extensions [iceberg-go]

Posted by "zeroshade (via GitHub)" <gi...@apache.org>.
zeroshade commented on issue #183:
URL: https://github.com/apache/iceberg-go/issues/183#issuecomment-2435645016

   I'd have to think about it a bit as far as recommending a path. But I would definitely see this as within the scope of this implementation if we can come up with a good/useful way to do so.


-- 
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: issues-unsubscribe@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org