paleolimbot commented on PR #8998: URL: https://github.com/apache/arrow-rs/pull/8998#issuecomment-3657410343
> This is probably overkill for just variant, it would also make a nice API for other potential extension types (like some of the geospatial types from This is 100% Kyle, but the place where geoarrow-rs does the encoding is here: https://github.com/geoarrow/geoarrow-rs/blob/main/rust/geoarrow-geojson/src/encoder/factory.rs#L19-L23 ...slightly different because the GeoJSON standard keeps geometry at the center of the universe (everything else is "properties"). Given the opportunity I think we'd be able to put pluggable encoders and decoders to good use. > Long(er) term I think its worth considering a more seamless integration for the canonical extension types. As a casual user it would be nice to not have to treat them any differently than standard types. In DataFusion we've been discussing a registry as a centralized place to customize how these types are handled so that built-in components can handle them ergonomically (https://github.com/apache/datafusion/issues/18223). I don't know as much about the expectation of arrow-rs users but most of the things we're discussing there at the moment are just packaging customizations of arrow-rs components. -- 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]
