Jack,
You can use pointer semantics [1] to differ nulls from zeroes. It won't
work for primitive types (as int), but it is a rare case, really, that your
value is a primitive type. And even if you want to use value, that only
contains single int it is simple enough to make a class-wrapper.
Hi Igor,
I took a look at the master branch. I have couple questions.
1. For void getAndPutIfAbsent, the method has this comment:
@param valOut Previously contained value regardless of whether put happened
or not (null if there
* was no previous value).
How do we
Hi Jack,
Design document is mostly for developers, not for users. It shows current
state of the master branch, so not every feature listed there as supported
actually presents in any Ignite release. You can try naightly builds [1]
though,
if you want try some new features before they get into
Hi Jack,
Should be included into next version [1]. Stay tuned.
[1] https://issues.apache.org/jira/browse/IGNITE-9904
пт, 15 мар. 2019 г. в 01:32, jackluo923 :
>
> After digging deeper, it appears that thin-client atomic cache operations are
> not implemented. I have implemented and tested the
After digging deeper, it appears that thin-client atomic cache operations are
not implemented. I have implemented and tested the atomic cache operations
in C++ thin-client locally and they appear to work correctly but I haven't
done any extensive testing. Is there any reason why atomic operations
Is atomic operation supported on C++ thin client?
Design documentation shows yes
(https://cwiki.apache.org/confluence/display/IGNITE/Thin+clients+features)
SDK documentation suggest now
(https://www.gridgain.com/sdk/pe/latest/cppdoc/classignite_1_1thin_1_1cache_1_1CacheClient.html)
Compilation
