ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dmreshet <dmres...@gmail.com>
Subject Re: Map-reduce proceesing
Date Wed, 20 Apr 2016 09:31:38 GMT
Yes, I know.
I want to compare performance of SQL,  SQL with indexes and MapReduce job.
I have found that I can use broadcast to garantie that my MapReduce job will
be executed on each node exactly once.
So now my job uses code:
/Collection<List&lt;Person> result =
ignite.compute(ignite.cluster()).broadcast((IgniteCallable<List&lt;Person>>)
() -> {...});/

And than I will reduce the result.

Is that the best practise to implement MapReduce job in case that I should
process data from cache?



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Map-reduce-proceesing-tp4357p4364.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Mime
View raw message