You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/08/02 09:56:00 UTC
[jira] [Updated] (ARROW-5917) [Java] Redesign the dictionary
encoder
[ https://issues.apache.org/jira/browse/ARROW-5917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated ARROW-5917:
----------------------------------
Labels: pull-request-available (was: )
> [Java] Redesign the dictionary encoder
> --------------------------------------
>
> Key: ARROW-5917
> URL: https://issues.apache.org/jira/browse/ARROW-5917
> Project: Apache Arrow
> Issue Type: New Feature
> Components: Java
> Reporter: Liya Fan
> Assignee: Liya Fan
> Priority: Major
> Labels: pull-request-available
>
> The current dictionary encoder implementation (org.apache.arrow.vector.dictionary.DictionaryEncoder) has heavy performance overhead, which prevents it from being useful in practice:
> # There are repeated conversions between Java objects and bytes (e.g. vector.getObject(i)).
> # Unnecessary memory copy (the vector data must be copied to the hash table).
> # The hash table cannot be reused for encoding multiple vectors (other data structure & results cannot be reused either).
> # The output vector should not be created/managed by the encoder (just like in the out-of-place sorter)
> # The hash table requires that the hashCode & equals methods be implemented appropriately, but this is not guaranteed.
> We plan to implement a new one in the algorithm module, and gradually deprecate the current one.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)