Kevin,
A few points:
- It's recommended that you avoid passing in a whole bucket as an
argument to a map/reduce query as this results in keys for the bucket being
listed, which as you know is an expensive operation.
- The .Link() function is a function that says "please extract links
Hello,
I created lager backend for Ybot -
https://github.com/0xAX/lager_ybot_backend. Ybot is chatrobot (
https://github.com/0xAX/Ybot).
Now you can receive your lager error messages in real time in your chat
rooms.
Now it's supports:
* IRC
* XMPP
* 37signals campfire chat.
* Google
First off thank you. I dont know why the learning curve is so steep for me.
I am just looking at the example on CIs web site. I have seen the warnings
about sending a whole bucket as input.
Rather than specifying what links you are interested in what about all the
links associated with t
Also: Is there an ETA on Riak Control?
On Thu, Feb 7, 2013 at 10:08 AM, Ian Ha wrote:
> +1.
>
> Developing a comprehensive admin console would be great.
>
> I would add merge statistics to Chad's feature requests. Would be nice to
> see who how much disk space is saved during merges, which merg
+1.
Developing a comprehensive admin console would be great.
I would add merge statistics to Chad's feature requests. Would be nice to
see who how much disk space is saved during merges, which merge/threshold
triggers were hit, and possible disk usage at that time.
On Wed, Feb 6, 2013 at 2:21 P
We need records in our database to only live for a certain period of
time (and we are using Bitcask). At first glance, expiry_secs seems to
be exactly what we are looking for.
The problem is, these records need to be pruned when they are older than
10 days *according to date information in the
Let me clarify that a bit, after 10 days there will be about 2 - 3
millions records in that bucket, about 200,000 - 300,000 of those
records will need to be pruned off nightly.
-Chad
From: riak-users [mailto:riak-users-boun...@lists.basho.com] On Behalf
Of Chad Engler
Sent: Thursday, Februa
Nice! Thanks for sending this along.
I have to ask, how ... annoying is this in production? Meaning what
volume of error traffic does it spew into your chat rooms? :)
Mark
On Thu, Feb 7, 2013 at 5:49 AM, Alex toyer
wrote:
> Hello,
>
> I created lager backend for Ybot -
> https://github.com/0xAX
Hello Mark,
It's initial release of lager_ybot_backend and at that moment it sends to
chat only [error] messages, yes it can be both annoying and a configurable
at one time. I think it can be useful sometime...
Thank you.
2013/2/7 Mark Phillips
> Nice! Thanks for sending this along.
>
> I hav
Hey Alex,
On Thu, Feb 7, 2013 at 9:40 AM, Alex toyer
wrote:
> Hello Mark,
>
> It's initial release of lager_ybot_backend and at that moment it sends to
> chat only [error] messages, yes it can be both annoying and a configurable
> at one time. I think it can be useful sometime...
>
Thanks for th
Sorry Mark, apparently I misunderstood.
About best practices, I've been going to write good documentation in one
place for Ybot and for all parts, and lager_ybot_backend of course, but
everything takes time to develop. When will the documentation i let you
know.
If are there questions about Ybot
Hi Chad,
I recommend looking at secondary indexes. You can set up a secondary index
with the relevant date from your entry. Note that there is no data type
date, only string or integer. But you can easily convert a date into a
string or an integer for your query purposes. Secondary indexes even
pr
I'm writing the prune script in Node, and the dates are stored as int
timestamps so that isn't an issue.
I was under the impression that secondary indexes only worked on the LevelDB
backend, we have a solid write throughput (maybe 10ish writes per second) and
very little read (aside from the
Hi All,
Basho is expanding the RICON [0] Conference series this year.
We're beyond excited to officially announce RICON East [1]. It's happening
May 13-14th at New World Stages in New York City. As with last year's event
[2], RICON East will be dedicated to developers building and using
distribut
Kevin Burton wrote:
kb> I replaced the 127.0.0.1 with the address for my cluster (I have 4
kb> nodes in the cluster). I get an error: `[info] can't set long node
kb> name Please check configuration' followed by a fatal error [error]
kb> Failed to start net kernel.
Kevin, what arguments did you
15 matches
Mail list logo
