Hello! I think this is because Ignite marshallers stick to what Java supports. Java only supports signed numbers and it only supports nullable composite values (no structs).
Thus on the C# side you can use those types which intersect between Java and .Net runtimes. I can see how this can be inconvenient, unfortunately we don't have that strong C# lobby to make the difference currently. Regards, -- Ilya Kasnacheev вт, 9 окт. 2018 г. в 0:04, Raymond Wilson <raymond_wil...@trimble.com>: > I’m using Ignite IBinarizable raw serialization in Ignite v2.6 with C# > client. > > > > I notice there is no support for unsigned short, int and long integer types > (both single values and arrays). > > > > I also noticed that Decimal, DateTime and Guid read/write methods only > support nullable values. > > > > Currently I have code that writes a ushort value into an into to preserve > its value range. Similarly I have non-nullable Guid values and need to do > the nullable dance to on the read side to transform them back to > non-nullable. > > > > Is there a particular reason these are not supported? > > > > Thanks, > > Raymond. >
