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

Posted to issues@ignite.apache.org by "Ignite TC Bot (JIRA)" <ji...@apache.org> on 2019/01/05 14:21:00 UTC

[jira] [Commented] (IGNITE-10290) Map.Entry interface for key cache may lead to incorrect hash code calculation

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

Ignite TC Bot commented on IGNITE-10290:
----------------------------------------

{panel:title=--&gt; Run :: All: No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--&gt; Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=2725248&amp;buildTypeId=IgniteTests24Java8_RunAll]

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