This example is based on http://jira.codehaus.org/browse/GPARS-104, just some more improvements to make more 'classic' mapreduce:
map/reduce in this case should be probably renamed/changed signature not to make confusion with old one
May I ask for a bit more details on the rationale behind the request to be able to assess it properly.
Actually and unfortunately I don't know too much about MR so I can't say exactly. Probably the best solution for this is
1) to study some MR implementations like Hadoop or GridGain
2) ask some people that do know about MR - post link to this discussion to the gpars mail list (-dev and probably -user)
OK, makes sence.
A demo showing possible uses of the current 'combine' implementation is at http://github.com/vaclav/GPars/blob/master/src/test/groovy/groovyx/gpars/samples/DemoParallelWordCount.groovy
Since the implementation currently reflects my (perhaps limited) view of the map/reduce world, if no-one objects I'd close the issue.
ok, I'll open another issue when I study MR implementations and have some specific (and reasonable) ideas (if combine will be not enough)
Sounds good to me. I'll always welcome your feedback.