Return-Path: X-Original-To: apmail-flink-issues-archive@minotaur.apache.org Delivered-To: apmail-flink-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CD42918695 for ; Tue, 25 Aug 2015 14:57:58 +0000 (UTC) Received: (qmail 68309 invoked by uid 500); 25 Aug 2015 14:57:46 -0000 Delivered-To: apmail-flink-issues-archive@flink.apache.org Received: (qmail 68138 invoked by uid 500); 25 Aug 2015 14:57:46 -0000 Mailing-List: contact issues-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flink.apache.org Delivered-To: mailing list issues@flink.apache.org Received: (qmail 67952 invoked by uid 99); 25 Aug 2015 14:57:46 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Aug 2015 14:57:46 +0000 Date: Tue, 25 Aug 2015 14:57:46 +0000 (UTC) From: "Ufuk Celebi (JIRA)" To: issues@flink.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (FLINK-1778) Improve normalized keys in composite key case MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/FLINK-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ufuk Celebi updated FLINK-1778: ------------------------------- Fix Version/s: (was: 0.9) 0.10 > 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.10 > > > 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)