The haskell client has now been patched to fix this problem, which boiled down to it not consuming all the phases produced in a job.
The new interface to mapReduce is here: https://github.com/mailrank/riak-haskell-client/blob/master/src/Network/Riak/Basic.hs#L142 Cheers to Brian for his swift application and cleanup of my patch! -Nick On Wed, May 18, 2011 at 3:16 PM, Nick Partridge <nkp...@gmail.com> wrote: > Hey all, > > I'm playing with Riak via the haskell client, and I've run into a problem > with mapreduce. The gist of the problem is that once I've done one mapreduce > job with a connection, I only ever see results from that job. > > I've distilled it down to small example here ( > https://gist.github.com/977611), which exhibits slightly different > behaviour to my application code. In the small example, I'm seeing results > from the second query twice. I think there might be something going on with > laziness, but it's beyond my ability to debug. > > Any pointers? This is somewhat specific to the haskell client, I hope this > is the right place to ask :) > > Cheers, > Nick > >
_______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
