Re: Incorect Input to Reduce

To be more clear for others reading, and correct my example: > [0,15] to {"reduce_phase_only_1":true,0:10,1:15} [0,15] to {"reduce_phase_only_1":true,"0":0,"1":15} (quoting the integer keys is not necessary, doing so for clarity) * Jonathan Langevin Manager, I

Re: Incorect Input to Reduce

n/m, I just need to modify my args from [0,15] to {"reduce_phase_only_1":true,0:10,1:15}* Jonathan Langevin Manager, Information Technology Loom Inc. Wilmington, NC: (910) 241-0433 - jlange...@loomlearning.com - www.loomlearning.com - Skype: intel352 * On Wed, No

Re: Incorect Input to Reduce

Excellent tip Sean, works great for a similar issue I was having. If I already had args being passed to my reduce phase though (such as when calling Riak.reduceSlice), is it possible to specify only_1 and still ensure that my regular args pass through to the function as expected? For instance, redu

Re: Incorect Input to Reduce

The reduce phase receives data in batches. Per the docs, the default size is for every 20 inputs, reduce. The batch size can be tuned via config or per m/r request. Re: 13, likely what you're seeing is the length of the last phase sent to reduce. It seems if I return [values.length], I get just th

Re: Incorect Input to Reduce

Hi Yehuda, Your reduce function is not guaranteed to run across all inputs in the first application, but may be applied many times as new inputs come in. Riak will batch up reduce inputs until a certain number or timeout is reached, then apply the function and take its output to be part of the inp

Incorect Input to Reduce

Hi, I've posted a mail on this few days ago, but went a bit further since then. I'm using ripple, running a map function on some input and getting a list of about 50 items. Right after that, I'm running a reduce function. The first thing I do in it is putting the length of v (the input) as an