jorisvandenbossche commented on PR #41823: URL: https://github.com/apache/arrow/pull/41823#issuecomment-2139537692
> The set of unknown types isn't a closed set. But also this extension type is not a closed set, as you can put whatever you want in the type_name and vendor_name metadata? > For something like nanoarrow this might work; however, in Arrow C++ the extension type information is aggressively dropped Then we should maybe consider if that behaviour in C++ is practical, otherwise this "arrow.other" type feels like a workaround for a limitation in the C++ API. In the past I had considered whether we (C++/pyarrow) should have a generic `UnknownExtensionType` subclass that is used for any extension type that is not recognized (i.e. for which the name is not registered). See https://github.com/apache/arrow/issues/22572 (however, doing that now _with_ dropping of the metadata in the schema's field metadata (as we do for registered types) would be a breaking change). -- 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: github-unsubscr...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
