paleolimbot commented on PR #41823: URL: https://github.com/apache/arrow/pull/41823#issuecomment-2139767614
> The driver not knowing about this type seems to be a choice you make in the implementation Probably a better example would be a user-defined type (type alias for a built-in or extension type) or a type from a loaded extension (which the ADBC driver would never have an opportunity to know). I think the example was changed to `"geometry"`, which is from an extension (although we could hard-code support for PostGIS). > That avoids requiring a specific implementation for this on the Arrow side. If extension type information wasn't dropped in multiple implementations this would probably work. Ensuring extension type registration in the presence of shared/static libraries and multiple languages is not trivial (as we know from considering this for geoarrow 🙂 ). > since it seems this mostly comes from ADBC use cases I think this issue comes up at any place data is converted to Arrow from something else. In R we (I) invented the undocumented `arrow.r.vctrs` extension type to handle something like this (unknown type name but storage that we do know how to convert). That's an example where the ability to attach some extra payload would be helpful (but also one where an extension type is fine because it only applies to one binding). -- 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]
