Re: boonfilters

[Tim Estes]

Bloomfilters I think is what you mean- correct?


Sent from my iPhone

On Apr 7, 2010, at 3:27 PM, "S Ahmed"  wrote:


Just reading up on boonfilters, few questions.

Basically boonfilters let give you a true/false if a particular key  
exists,
and they *may* give you a false positive i.e. they key exists but  
never a

false negative i.e. the key doesn't exist.

The core of boonfilters is its hashing mechanism that marks the in- 
memory

matrix/map if the key exists.

1. Is the only place boonfilters are used in Cassandra is when you  
want to

see if a particular key exists in a particular node?

2. Are boonfilters a fixed size, or they adjust as to the # of  
keys?  any

example size?

3. Boonfilters don't give false negatives:
   So you hit a node, and perform a lookup in the boonfilter for a  
key.  It
says "yes", but when you do a lookup the object returned is null, so  
then

you flag that this node needs this particular key during replication.


Have I grasp this concept?

Really loving this project, learning allot from the code.  It would  
be great
if someone could do a walkthrough of common functionality in a  
detailed way

:)

Re: Time for 1.0

[Tim Estes]

Speaking more for an organization that works with a lot of external parties 
using Cassandra (that don't necessarily develop on it), I think the pivot to 
1.0 makes better sense. A lot of the world is still coming to know Cassandra 
vs. any other NoSQL type solution. In that environment, I think the production 
grade validation is important.

to the point below... I'd submit that sometimes you jump for 8.0 to 10.0. Then 
we just move the decimal.

Really- I'm sure that groups can make the shift and get it. 

+1 to Jonathan's original suggestion.

-- 
Tim Estes
CEO 
Digital Reasoning Systems



On Jan 13, 2011, at 1:58 AM, Daniel Lundin wrote:

> On Wed, Jan 12, 2011 at 5:29 AM, Eric Evans  wrote:
>> I'd rather drop the leading the 0 and continue to number releases
>> sequentially the way we have.  If our < 1 versioning is signaling a lack
>> of readiness, and if >= 1 is a necessary gate, then 8.0 should work
>> equally as well.  Better in fact, 8 times better!
> 
> +1 for semantic versioning <http://semver.org/>.
> 
> It may not be perfect (whatever that means) but at least it has a
> common, [well] defined meaning.
> 
> As for `due diligence`, that's a fine codename for the next release. :)

Re: Jenkins build became unstable: Cassandra-Coverage #131

[Tim Estes]

+1

Sent from my iPhone

On Sep 22, 2011, at 5:46 PM, "Eric Evans"  wrote:

> On Thu, Sep 22, 2011 at 7:28 PM,   wrote:
>> FUCK YOU & JENKINS YOU STUPID GEEKS
> 
> http://goo.gl/0rylR
> 
>> --Original Message--
>> From: Apache Jenkins Server
>> To: dev@cassandra.apache.org
>> ReplyTo: dev@cassandra.apache.org
>> Subject: Jenkins build became unstable:  Cassandra-Coverage #131
>> Sent: Sep 22, 2011 8:20 PM
>> 
>> See 
>> 
>> 
>> 
>> 
>> Sent from my Verizon Wireless BlackBerry
>> 
> 
> 
> 
> -- 
> Eric Evans
> Acunu | http://www.acunu.com | @acunu