[
https://issues.apache.org/jira/browse/ARROW-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763898#comment-16763898
]
Wes McKinney commented on ARROW-585:
------------------------------------
I'm going to take a stab at a prototype of this. The idea is that the type's
{{id()}} method will return {{Type::USER_DEFINED}}, and {{UserDefinedArray}}
will have an API to return the physical representation of the data (which might
be {{BinaryArray}} or something else depending on what kind of data it is).
Then {{UserDefinedArray}} can be static-casted by application code to the
desired container type.
Python code can define similar wrapper-callbacks. This can be used to implement
the "uuid" type that's been discussed elsewhere (though it may make sense at
some point to add that to the spec)
I think user-defined types can also be a useful way to experiment with new data
types which may or may not formally become part of the Arrow specification.
cc [~xhochy] [~leif] for any thoughts
> [C++] Define public API for user-defined data types
> ---------------------------------------------------
>
> Key: ARROW-585
> URL: https://issues.apache.org/jira/browse/ARROW-585
> Project: Apache Arrow
> Issue Type: New Feature
> Components: C++
> Reporter: Wes McKinney
> Priority: Major
> Fix For: 0.13.0
>
>
> This will include:
> * Implementing a subclass of DataType
> * A "fallback" mechanism for receivers that do not understand our custom
> metadata
> * Implementing a serializer interface for custom metadata (to be send and
> received in an IPC setting)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
