i found solution from
https://stackoverflow.com/questions/68768699/h2-database-dbexception-unsupported-connection-setting-multi-threaded
implementation ('com.h2database:h2') {
version {
strictly '1.4.197'
}
}
wkhapy...@gmail.com
From: wkhapy...@gmail.com
Date
2。I see Ignite doc has mapreduce
job，but it seem not example iterator cache key。 is there any method to iterator
key in mapreduce job。Thank you very much
wkhapy...@gmail.com
Thank you very, very much
wkhapy...@gmail.com
From: Stephen Darlington
Date: 2022-08-25 20:58
To: user
Subject: Re: count cache key number
var p = ignite.affinity(“CACHENAME”).partitions();
On 25 Aug 2022, at 13:10, wkhapy...@gmail.com wrote:
affinityCallAsync need PartitionId，how can i get
affinityCallAsync need PartitionId，how can i get all PartitionIds?
Or the number of partitions is 1024
wkhapy...@gmail.com
From: wkhapy...@gmail.com
Date: 2022-08-25 19:11
To: user
Subject: Re: Re: count cache key number
affinityCallAsync need PartitionId，how can i get all PartitionIds
affinityCallAsync need PartitionId，how can i get all PartitionIds
wkhapy...@gmail.com
From: Stephen Darlington
Date: 2022-08-25 18:55
To: user
Subject: Re: count cache key number
You’d need to use a thick client to call that API.
On 25 Aug 2022, at 10:39, wkhapy...@gmail.com wrote:
sorry
sorry,i find igniteClient.compute() has no affinityCallAsync method ,does
igniteClient can call affinityCallAsync
wkhapy...@gmail.com
From: Stephen Darlington
Date: 2022-08-24 20:27
To: user
Subject: Re: count cache key number
There are a number of ways to tackle this.
If your cache split
2。I see Ignite doc has mapreduce
job，but it seem not example iterator cache key。 is there any method to iterator
key in mapreduce job。Thank you very much
wkhapy...@gmail.com
Hi,
ok,I'll try it later.
wkhapy...@gmail.com
From: Maksim Timonin
Date: 2022-06-23 13:53
To: user
Subject: Re: ignite client can not reconnect to ignite Kubernetes cluster,after
pod restart
Hi,
Please, try to use `ClientConfiguration#setRetryLimit` additionally to
`ClientRetryAllPolicy
reason i found ，ignite server node restart ip changed，but ignite client still
use old ip address，is there any way refresh address
wkhapy...@gmail.com
From: f cad
Date: 2022-06-22 09:53
To: user
Subject: ignite client can not reconnect to ignite Kubernetes cluster,after pod
restart
below
