[
https://issues.apache.org/jira/browse/ARROW-8028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17057088#comment-17057088
]
Wes McKinney commented on ARROW-8028:
-------------------------------------
The project has so far taken the position that downstream applications are
responsible for the enforcement of these kinds of metadata constraints. From
the perspective of the Arrow protocol "data is data". In my experience
duplicate field names do arise in practice and it's a slippery slope if Arrow
implementations start making arbitrary (or otherwise opinionated) decisions
about what to do with such data (whether disallowing them or otherwise
disambiguating them by modifying the field names). APIs that presume field name
uniqueness can raise an exception, though
> [Go] Allow duplicate field names in schemas and nested types
> ------------------------------------------------------------
>
> Key: ARROW-8028
> URL: https://issues.apache.org/jira/browse/ARROW-8028
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Go
> Affects Versions: 0.16.0
> Reporter: Ben Kietzman
> Priority: Major
> Fix For: 0.17.0
>
>
> Go's implementation of Schema panics if field names are duplicated within a
> schema. This is not guaranteed by the standard, so Go will not be able to
> handle valid record batches produced by other implementations which contain
> these.
> https://github.com/apache/arrow/blob/084549a/go/arrow/schema.go#L117
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
