refactor: convert Field::metadata to HashMap#3148
Conversation
d1b7e93 to
5f1d8e7
Compare
There was a problem hiding this comment.
Is this the correct way round?
There was a problem hiding this comment.
Technically this doesn't matter since HashMaps aren't ordered by default, so "who goes first" is implementation-defined by arrow, but I'll add a test.
tustvold
left a comment
There was a problem hiding this comment.
I'm not sure that the Ord implementation is correct, I'm also not sure we actually have any tests of it...
I would feel more comfortable with this, if we had a test that verified this
5f1d8e7 to
9367fe7
Compare
9367fe7 to
ba0f083
Compare
Co-authored-by: Raphael Taylor-Davies <1781103+tustvold@users.noreply.github.com>
|
Benchmark runs are scheduled for baseline = 6f8187f and contender = 57f91f2. 57f91f2 is a master commit associated with this PR. Results will be available as each benchmark for each run completes. |
Which issue does this PR close?
Closes #2262.
Closes #3086
Rationale for this change
Consistent metadata types, smaller memory footprint, easier size calculations (see #3147).
What changes are included in this PR?
Field::metadatais now aHashMapinstead of aBTreeMap.Are there any user-facing changes?