You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Tupitsyn (JIRA)" <ji...@apache.org> on 2017/04/24 09:06:04 UTC

[jira] [Commented] (IGNITE-2578) .NET: Native object comparison

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

Pavel Tupitsyn commented on IGNITE-2578:
----------------------------------------

* {{Object.GetHashCode}} is no longer used by Ignite. Hash codes and equality are handled by {{BinaryArrayEqualityComparer}} always (IGNITE-4919).
* Un-ignored {{AtomicReferenceTest}} tests, they work as expected.

> .NET: Native object comparison
> ------------------------------
>
>                 Key: IGNITE-2578
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2578
>             Project: Ignite
>          Issue Type: Improvement
>          Components: platforms
>    Affects Versions: 1.1.4
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>              Labels: .net
>             Fix For: 2.0
>
>
> Currently all comparisons (cache key comparisons, atomic operations, etc) are performed in binary form on Java side. This may not work as intended when user has overridden Equals/GetHashCode. Need to investigate whether we can or should do anything about this. 
> * Is it really an issue?
> * Is there a workaround?
> * Are there any user requests about this?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)