Support custom metadata for schema and columns #20
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #13. This PR adds two new functions:
Arrow.getmetadata(x)
andArrow.setmetadata!(x, ::Dict{String, String})
, which allows, ratherobviously, setting metadata for an arbitrary object and then retrieving
that metadata. By utilizing these functions, users can get/set custom
metadata that is serialized in the arrow format at the schema level and
field (column) level. More specifically, to set arrow schema custom
metadata, a user would call
Arrow.setmetadata!(tbl, meta)
on theirtable object
tbl
. To retrive arrow schema custom metadata, one cancall
tbl = Arrow.Table(...); meta = Arrow.getmetadata(tbl)
. Similarlyfor column/field-level metadata, one can call
Arrow.setmetadata!(col, colmeta)
to cause custom metadata to be serialized in the arrowmessage, and call
Arrow.getmetadata(tbl.colX)
to retrive custommetadata for a specific column in an
Arrow.Table
.Note that technically the arrow
Message
andFooter
objects alsoallow setting custom metadata, but those are not addressed at all in
this PR since they seem to be less useful/urgent.