hi,
thanks for explanation!
YAMAMOTO Takashi
> Hi,
>
> It's intentional. Originally the code only used nodeid, but there was a
> problem with ownership change so we fixed it by adding the timestamp.
>
> The issue we found goes like this, if nodeA is originally in the preflistt,
> after a few
hi,
riak_client.erl has a reference to a non-existent module riak_kv_mapred_filter.
(without "s")
YAMAMOTO Takashi
___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
Nice proposal.
It would be great if you could add a 'matches' regular expression option like
you currently have on key filters. I can't speak for everyone here, but this
[in addition to the 'limit' option] would definitely be a killer feature for me
and would definitely make managing large data
Reid I really like your proposal. It gives some of the same expressiveness to
2i that one gets with CouchDB views. Ability to retrieve sorted descending
would be very cool as well.
--gordon
On May 17, 2012, at 15:13 , Reid Draper wrote:
> Riak Users,
>
> I've been working on some proposed
Been seeing some busy_dist_port errors lately in our riak logs and curious
if it's anything to worry about.
Here is a specific instance of the log msg
https://gist.github.com/881598dc29ca168dba34
More info on our setup
* 9 node cluster (dedicated)
* Ubuntu 10.04
* 32GB ram
* SSDs
* 256K block siz
Riak Users,
I've been working on some proposed changes for Riak's secondary indexing, and
wanted to get some feedback. The proposal is in a gist:
https://gist.github.com/2721295
Feel free to email your comments or add them in the gist.
Thanks,
Reid Draper
Software Engineer
Basho
