Mailing-List: contact dev-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
Date: Mon, 21 Nov 2016 14:23:58 +0000 (UTC)
From: "Kostas Kloudas (JIRA)" <jira@apache.org>
To: dev@flink.apache.org
Message-ID: <JIRA.13022202.1479738192000.328269.1479738238403@Atlassian.JIRA>
In-Reply-To: <JIRA.13022202.1479738192000@Atlassian.JIRA>
References: <JIRA.13022202.1479738192000@Atlassian.JIRA> <JIRA.13022202.1479738192423@arcas>
Subject: [jira] [Created] (FLINK-5111) Change the assignToKeyGroup() method
 to not use Object.hashCode()
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 21 Nov 2016 14:24:05 -0000

Kostas Kloudas created FLINK-5111:
-------------------------------------

             Summary: Change the assignToKeyGroup() method to not use Object.hashCode()
                 Key: FLINK-5111
                 URL: https://issues.apache.org/jira/browse/FLINK-5111
             Project: Flink
          Issue Type: Bug
    Affects Versions: 1.2.0
            Reporter: Kostas Kloudas
            Priority: Blocker
             Fix For: 1.2.0


Currently we use the Object.hashCode method as an intermediate step to assign an item to a key group. According to the java documentation:

"This integer (returned by the method) need not remain consistent from one execution of an application to another execution of the same application."

This means that a key may be assigned to another keygroup after restoring. This can easily break the semantics of a pipeline.


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