You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@arrow.apache.org by GitBox <gi...@apache.org> on 2021/09/02 18:28:38 UTC
[GitHub] [arrow] jorgecarleitao commented on pull request #11071: ARROW-13855: [C++][Python] Implement C data interface support for extension types
jorgecarleitao commented on pull request #11071:
URL: https://github.com/apache/arrow/pull/11071#issuecomment-911948221
Can't review the c++ in depth, but from what I can read, I took an equivalent approach (https://github.com/jorgecarleitao/arrow2/pull/363), which I am glad of.
To import
1. read metadata
2. detect extension from meta
3. use extension
To export
1. create meta map with extension name and meta
2. fill meta map with remaining meta from field
3. unwrap inner extension
4. expose in c data interface
There is a small divergence in that we remove the extension fields from the field's metadata when consuming from IPC and FFI, and automatically convert them to the `DataType::Extension` variant (and vice-versa on export). AFAI understand this is an implementation detail that does not impact how they communicate.
--
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-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org