[
https://issues.apache.org/jira/browse/ARROW-7173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17100850#comment-17100850
]
Antoine Pitrou commented on ARROW-7173:
---------------------------------------
Hmm, I'm looking at this and it doesn't fit well with how map types are treated
in C++ currently. The IPC side ignores the field names completely when
receiving a map type, instead normalizing it (but it does seem to emit the
names in the write side). The C++ MapType doesn't have any provision for custom
field names (though that could be added).
> [Integration] Add test to verify Map field names can be arbitrary
> -----------------------------------------------------------------
>
> Key: ARROW-7173
> URL: https://issues.apache.org/jira/browse/ARROW-7173
> Project: Apache Arrow
> Issue Type: Test
> Components: Integration
> Reporter: Bryan Cutler
> Assignee: Antoine Pitrou
> Priority: Major
> Fix For: 1.0.0
>
>
> A Map has child fields and the format spec only recommends that they be named
> "entries", "key", and "value" but could be named anything. Currently,
> integration tests for Map arrays verify the exchanged schema is equal, so the
> child fields are always named the same. There should be tests that use
> different names to verify implementations can accept this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
