[
https://issues.apache.org/jira/browse/ARROW-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wes McKinney moved PARQUET-1324 to ARROW-3772:
----------------------------------------------
Fix Version/s: (was: cpp-1.6.0)
0.13.0
Component/s: (was: parquet-cpp)
C++
Workflow: jira (was: patch-available, re-open possible)
Key: ARROW-3772 (was: PARQUET-1324)
Project: Apache Arrow (was: Parquet)
> [C++] Read Parquet dictionary encoded ColumnChunks directly into an Arrow
> DictionaryArray
> -----------------------------------------------------------------------------------------
>
> Key: ARROW-3772
> URL: https://issues.apache.org/jira/browse/ARROW-3772
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++
> Reporter: Stav Nir
> Priority: Major
> Labels: parquet
> Fix For: 0.13.0
>
>
> Dictionary data is very common in parquet, in the current implementation
> parquet-cpp decodes dictionary encoded data always before creating a plain
> arrow array. This process is wasteful since we could use arrow's
> DictionaryArray directly and achieve several benefits:
> # Smaller memory footprint - both in the decoding process and in the
> resulting arrow table - especially when the dict values are large
> # Better decoding performance - mostly as a result of the first bullet -
> less memory fetches and less allocations.
> I think those benefits could achieve significant improvements in runtime.
> My direction for the implementation is to read the indices (through the
> DictionaryDecoder, after the RLE decoding) and values separately into 2
> arrays and create a DictionaryArray using them.
> There are some questions to discuss:
> # Should this be the default behavior for dictionary encoded data
> # Should it be controlled with a parameter in the API
> # What should be the policy in case some of the chunks are dictionary
> encoded and some are not.
> I started implementing this but would like to hear your opinions.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
