Mailing-List: contact issues-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
Date: Tue, 25 Aug 2015 14:30:45 +0000 (UTC)
From: "Stephan Ewen (JIRA)" <jira@apache.org>
To: issues@flink.apache.org
Message-ID: <JIRA.12785192.1427210439000.159617.1440513045663@Atlassian.JIRA>
In-Reply-To: <JIRA.12785192.1427210439000@Atlassian.JIRA>
References: <JIRA.12785192.1427210439000@Atlassian.JIRA>
 <JIRA.12785192.1427210439149@arcas>
Subject: [jira] [Commented] (FLINK-1778) Improve normalized keys in
 composite key case
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/FLINK-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14711362#comment-14711362 ] 

Stephan Ewen commented on FLINK-1778:
-------------------------------------

Has not been addressed

> Improve normalized keys in composite key case
> ---------------------------------------------
>
>                 Key: FLINK-1778
>                 URL: https://issues.apache.org/jira/browse/FLINK-1778
>             Project: Flink
>          Issue Type: Improvement
>          Components: Local Runtime
>    Affects Versions: 0.9
>            Reporter: Stephan Ewen
>            Assignee: Stephan Ewen
>             Fix For: 0.9
>
>
> Currently, if we have a key (String, long), the String will take up the entire normalized key space, without being fully discerning anyways. Limiting the key prefix in size and giving space to the second key field should in most cases improve the comparison efficiency.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)