[jira] [Resolved] (ARROW-6187) [C++] fallback to storage type when writing ExtensionType to Parquet

["Antoine Pitrou (Jira)" <ji...@apache.org>]

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

Antoine Pitrou resolved ARROW-6187.
-----------------------------------
    Fix Version/s:     (was: 1.0.0)
                   0.15.0
       Resolution: Fixed

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

> [C++] fallback to storage type when writing ExtensionType to Parquet
> --------------------------------------------------------------------
>
>                 Key: ARROW-6187
>                 URL: https://issues.apache.org/jira/browse/ARROW-6187
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: C++
>            Reporter: Joris Van den Bossche
>            Assignee: Joris Van den Bossche
>            Priority: Major
>              Labels: parquet, pull-request-available
>             Fix For: 0.15.0
>
>          Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> Writing a table that contains an ExtensionType array to a parquet file is not yet implemented. It currently raises "ArrowNotImplementedError: Unhandled type for Arrow to Parquet schema conversion: extension<arrow.py_extension_type>" (for a PyExtensionType in this case).
> I think minimal support can consist of writing the storage type / array. 
> We also might want to save the extension name and metadata in the parquet FileMetadata. 
> Later on, this could be potentially be used to restore the extension type when reading. This is related to other issues that need to save the arrow schema (categorical: ARROW-5480, time zones: ARROW-5888). Only in this case, we probably want to store the serialised type in addition to the schema (which only has the extension type's name). 



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