Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ARROW-6484: [Java] Enable create indexType for DictionaryEncoding according to dictionary value count #5321

Closed
wants to merge 1 commit into from

Conversation

tianchen92
Copy link
Contributor

Related to ARROW-6484.

Currently, when create DictionaryEncoding, we need to specify indexType, and it use Int(32, true) as default if this value is null.
Actually, when dictionary valueCount is small, we should use Int(8,true)/Int(16,true) instead to reduce memory allocation.
This issue is about to provide API for creating indexType according to valueCount and apply it to avro adapter for enum type.

@emkornfield
Copy link
Contributor

+1, thank ou.

pprudhvi pushed a commit to pprudhvi/arrow that referenced this pull request Sep 16, 2019
…ording to dictionary value count

Related to [ARROW-6484](https://issues.apache.org/jira/browse/ARROW-6484).

Currently, when create DictionaryEncoding, we need to specify indexType, and it use Int(32, true) as default if this value is null.
Actually, when dictionary valueCount is small, we should use Int(8,true)/Int(16,true) instead to reduce memory allocation.
This issue is about to provide API for creating indexType according to valueCount and apply it to avro adapter for enum type.

Closes apache#5321 from tianchen92/ARROW-6484 and squashes the following commits:

fc1931b <tianchen>  Enable create indexType for DictionaryEncoding according to dictionary value count

Authored-by: tianchen <niki.lj@alibaba-inc.com>
Signed-off-by: Micah Kornfield <emkornfield@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants