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
I have tried replacing the PutAll() with two Put()s, like this:
cache.Put(key1, new byte[100]);
cache.Put(key2, new byte[100]);
The first Put throws this exception:
*Name*
*Value*
*Type*
▶
$exception
{Apache.Ignite.Core.Cache.CacheException: class
org.apache.i
