[
https://issues.apache.org/jira/browse/ARROW-14999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17578368#comment-17578368
]
Joris Van den Bossche commented on ARROW-14999:
-----------------------------------------------
bq. am unable to determine any real use case for a custom field name
We are starting to use custom field names in the extension types for geospatial
data
(https://github.com/geopandas/geo-arrow-spec/blob/main/extension-types.md#concrete-examples-of-extension-type-metadata,
https://github.com/paleolimbot/geoarrow/).
I don't know if we currently already rely on those names, but we had the
intention to do so in the future (cc [~paleolimbot])
> [C++] List types with different field names are not equal
> ---------------------------------------------------------
>
> Key: ARROW-14999
> URL: https://issues.apache.org/jira/browse/ARROW-14999
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++
> Affects Versions: 6.0.0
> Reporter: Will Jones
> Assignee: Will Jones
> Priority: Major
> Labels: pull-request-available
> Fix For: 10.0.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When comparing map types, the names of the fields are ignored. This was
> introduced in ARROW-7173.
> However for list types, they are not ignored. For example,
> {code:python}
> In [6]: l1 = pa.list_(pa.field("val", pa.int64()))
> In [7]: l2 = pa.list_(pa.int64())
> In [8]: l1
> Out[8]: ListType(list<val: int64>)
> In [9]: l2
> Out[9]: ListType(list<item: int64>)
> In [10]: l1 == l2
> Out[10]: False
> {code}
> Should we make list type comparison ignore field names too?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
