paleolimbot commented on PR #41823: URL: https://github.com/apache/arrow/pull/41823#issuecomment-2139463628
> Thoughts on using "Unknown" instead of "Other" ? I recently was looking into this concept in Parquet and apparently they use the term "undefined" for this there. I think "unknown" best communicates this concept (as in, this is not a type that is known to the implementation); however, I don't have strong feelings about the name. > It's not entirely clear to me what the motivation is to bucket those other types together in a single arrow.other extension For something like nanoarrow this might work; however, in Arrow C++ the extension type information is aggressively dropped, so it's very possible that that a pyarrow consumer would never be able to query the extension name to get the relevant information (what the type name is and where it came from). One could argue that also maybe Arrow C++ should stop aggressively dropping extension information, but even with that I think that this extension type is a better solution than an extension name that a database might not even know that it has until it receives a query. -- 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
