Hi,
We´re also in the hundreds of thousands scale. So loading everything is
unfortunately not possible.
Would be nice if one could settle for one database, instead of mixing different
types. Nice to only care about scaling and providing redundancy for Riak,
instead of Riak and PostgreSQL :-)
I
As far as I see it, there's no "good" way of doing that, since this
awareness about the number of keys/buckets is very expensive in a
Dynamo-like system (in some cases 2i may be the rescue, I believe).
I remember there's a post on similar topic by Mathias:
http://www.paperplanes.de/2011/12/13/list-
Right, the problem goes way beyond just the client-side libraries.
Relational databases can do "pagination" easily because of the ORDER BY,
LIMIT and OFFSET query modifiers. Reid Draper has previously shared a plan
for limited/resumed 2I queries in Riak, but that feature won't be in Riak
1.2, nor w
Hi,
The repair function triggers some errors :
riak_search_vnode:repair().
First, an unexpected message is received by mi_server gen_server :
13:27:20.165 [error] Unexpected info
{#Port<0.17562700>,{data,[2,0,0,0,0,0,0,0,1|<<128>>]}}
Then after some time we can see the same error as with sea
I agree, but sometimes you make sacrifices. ;)
Alternatively, you could use something like redis or memcache to hold keylists,
either populated dynamically with key lists, or loaded with data on startup.
You might even be able to get away with just some reasonably complex
send-current-and-refre
On Thu, Jul 19, 2012 at 9:37 AM, Arnaud Wetzel wrote:
> Hi,
> The repair function triggers some errors :
> riak_search_vnode:repair().
>
> First, an unexpected message is received by mi_server gen_server :
>
> 13:27:20.165 [error] Unexpected info
> {#Port<0.17562700>,{data,[2,0,0,0,0,0,0,0,1|<
I have always paired Riak with Redis for exactly this issue. Redis provides the
data structures that Riak lacks. Pagination schemes via Redis are fairly
trivial. To obviate the SPOF issue you should replicate Redis but what I do in
addition is persist Redis keys to Riak on some frequency. Of cou
We're pairing Redis and Riak too - Riak for the 'proper' persistence, and
Redis for a cache of what's in use right now - Redis has all sorts of handy
bits which play really nicely for this purpose.
Catherine
On Thu, Jul 19, 2012 at 4:59 PM, Alexander Sicular wrote:
> I have always paired Riak wi
I've fooled around with paginating large lists of keys in Riak. A
technique that I have found is to emulate a set using 2i with
Lexicographically sorted keys. You can then emulate a db cursor using
a ranged 2i query to get chunks of values. You'll do repeated queries
to get chunks of data to bui
Hi,
We are exploring using Riak as our persistent storage for our next project.
Does Java client support search with paging and sorting, like the web solr api?
If yes, can you point one with class/method support it?
Here is an example with page and number of rows per page set,
curl "http://localh
10 matches
Mail list logo
