[
https://issues.apache.org/jira/browse/APEXMALHAR-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15308909#comment-15308909
]
ASF GitHub Bot commented on APEXMALHAR-175:
-------------------------------------------
GitHub user ilganeli opened a pull request:
https://github.com/apache/incubator-apex-malhar/pull/303
[APEXMALHAR-175] KeyValPair isn't automatically sticky partitioned for key
* Updated KeyValPair to override hashCode to support sticky partitioning by
key.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ilganeli/incubator-apex-malhar APEXMALHAR-175
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-apex-malhar/pull/303.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 #303
----
commit 19b5fd1085c1999bab833929cc6ad21e6fae40a3
Author: Ilya Ganelin <[email protected]>
Date: 2016-05-31T23:56:29Z
Updated KeyValPair to override hashcode to support sticky partitining by
key.
----
> KeyValPair isn't automatically sticky partitioned for key
> ---------------------------------------------------------
>
> Key: APEXMALHAR-175
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-175
> Project: Apache Apex Malhar
> Issue Type: Task
> Reporter: Pramod Immaneni
>
> KeyValPair is being used in some operators with the assumption that it will
> be sticky partitioned for key but it doesn't override hashcode function
> returning the key hashcode. KeyValPair extends AbstractMap.SimpleEntry which
> overrides hashcode and it is a function of both key and value.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
