[
https://issues.apache.org/jira/browse/FLINK-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14227941#comment-14227941
]
ASF GitHub Bot commented on FLINK-1292:
---------------------------------------
GitHub user StephanEwen opened a pull request:
https://github.com/apache/incubator-flink/pull/241
[FLINK-1292] Allow for longer normalized keys when using composite keys
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/StephanEwen/incubator-flink normkey
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-flink/pull/241.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #241
----
commit ee8409634ead792913fb1c320f48c440e137e613
Author: Stephan Ewen <[email protected]>
Date: 2014-11-27T19:27:26Z
[FLINK-1292] Allow for longer normalized keys when using composite keys
----
> Allow for longer normalized keys
> --------------------------------
>
> Key: FLINK-1292
> URL: https://issues.apache.org/jira/browse/FLINK-1292
> Project: Flink
> Issue Type: Improvement
> Components: Local Runtime
> Affects Versions: 0.8-incubating
> Reporter: Stephan Ewen
> Fix For: 0.8-incubating
>
>
> The normalized key sorter currently has a hardwired limit of a normalized key
> size of 8 bytes. This still comes from the "single key" era.
> For composite keys, this length is easily exceeded and sorts cannot happen as
> fast as the could. On the other hand, setting the value arbitrarily large
> impacts memory consumption.
> I propose to extend this to allow for 8 bytes per key up to a total length of
> 16 bytes. This fits at least two composite longs, or a sequence of Ints.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
