While we have the custom_metadata field at the Field level, it may be useful to have a proper user-defined type metadata in the Type union, which would allow us to provide a physical representation type (e.g. "Latitude longitude is represented by a struct, whose children consist of two doubles") from the other non-user defined types.
This is more flexible than custom_metadata because we can leverage existing structure in the Flatbuffers for describing the user type
https://github.com/apache/arrow/blob/master/format/Schema.fbs#L285
Reporter: Wes McKinney / @wesm
Assignee: Wes McKinney / @wesm
Note: This issue was originally created as ARROW-1587. Please see the migration documentation for further details.
While we have the custom_metadata field at the Field level, it may be useful to have a proper user-defined type metadata in the
Typeunion, which would allow us to provide a physical representation type (e.g. "Latitude longitude is represented by a struct, whose children consist of two doubles") from the other non-user defined types.This is more flexible than
custom_metadatabecause we can leverage existing structure in the Flatbuffers for describing the user typehttps://github.com/apache/arrow/blob/master/format/Schema.fbs#L285
Reporter: Wes McKinney / @wesm
Assignee: Wes McKinney / @wesm
Note: This issue was originally created as ARROW-1587. Please see the migration documentation for further details.