Hi, Vishwas
It is known issue with REST.
I fixed it recently in https://issues.apache.org/jira/browse/IGNITE-7725
It will be available in ignite-2.5 because it was late to push it in
ignite-2.4 due to code freeze.
You can wait for ignite-2.5 or build from sources from master branch.
On Sun,
Hi,
I am using ignite 2.3. I have added the ignite-rest-http folder under libs
folder.
Ignite version command is working as expected:
curl http://10.194.11.99:8080/ignite?cmd=version
{"successStatus":0,"sessionToken":null,"error":null,"response":"2.3.0"}
But when I try to create cache it return
Is there any method I can use to auto generate (auto increment, for example)
"primary key" (id) of "table" in distributed environment via INSERT
SQL-query?
If no, what is preferred technique for clustered multithreading system
(UUID, timestamp)?
--
Sent from: http://apache-ignite-users.70518.x6
hi mike,
you can create another cache with key equals (idnumber + value), redirect
your streamer to it, and then feel free to check cache size. it could waste
your RAM, but fast enough for any parallel queries, because it's not
map/reduce at all. we used this weird k/v trick in many 'ignite report