This info should be in the docs. I just added an issue to track it [1].
Thanks for digging. :)

Mark
twitter.com/pharkmillups

[1] https://github.com/basho/riak_wiki/issues/316

On Sun, Jul 15, 2012 at 9:18 PM, Mark Boyd ソフトウェア 建築家
<boy...@ldschurch.org>wrote:

>  Never mind. I found the archive search page and this same question
> posted earlier here:****
>
> ** **
>
>
> http://riak-users.197444.n3.nabble.com/Map-Reduce-behavior-when-key-not-found-td3641739.html
> ****
>
> ** **
>
> Mark****
>
> ** **
>
> *From:* riak-users-boun...@lists.basho.com [mailto:
> riak-users-boun...@lists.basho.com] *On Behalf Of *Mark Boyd ?????? ???
> *Sent:* Sunday, July 15, 2012 7:55 AM
> *To:* riak-users@lists.basho.com
> *Subject:* mapreduce with non-existent keys****
>
> ** **
>
> I’ve got a set of bucket/key pairs that may contain items that no longer
> exist in riak. Is it possible to pass that to map/reduce and explicitly
> tell riak to ignore any pairs which aren’t current, ie: which aren’t found?
> For example, if I have compiled a list of pairs but before passing the
> list, one or more of those items was removed from the database, then my
> map/reduce appears to fail since it doesn’t find the referenced item. Can
> riak be told to ignore such missing items if they are incurred? ****
>
> ** **
>
> Thanks.****
>
> ** **
>
> Mark****
>
>
>
> NOTICE: This email message is for the sole use of the intended
> recipient(s) and may contain confidential and privileged information. Any
> unauthorized review, use, disclosure or distribution is prohibited. If you
> are not the intended recipient, please contact the sender by reply email
> and destroy all copies of the original message.****
>
> ** **
>
> _______________________________________________
> riak-users mailing list
> riak-users@lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>
>
_______________________________________________
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Reply via email to