Hi Alexey,
Yes, you are absolutely correct.
Thanks!
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Yes, its getting stored as string, not as individual fields or properties of
an object.
Thanks
naveen
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Slava, I think what you suggested would add the "{"
partyId":"P10002",...}" value as a String. My guess was Naveen had a
value of a custom type. My understanding is Ignite currently does not try
to cast provided value to a custom type before invoking cache.put.
Hi Naveen,
Yes, PUT command can be used in order to update a record.
In accordance with the spec https://apacheignite.readme.io/docs/rest-api#put
it requires 3 mandatory parameters:
- key - key
- val - new value. you need to provide all properties.
unfortunately, there is no capa
Thin Client protocol (coming in 2.4) is a faster and more feature-rich
binary alternative to REST.
It supports arbitrary objects as well.
See
https://cwiki.apache.org/confluence/display/IGNITE/IEP-9+Thin+Client+Protocol
.
For now you can try nightly builds or build Ignite from sources.
Thanks,
Pa
I quickly looked at ignite REST implementation and it seems you can only
use it to add string keys and values only. You might contact Ignite
developers on the DEV list and ask to extend REST API to support keys and
values of arbitrary types.
