Yes, thick client always sends requests to the "right" node that actually
contains data.
Best Regards,
Igor
On Mon, Jan 21, 2019 at 9:20 AM summasumma wrote:
> Thanks Igor.
>
> One more clarification:
>
> Does Ignite client perform sharding by itself by selecting the
> node/partition across se
Thanks Igor.
One more clarification:
Does Ignite client perform sharding by itself by selecting the
node/partition across server cluster nodes for performing operations like
Insert/update etc using some hash operation on the key locally? Or it
connects to one of the nodes in the cluster and that
No you should not have the same configs, but you need to have the same
configuration of the protocol, which is different for Java and C++ by
default
(I believe, you use Java server).
You may find details here [1].
[1] -
https://apacheignite-cpp.readme.io/docs/cross-platform-interoperability
Best
Thanks Igor.
Yes it is trying to start in client mode now with correct file. My bad
filename misspelled by a character.
Now im getting following error:
[09:55:28] REST protocols do not start on client node. To start the
protocols on client node set '-DIGNITE_REST_START_ON_CLIENT=true' system
prop
It should start in client mode. Make sure that the right configuration file
is used.
Best Regards,
Igor
On Thu, Jan 17, 2019 at 12:40 PM summasumma wrote:
> Thanks Igor.
>
> I am trying to do an example putandget operation using the Ignite-c++
> client
> code from the following link:
> https:/
Thanks Igor.
I am trying to do an example putandget operation using the Ignite-c++ client
code from the following link:
https://github.com/apache/ignite/tree/master/modules/platforms/cpp/examples
==
Source code:
https://github.com/apache/ignite/blob/master/modules/platforms/cpp/e
Hi,
1. Async is not yet supported in C++ clients.
2. Continuous queries supported by thick C++ client.
3. Works through SQL, so supported by thick client.
4. SQL supported by thick client, and also planned for C++ thin client.
Best Regards,
Igor
On Mon, Jan 14, 2019 at 10:53 AM summasumma w
hi all,
Can you please clarify if Ignite C++ CLIENT(both thin and thick/normal)
supports following:
1. Async read/insert/update/delete operations (from our application we will
send a read request asynchronously, and once the Ignite server responds back
we should get notification on the response)?
Do continuous queries work for you?
https://apacheignite-cpp.readme.io/docs/continuous-queries
Denis
On Wed, Jan 9, 2019 at 4:08 PM SamsonLai wrote:
> Thanks a lot
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
Thanks a lot
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
That's right, Ignite C++ do not support messaging currently.
Best Regards,
Igor
On Tue, Jan 8, 2019 at 3:07 AM SamsonLai wrote:
> I have an ignite cluster that running on Java, all nodes (Java) within the
> cluster can send and receive Ignite messages. Now, I have to create another
> client no
I have an ignite cluster that running on Java, all nodes (Java) within the
cluster can send and receive Ignite messages. Now, I have to create another
client node by C++, I am using Ignite 2.7, but seems that Ignite C++ does
not supports Ignite messages, right?
--
Sent from: http://apache-ignit
12 matches
Mail list logo