apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ilya Ganelin (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Deleted] (APEXMALHAR-175) KeyValPair isn't automatically sticky partitioned for key
Date Wed, 01 Jun 2016 18:07:59 GMT

     [ https://issues.apache.org/jira/browse/APEXMALHAR-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Ilya Ganelin updated APEXMALHAR-175:
    Comment: was deleted

(was: This issue is resolved by using the existing 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
>            Assignee: Ilya Ganelin
> 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

View raw message