Re: Map Reduce behavior when key not found

On 8 Jan 2012, at 11:03, Yehuda Zargrov wrote: > Hi, > > I’m adding a range of keys to a MapReduce object, knowing that some of them > do not exist. > When running map & reduce functions, I’ve noticed a strange behavior like > adding ‘not_found’ records to the input of the reduce. Is there a

Map Reduce behavior when key not found

Hi, I'm adding a range of keys to a MapReduce object, knowing that some of them do not exist. When running map & reduce functions, I've noticed a strange behavior like adding 'not_found' records to the input of the reduce. Is there a way to simply ignore un-existing keys? Thanks, [cid:image00