>From what I read in another thread, Cassandra isn't used for isn't 'ideal'
for keeping track of counts.
For example, I would undertand this to mean keeping track of which stories
were dugg.
If this is true, how would a site like digg keep track of the 'dugg'
counter?
Also, I am assuming with ev
They don't use cassandra for it yet.
-ryan
On Tue, Apr 6, 2010 at 9:00 AM, S Ahmed wrote:
> From what I read in another thread, Cassandra isn't used for isn't 'ideal'
> for keeping track of counts.
> For example, I would undertand this to mean keeping track of which stories
> were dugg.
> If thi
Is it just the counters they are using mysql/postgresql for or also the list
of stories?
e.g. get me the top stories in category x.
On Tue, Apr 6, 2010 at 12:50 PM, Ryan King wrote:
> They don't use cassandra for it yet.
>
> -ryan
>
> On Tue, Apr 6, 2010 at 9:00 AM, S Ahmed wrote:
> > From wha
That's not true. We have been using the Zookeper work we posted on jira. That's
what we are using internally and have been for months. We are now just wrapping
up our vector clocks + distributed counter patch so we can begin transitioning
away from the Zookeeper approach because there are proble
Chris,
When you so patch, does that mean for Cassandra or your own internal
codebase?
Sounds interesting thanks!
On Tue, Apr 6, 2010 at 12:54 PM, Chris Goffinet wrote:
> That's not true. We have been using the Zookeper work we posted on jira.
> That's what we are using internally and have been
http://issues.apache.org/jira/browse/CASSANDRA-704
http://issues.apache.org/jira/browse/CASSANDRA-721
We have our own internal codebase of Cassandra at Digg. But we are using those
above patches until we have the vector clock work cleaned up, that patch will
also goto jira. Most likely the vecto
What will be the latency for the zk based atomic increase?
On Tue, Apr 6, 2010 at 8:22 PM, Chris Goffinet wrote:
> http://issues.apache.org/jira/browse/CASSANDRA-704
> http://issues.apache.org/jira/browse/CASSANDRA-721
> We have our own internal codebase of Cassandra at Digg. But we are using
> t
Can we not implement counts by just storing all the deltas in a row, and
then summing them all up to acheive a count.
If a row ends up with too many deltas, a reader could just summarise the
deltas occasionally into a single value (in a way which avoids race
conditions, of course).
So you'd map
On Sun, Apr 11, 2010 at 3:30 AM, Mark Robson wrote:
> Can we not implement counts by just storing all the deltas in a row, and
> then summing them all up to acheive a count.
>
> If a row ends up with too many deltas, a reader could just summarise the
> deltas occasionally into a single value (in a
