Re: Pagination with Ripple

2012-07-19 Thread Eric Moritz
but unless you're holding lots data > in ram _somewhere_, your service is never really going to run at interactive > speeds. This is true of all data systems, not just riak, consider highly > random access to a traditional RDBMS with data > ram and no indexes. > > - Alex &

Re: Pagination with Ripple

2012-07-19 Thread Catherine Jung
h data > ram and no > indexes. > > > > - Alex > > > > - Original Message ----- > > From: "Martin Stabenfeldt" > > To: riak-users@lists.basho.com > > Sent: Thursday, July 19, 2012 3:15:25 AM > > Subject: Re: Pagination with Ripple >

Re: Pagination with Ripple

2012-07-19 Thread Alexander Sicular
- Original Message - > From: "Martin Stabenfeldt" > To: riak-users@lists.basho.com > Sent: Thursday, July 19, 2012 3:15:25 AM > Subject: Re: Pagination with Ripple > > > > Hi, > > > We´re also in the hundreds of thousands scale. So loading

Re: Pagination with Ripple

2012-07-19 Thread Alex Thompson
sider highly random access to a traditional RDBMS with data > ram and no indexes. - Alex - Original Message - From: "Martin Stabenfeldt" To: riak-users@lists.basho.com Sent: Thursday, July 19, 2012 3:15:25 AM Subject: Re: Pagination with Ripple Hi, We´re also in the hun

Re: Pagination with Ripple

2012-07-19 Thread Sean Cribbs
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

Re: Pagination with Ripple

2012-07-19 Thread Vlad Gorodetsky
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-

Re: Pagination with Ripple

2012-07-19 Thread Martin Stabenfeldt
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

Re: Pagination with Ripple

2012-07-18 Thread Alex Thompson
My 2c: 1000s of subscribers per list isn't a problem. Just have a data object which represents the subscriber list, store a list of subscriber ids in the subscriber list object. Load the whole list every time, and sort/paginate in your app code. Unless you're planning on shuffling the lists a

Re: Pagination with Ripple

2012-07-18 Thread Martin Stabenfeldt
If someone has an example on how this is implemented with Ripple, I´d be very happy to see them! :-) -- Martin Stabenfeldt Tlf: +47 93441707 On Wednesday, 18 July 2012 at 09:59, Martin Stabenfeldt wrote: > Thanks, Matthew! > > I´ll give that a go! :-) > > -- > Martin Stabenfeldt > >

Re: Pagination with Ripple

2012-07-18 Thread Martin Stabenfeldt
Thanks, Matthew! I´ll give that a go! :-) -- Martin Stabenfeldt -- Martin Stabenfeldt Sent with Sparrow (http://www.sparrowmailapp.com/?sig) On Wednesday, 18 July 2012 at 09:51, Matthew Tovbin wrote: > Martin, > > You may try to use range queries > (https://github.com/basho/riak-ruby-

Re: Pagination with Ripple

2012-07-18 Thread Matthew Tovbin
Martin, You may try to use range queries for this purpose in couple with LevelDB as a backend. .../buckets//\$key// And in case you a ready to sacrifice performance, you may use Solr, which is available through Riak Search