Hi Scott,
Until Riak gains the ability to constrain list traversals by bucket this will
continue to be a point of friction. This issue has been broached before and
there are tickets open on the issues tracking site. As I understand it, one
solution would potentially modify bitcask to open a 'ca
Listing keys in a bucket is not necessarily going to be faster than storing the
list in an object. You might want to measure this to be sure - be aware that
list-keys is bound by the total number of keys in the cluster, not by the
amount in the bucket.
Sean Cribbs
Developer Advocate
Basho Tec
Thanks for the quick replies Sean and Alexander. One of our current
products allows users to sign up for weather alerts based on their zip
code. When we receive a weather alert for a set of locations, we need
to quickly find all users in the zip codes effected. We currently do
this with a sim
There is no limit to the amount of buckets a cluster can handle. The
only consideration I know of is when using non default bucket
properties (like bucket specific N vals). The reason being that non
default values are chatted around the cluster in the gossip channel.
-Alexander
@siculars
Scott,
There is no limit on the number of buckets unless you are changing the bucket
properties, like the replication factor, allow_mult, or the pre- and
post-commit hooks. Buckets that have properties other than the defaults
consume space in the ring state. Other than that, they are essentia
Is there a practical (or hard) limit to the number of buckets a riak cluster
can handle? One possible data model we could use for one application could
result in ~80,000 buckets. Is that a reasonable number?
Thanks,
Scott
___
riak-users mailing list
r
