ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ilya Lantukh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-10290) Map.Entry interface for key cache may lead to incorrect hash code calculation
Date Mon, 24 Dec 2018 13:48:00 GMT

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

Ilya Lantukh commented on IGNITE-10290:
---------------------------------------

[~DmitriyGovorukhin], thanks for the contribution!

Please add test that reproduces this problem to the pull request.

> Map.Entry interface for key cache may lead to incorrect hash code calculation
> -----------------------------------------------------------------------------
>
>                 Key: IGNITE-10290
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10290
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Dmitriy Govorukhin
>            Assignee: Dmitriy Govorukhin
>            Priority: Major
>             Fix For: 2.8
>
>         Attachments: Reproducer.java
>
>
>  If use Map.Entry interface for a key, we can try to find (key, value) in store with
incorrect calculated hash code for binary representation, it lead to result null.
> The problem is in the 
> GridPartitionedSingleGetFuture#localGet() and GridPartitionedGetFuture#localGet() does
not execute prepareForCache before reading cacheDataRow from row store.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message