Shawn,
map() method is execute locally on the master node, so you can do all the
checks outside the task and then execute only if needed. Will this work?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/compute-SQL-returned-data-tp9890p10016.html
Sent from
2017年1月11日 3:31
收件人: user@ignite.apache.org
主题: Re: 答复: compute SQL returned data.
Hi Shawn,
This means what it says - ComputeTask.map() method returned no jobs, i.e.
null or empty map.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/compute-SQL-returne
Hi Shawn,
This means what it says - ComputeTask.map() method returned no jobs, i.e.
null or empty map.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/compute-SQL-returned-data-tp9890p.html
Sent from the Apache Ignite Users mailing list archive at Nabb
@ignite.apache.org
主题: 答复: compute SQL returned data.
Thanks, I already figure it out just As you mentioned.
-邮件原件-
发件人: dkarachentsev [mailto:dkarachent...@gridgain.com]
发送时间: 2017年1月9日 17:24
收件人: user@ignite.apache.org
主题: Re: compute SQL returned data.
Hi Shawn,
For map-reduce operations is
Thanks, I already figure it out just As you mentioned.
-邮件原件-
发件人: dkarachentsev [mailto:dkarachent...@gridgain.com]
发送时间: 2017年1月9日 17:24
收件人: user@ignite.apache.org
主题: Re: compute SQL returned data.
Hi Shawn,
For map-reduce operations is most suitable ComputeTask [1], which has
map/
We can submite Compute Task which will be mapped jobs on nodes. Jobs can
execute local SQL query (see Query#setLocal). Examples queries and compute
task can be found here: https://github.com/apache/ignite/tree/master/
examples/src/main/java/org/apache/ignite/examples
On Thu, Jan 5, 2017 at 11:09 A
Thanks!
My case looks like this:
We store big cache object to overcome the defects of ignite overhead of each
cache entry.
For these big cache object, we can’t use SQL to query/aggregate them. So we
need compute by ourselves.
We want to compute on the SQL returned data in ignite se
