Hi!
We try to isolate read transaction from write transaction. So, we write to
two transactional caches and commit transaction. From another thread we
read from both caches (READ_COMMITED). Ignite isolate data change for every
single cache, but not for both caches simultaneously.
In Oracle databas
Update:
I updated IgniteClientStarter.java to use Ignite instead of IgniteClient.
Now I can see that the 'new' node joins the cluster and starts cache with
mode=PARTITIONED. Also cache fetch is successful. This is still not optimal
as I would like to use the 'new' node in client mode to avoid loadi
HI Ivan, thanks for the quick reply.
Yes it perfectly works as needed with the fix.
Person.Address.Street will not work because
person.getPerson().getAddress().getStreet() does not exist. It has to be
person.getAddress().getStreet(). So column name should be "Address.street"
Any other name does
I don't know if this relates and we have not fully understood where the
problem is but after we upgraded to SpringBoot 2.2.0 the Kubernetes TCP
finder "seemed" to be failing on the "logger" which was odd because
everything else seemed to work, even logging in other pieces (it worked
previously).
Hi Sudhir,
Client nodes do not store data and do not perform CacheStore operations.
When you do a cache operation from client node, it is performed on the
server node, where ReadThrough happens if configured.
On Wed, Oct 23, 2019 at 2:47 PM Sudhir Patil
wrote:
> Hi All,
>
> Any opinion / views
Hi All,
Any opinion / views about below question???
On Wednesday, October 23, 2019, Sudhir Patil
wrote:
> Hi All,
>
> In ignite.Net, is it possible to do Read through operation from client
> node/mode instead of server node/mode??
>
>
> Regards,
> Sudhir
>
>
> --
> Thanks & Regards,
> Sudhir Pa
I have a system that uses JMS topics with a durable subscription to process
events between different applications, and the durable subscription ensures
that the subscriber does not loose messages in the event that the consumer
is down for some reason.
I like the data grid capabilities and would li
Hi Hemambara,
Yep, I left some trash in gist [1] initially ("as address"), cleaned up.
But does it really works as you need? In previous email I meant that
the behavior is not plausible even in one node case. And the problem
here is that added column "Address.street" is not mapped to
Person.addre
Yes.
The thing is that when I run the node (same configuration and same version)
just switching to server mode it works properly.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
It is not some kind of reset, you just adding new cache and this is allowed
for the client. Rules for new caches are the same for client and server
nodes. Ignite just checks what is already in cluster. So in your case it
should be the following behaviour:
1) first cache starts in group_data_loom gr
10 matches
Mail list logo