Is your feature request related to a problem or challenge? Please describe what you are trying to do.
Right now, Schema metadata is encoded using HashMap and Field metadata is encoded using BTreeMap:
This is confusing and makes for awkward code.
Describe the solution you'd like
A single unified metadata type for both Schema and Field
Describe alternatives you've considered
- Standardize on either
HashMap or BTreeMap
- Standardize on either
Option<HashMap> or Option<BTreeMap>
- Make an
arrow specific Metadata type that wraps HashMap / BTreeMap and implements whatever extra behavior might be needed
Additional context
There is quite a bit of discussion on #2261
Is your feature request related to a problem or challenge? Please describe what you are trying to do.
Right now, Schema metadata is encoded using
HashMapand Field metadata is encoded usingBTreeMap:This is confusing and makes for awkward code.
Describe the solution you'd like
A single unified metadata type for both
SchemaandFieldDescribe alternatives you've considered
HashMaporBTreeMapOption<HashMap>orOption<BTreeMap>arrowspecific Metadata type that wraps HashMap / BTreeMap and implements whatever extra behavior might be neededAdditional context
There is quite a bit of discussion on #2261