wil...@trimble.com]
*Sent:* Friday, May 11, 2018 2:37 PM
*To:* 'dev@ignite.apache.org'
*Subject:* RE: Possible bug in PutAll() in Ignite 2.4, .Net client
I have previously used the same logic using a long instead of a Guid
without this issue.
*From:* Raymond Wilson [mailto:raymond_wil...@trimbl
I have previously used the same logic using a long instead of a Guid
without this issue.
*From:* Raymond Wilson [mailto:raymond_wil...@trimble.com]
*Sent:* Friday, May 11, 2018 2:36 PM
*To:* 'dev@ignite.apache.org'
*Subject:* RE: Possible bug in PutAll() in Ignite 2.4, .Net client
ne
104}
Apache.Ignite.Core.Cache.CacheException
*From:* Raymond Wilson [mailto:raymond_wil...@trimble.com]
*Sent:* Friday, May 11, 2018 2:31 PM
*To:* 'dev@ignite.apache.org'
*Subject:* Possible bug in PutAll() in Ignite 2.4, .Net client
I have run into an issue using an AffinityFunction with a Guid
I have run into an issue using an AffinityFunction with a Guid in the key.
The complete reproducer is included below as an XUnit unit test.
I do know about the [AffinityKeyMapped] attribute, but I want to have
different behaviour for these keys depending on context (sometimes I want
them partiti
