You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@apex.apache.org by "Ilya Ganelin (JIRA)" <ji...@apache.org> on 2016/06/01 18:01:02 UTC

[jira] [Comment Edited] (APEXMALHAR-175) KeyValPair isn't automatically sticky partitioned for key

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

Ilya Ganelin edited comment on APEXMALHAR-175 at 6/1/16 6:00 PM:
-----------------------------------------------------------------

This issue is resolved by using the existing KeyHashValPair class instead.


was (Author: ilganeli):
This issue is resolved by using the KeyHashValPair class instead.

> 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)