You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Neville Dipale (Jira)" <ji...@apache.org> on 2021/03/26 19:09:00 UTC
[jira] [Resolved] (ARROW-11365) [Rust] [Parquet] Implement parsers
for v2 of the text schema
[ https://issues.apache.org/jira/browse/ARROW-11365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Neville Dipale resolved ARROW-11365.
------------------------------------
Fix Version/s: 4.0.0
Resolution: Fixed
Issue resolved by pull request 9705
[https://github.com/apache/arrow/pull/9705]
> [Rust] [Parquet] Implement parsers for v2 of the text schema
> ------------------------------------------------------------
>
> Key: ARROW-11365
> URL: https://issues.apache.org/jira/browse/ARROW-11365
> Project: Apache Arrow
> Issue Type: Sub-task
> Components: Rust
> Affects Versions: 3.0.0
> Reporter: Neville Dipale
> Assignee: Neville Dipale
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> V2 of the writer produces schema like:
> required INT32 fieldname INTEGER(32, true);
> We should support parsing this format, as it maps to logical types.
> I'm unsure of what the implications are for fields that don't have a logical type representation, but have a converted type (e.g. INTERVAL). We can try write a V2 file with parquet-cpp and observe the behaviour.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)