Re: Riak cluster on Docker

2014-09-04 Thread superstructor
I only need to run one Riak instance per physical host, otherwise data redundancy guarantees are compromised in a production environment. So initially I was simply publishing the required ports to the real host interface, and then doing clustering as you would normally between Riak hosts on a netw

Re: Retrieve keys on bucket by timestamp

2014-09-04 Thread tele
Hi Sean, Received. thanks! :tele On Thu, 4 Sep 2014 08:44:14 -0500 Sean Cribbs wrote: > Hi tele, > > Yes, a secondary index is the most reasonable way to accomplish this. > Here's an example using the Python client: > > now = time.gmtime() > myobj.add_index('modified_int', now) > myobj.store

Re: Retrieve keys on bucket by timestamp

2014-09-04 Thread Alex De la rosa
damn... i got excited i missed the first line "now = time.gmtime()"... forget my stupid question... lol Thanks, Alex On Thu, Sep 4, 2014 at 4:10 PM, Alex De la rosa wrote: > This is really useful! > > So we can use "now" as a constant to get a current timestamp? > > Thanks! > Alex > > > On Thu

Re: Retrieve keys on bucket by timestamp

2014-09-04 Thread Alex De la rosa
This is really useful! So we can use "now" as a constant to get a current timestamp? Thanks! Alex On Thu, Sep 4, 2014 at 3:44 PM, Sean Cribbs wrote: > Hi tele, > > Yes, a secondary index is the most reasonable way to accomplish this. > Here's an example using the Python client: > > now = time

Re: Retrieve keys on bucket by timestamp

2014-09-04 Thread Sean Cribbs
Hi tele, Yes, a secondary index is the most reasonable way to accomplish this. Here's an example using the Python client: now = time.gmtime() myobj.add_index('modified_int', now) myobj.store() bucket.get_index('modified_int', now-3600, now+3600) Hope that helps. On Wed, Sep 3, 2014 at 9:09 PM,

Re: repair-2i stops with "bad argument in call to eleveldb:async_write"

2014-09-04 Thread Effenberg, Simon
Or could it be that the timeout is also used inside the automatic 2i AAE? Now I try to repair all partitions.. but this will take some time (2-4hours per partition with 256 partitions overall and probably only 3-4 partitions in parallel.. so ~10 days minimum). But still the question, why was it no