You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hyukjin Kwon (JIRA)" <ji...@apache.org> on 2019/05/21 04:18:20 UTC

[jira] [Resolved] (SPARK-22736) Consider caching decoded dictionaries in VectorizedColumnReader

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

Hyukjin Kwon resolved SPARK-22736.
----------------------------------
    Resolution: Incomplete

> Consider caching decoded dictionaries in VectorizedColumnReader
> ---------------------------------------------------------------
>
>                 Key: SPARK-22736
>                 URL: https://issues.apache.org/jira/browse/SPARK-22736
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 2.2.1
>            Reporter: Henry Robinson
>            Priority: Major
>              Labels: bulk-closed
>
> {{VectorizedColumnReader.decodeDictionaryIds()}} calls {{dictionary.decodeToX}} for every dictionary ID encountered in a dict-encoded Parquet page.
> The whole idea of dictionary encoding is that a) values are repeated in a page and b) the dictionary only contains values that are in a page. So we should be able to save some decoding cost by decoding the entire dictionary page once, at the cost of using some memory (but theoretically we could discard the encoded dictionary, I think), and using the decoded dictionary to populate rows. 
> This is particularly true for TIMESTAMP data, which after SPARK-12297, might have a timezone conversion as part of its decoding step.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org