Skip to content

Encode Field and Schema metadata using the same type #2262

@alamb

Description

@alamb

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

  1. Standardize on either HashMap or BTreeMap
  2. Standardize on either Option<HashMap> or Option<BTreeMap>
  3. 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

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementAny new improvement worthy of a entry in the changelog

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions