[
https://issues.apache.org/jira/browse/FLINK-5111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15683737#comment-15683737
]
Stefan Richter commented on FLINK-5111:
---------------------------------------
I think this is not an issue, because the documentation is talking about the
default of hashCode, which is typically related to the objects memory
reference. However, all keys should provide meaningful overrides for equals and
hashCode, which are also stable.
> 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)
