[jira] [Resolved] (ARROW-10261) [Rust] [BREAKING] Lists should take Field instead of DataType

["Neville Dipale (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARROW-10261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Neville Dipale resolved ARROW-10261.
------------------------------------
    Fix Version/s: 3.0.0
       Resolution: Fixed

Issue resolved by pull request 8608
[https://github.com/apache/arrow/pull/8608]

> [Rust] [BREAKING] Lists should take Field instead of DataType
> -------------------------------------------------------------
>
>                 Key: ARROW-10261
>                 URL: https://issues.apache.org/jira/browse/ARROW-10261
>             Project: Apache Arrow
>          Issue Type: Sub-task
>          Components: Integration, Rust
>    Affects Versions: 1.0.1
>            Reporter: Neville Dipale
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.0.0
>
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> There is currently no way of tracking nested field metadata on lists. For example, if a list's children are nullable, there's no way of telling just by looking at the Field.
> This causes problems with integration testing, and also affects Parquet roundtrips.
> I propose the breaking change of [Large|FixedSize]List taking a Field instead of Box<DataType>, as this will overcome this issue, and ensure that the Rust implementation passes integration tests.
> CC [~andygrove] [~jorgecarleitao] [~alamb]  [~jhorstmann] ([~carols10cents] as this addresses some of the roundtrip failures).
> I'm leaning towards this landing in 3.0.0, as I'd love for us to have completed or made significant traction on the Arrow Parquet writer (and reader), and integration testing, by then.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)