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

2019-01-05 Thread Dmitriy Govorukhin (JIRA) 


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

Dmitriy Govorukhin commented on IGNITE-10290:
-

[~ilantukh] Thanks for the review, I added a test.

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

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

2019-01-05 Thread Ignite TC Bot (JIRA) 


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

Ignite TC Bot commented on IGNITE-10290:


{panel:title=-- Run :: All: No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2725248buildTypeId=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)

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

2018-12-24 Thread Ilya Lantukh (JIRA) 


[ 
https://issues.apache.org/jira/browse/IGNITE-10290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)

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

2018-11-26 Thread Roman Shtykh (JIRA) 


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

Roman Shtykh commented on IGNITE-10290:
---

Dmitriy, if you could review it or make any suggestions how to improve, that 
would be great.

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

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

2018-11-26 Thread Dmitriy Govorukhin (JIRA) 


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

Dmitriy Govorukhin commented on IGNITE-10290:
-

Roman Shtykh I will check it before merging this issue, thanks!

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

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

2018-11-26 Thread Roman Shtykh (JIRA) 


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

Roman Shtykh commented on IGNITE-10290:
---

Looks like `prepareForCache` is missed in several places. IGNITE-10017 is 
another issue with that.

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

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

2018-11-23 Thread Ignite TC Bot (JIRA) 


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

Ignite TC Bot commented on IGNITE-10290:


{panel:title=Possible 
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Binary Objects (Simple Mapper Basic){color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=2341728]]
* IgniteBinarySimpleNameMapperBasicTestSuite: 
MarshallerContextLockingSelfTest.testMultithreadedUpdate - 0,0% fails in last 
100 master runs.

{panel}
[TeamCity Run All 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2341837buildTypeId=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)