Hello!
I would believe that reduce may run multiple times as you have suggested.
Regards,
--
Ilya Kasnacheev
чт, 1 нояб. 2018 г. в 5:48, gsaxena888 :
> I've been thinking about this some more: I think the ignite solution is
> nearly perfect, *if* the reduce operation runs within every node
I've been thinking about this some more: I think the ignite solution is
nearly perfect, *if* the reduce operation runs within every node (so that,
for example, the results of ~96 threads on one google compute enginer were
reduced/summarized to a single value) and then either a single final
Ahh, I see. But still, even with "map reduce" stratedgy, I *think* that there
is only a SINGLE node which will do the reduction, right? As in, the
reduction will NOT occur in parallel across nodes, right? (In fact, it
sounds like the reduction won't even occur in parallel *within* a node,
right?)
Hello!
String::length will be run on all nodes, but Integer::intValue will be run
locally.
If you want it to be smarter than that, you could use MapReduce & ForkJoin:
https://apacheignite.readme.io/docs/compute-tasks
Regards,
--
Ilya Kasnacheev
вт, 30 окт. 2018 г. в 22:02, gsaxena888 :
>
I'm new to Apache Ignite, but a long-time user of jdk8 streams. (And I've
used Google Cloud Dataflow.) I'm trying to understand the example described
in latest doc:
https://apacheignite.readme.io/docs/distributed-closures#apply-methods
