Thanks much Andrey & Dmitry, the solution is working.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Dmitry,
Yes, you are right. we should broadcast a job with local scan queries.
On Mon, Oct 30, 2017 at 4:54 PM, Dmitry Pavlov
wrote:
> Hi Andrey, should we limit scan query to be executed only for current node
> here with setLocal() method?
>
>
> пн, 30 окт. 2017 г. в 16:48, Andrey Mashenkov >
Hi Andrey, should we limit scan query to be executed only for current node
here with setLocal() method?
пн, 30 окт. 2017 г. в 16:48, Andrey Mashenkov :
> As a workaround you can try to broadcast a task :
>
> Collection res =
> ignite.compute(ignite.cluster().forCacheNodes("mycache")).broadc
As a workaround you can try to broadcast a task :
Collection res =
ignite.compute(ignite.cluster().forCacheNodes("mycache")).broadcast(
new IgniteCallable() {
/** Auto-inject ignite instance. */
@IgniteInstanceResource
private Ignit
Hi,
This is known bug that transformer applies only to first page of results.
Here is a ticket [1]
[1] https://issues.apache.org/jira/browse/IGNITE-5804
On Sat, Oct 28, 2017 at 8:57 AM, naresh.goty wrote:
> Hi All,
>
> We are seeing an issue with calculating size of few caches in our
> applic
Hi All,
We are seeing an issue with calculating size of few caches in our
application, only when there
are more than one server node is started at the same time.
As part of startup routine, we have a custom load routine to load data to
cache, and once load is successfully complete, then cache s
