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

ASF GitHub Bot commented on IGNITE-10290:
-----------------------------------------

GitHub user dgovorukhin opened a pull request:

    https://github.com/apache/ignite/pull/5405

    IGNITE-10290 Fix missed prepareForCache in localGet operation

    Signed-off-by: Dmitriy Govorukhin <dmitriy.govoruk...@gmail.com>

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-10290

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/5405.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 #5405
    
----
commit 71308b18d891e707c801959f5fe92460b3bde69b
Author: Dmitriy Govorukhin <dmitriy.govorukhin@...>
Date:   2018-11-15T23:15:18Z

    IGNITE-10290 Fix missed prepareForCache in localGet operation
    
    Signed-off-by: Dmitriy Govorukhin <dmitriy.govoruk...@gmail.com>

----


> Map.Entry interface for key cache may lead to incorrect calculation hash code
> -----------------------------------------------------------------------------
>
>                 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
>
>
> In case 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.
> 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)

Reply via email to