a. All
> based on 0.6 beta2.
>
> -Weijun
>
> -Original Message-
> From: Jonathan Ellis [mailto:jbel...@gmail.com]
> Sent: Saturday, March 13, 2010 5:36 AM
> To: cassandra-user@incubator.apache.org
> Subject: Re: question about deleting from cassandra
>
> You
10 5:36 AM
To: cassandra-user@incubator.apache.org
Subject: Re: question about deleting from cassandra
You should submit your minor change to jira for others who might want to try
it.
On Sat, Mar 13, 2010 at 3:18 AM, Weijun Li wrote:
> Tried Sylvain's feature in 0.6 beta2 (need minor cha
You should submit your minor change to jira for others who might want to try it.
On Sat, Mar 13, 2010 at 3:18 AM, Weijun Li wrote:
> Tried Sylvain's feature in 0.6 beta2 (need minor change) and it worked
> perfectly. Without this feature, as far as you have high volume new and
> expired columns y
Tried Sylvain's feature in 0.6 beta2 (need minor change) and it worked
perfectly. Without this feature, as far as you have high volume new and
expired columns your life will be miserable :-)
Thanks for great job Sylvain!!
-Weijun
On Fri, Mar 12, 2010 at 12:27 AM, Sylvain Lebresne wrote:
> I gue
I guess you can also vote for this ticket :
https://issues.apache.org/jira/browse/CASSANDRA-699 :)
--
Sylvain
On Fri, Mar 12, 2010 at 8:28 AM, Mark Robson wrote:
> On 12 March 2010 03:34, Bill Au wrote:
>>
>> Let take Twitter as an example. All the tweets are timestamped. I want
>> to keep
On 12 March 2010 03:34, Bill Au wrote:
> Let take Twitter as an example. All the tweets are timestamped. I want to
> keep only a month's worth of tweets for each user. The number of tweets
> that fit within this one month window varies from user to user. What is the
> best way to accomplish t
I've been thinking more about a similar sort of problem.
The major difference between normal relational databases and big hashtables
is that in the former you can sort and retrieve on any column. In big
hashtables (or at least from Cassandra), you only have 1 field to sort on
and the sort type is
