Hi Antoine, Oh, sorry. I also missed the comment...
I'll revert the recent C++ change: https://github.com/apache/arrow/pull/49416 BTW, should the Rust implementation and nanoarrow also always use "key"/"value"/"entries" for map type field names? Thanks, -- kou In <[email protected]> "Re: Map type's key/item/value field names" on Wed, 4 Mar 2026 09:13:35 +0100, Antoine Pitrou <[email protected]> wrote: > > Hi Kou, > > Le 04/03/2026 à 06:14, Sutou Kouhei a écrit : >> I think that key/item/value field names of map type in >> Apache Arrow data should not be ignored. Is it correct? > > I don't know. The behavior in Arrow C++ was deliberate, see previous > work here: > https://github.com/apache/arrow/pull/35298#issuecomment-1520357836 > > In particular Will Jones said this: > > """Preserve field names of Map subfields. I'm -0.7 on this. The spec > dictates they should be certain names, and I don't see good reason to > let them deviate from this much. Right now we don't preserve them in > the C Data Interface.""" > > Regards > > Antoine. >
