[
https://issues.apache.org/jira/browse/ARROW-5342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rok Mihevc updated ARROW-5342:
------------------------------
External issue URL: https://github.com/apache/arrow/issues/21801
> [Format] Formalize extension type metadata in IPC protocol
> ----------------------------------------------------------
>
> Key: ARROW-5342
> URL: https://issues.apache.org/jira/browse/ARROW-5342
> Project: Apache Arrow
> Issue Type: New Feature
> Components: Format
> Reporter: Wes McKinney
> Assignee: Wes McKinney
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.14.0
>
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> On the heels of ARROW-585 and ARROW-5255, it has been proposed to add
> reserved keys to {{custom_metadata}} on the {{Field}} Flatbuffer type to pass
> along the name of a custom/user-defined data type and any serialized data
> required to reconstruct that data type.
> The objective of this is to enable library users to define new data types
> that are embedded semantically in pre-defined Arrow data types like Binary or
> FixedSizeBinary. For example, UUID could be defined as an extension type atop
> FixedSizeBinary(16) (though UUID may be important enough to formalize as a
> logical type at some point...)
> I will propose language to add to Metadata.rst and start a discussion on the
> mailing list to possibly call a vote
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
