Re: UPDATED: BinaryIdentityResolver is gone in 2.0 but default seems to have a problem

Let's move the discussion to a single thread: http://apache-ignite-users.70518.x6.nabble.com/Get-by-key-only-working-on-net-for-certain-long-literal-values-td13456.html On Wed, Jun 7, 2017 at 6:23 AM, Gordon Reid (Nine Mile) < gordon.r...@ninemilefinancial.com> wrote: > Hi There, > > > > I am abl

Re: BinaryIdentityResolver is gone in 2.0 but default seems to have a problem

Let's move the discussion to a single thread: http://apache-ignite-users.70518.x6.nabble.com/Get-by-key-only-working-on-net-for-certain-long-literal-values-td13456.html On Wed, Jun 7, 2017 at 6:21 AM, Gordon Reid (Nine Mile) < gordon.r...@ninemilefinancial.com> wrote: > Hi There, > > > > I am abl

UPDATED: BinaryIdentityResolver is gone in 2.0 but default seems to have a problem

Hi There, I am able to load the same row into my cache from my persistent store twice, and have it present in my cache twice. It seems the id hash is different for the key. The key class is very simple, just one int id. And here is what I see debugging. How can the id hash be different here.??

BinaryIdentityResolver is gone in 2.0 but default seems to have a problem

Hi There, I am able to load the same row into my cache from my persistent store twice, and have it present in my cache twice. It seems the id hash is different for the key. The key class is very simple, just one int id. And here is what I see debugging. How can the id hash be different here.??