That's right. You can watch it for update notifications.
Best Regards,
Igor
On Fri, Nov 17, 2017 at 2:37 PM, kotamrajuyashasvi <
kotamrajuyasha...@gmail.com> wrote:
> Hi
>
> Yes.. around 100-150 C++ processes or may be threads will be running on a
> machine, but each process/thread requires to
Hi
Yes.. around 100-150 C++ processes or may be threads will be running on a
machine, but each process/thread requires to use a separate transaction. I
found out that along with sql transactions feature ticket, a separate ticket
is present to implement transactions support for ODBC. Hope it will
Hi
Thanks for your response. Actually I'm working on a C++ project where
multiple C++ processes run in parallel. Each process should connect to
Ignite Server initially and start a transaction. Cassandra is used as
persistent store(The main reason to use ignite on top of Cassandra is for
the
Hi,
Ignite C++ indeed starts JVM process, but it is not just client,
it is basically ordinary Ignite node, that can be client or server
and can do in cluster almost anything, that Java Ignite node can,
although, C++ still does not have all the features that Java API
has. So, basically, C++ allows
Hi
I have a C++ Application that needs to perform query operations(DML and
Select) and transactions on Ignite Server. Whats the best way to achieve
this ? There are two choices: 1. Ignite ODBC driver and 2. Ignite C++
Driver.
I would like to what would be right choice to use from the point of
