composite indexes?

2010-09-22 Thread Colin Taylor
Is this on the roadmap? I guess I cant see why it wouldnt be and we would be happy to supply patches if they were to be accepted, just puzzled by the seeming lack of interest. cheers Colin

Re: [VOTE] 0.7.0 beta2

2010-09-22 Thread Brandon Williams
On Wed, Sep 22, 2010 at 11:58 AM, Eric Evans wrote: > > It feels like 0.7.0-beta1 is becoming too distant a spec in the > rear-view, and the delta[1] is becoming quite large. I propose we > vote to release a new beta. > > SVN: https://svn.apache.org/repos/asf/cassandra/tr...@r999875 > -1 Befor

[VOTE] 0.7.0 beta2

2010-09-22 Thread Eric Evans
It feels like 0.7.0-beta1 is becoming too distant a spec in the rear-view, and the delta[1] is becoming quite large. I propose we vote to release a new beta. SVN: https://svn.apache.org/repos/asf/cassandra/tr...@r999875 0.7.0-beta2 artifacts: http://people.apache.org/~eevans The vote will be op

Re: dropped messages

2010-09-22 Thread Jonathan Ellis
that's your cluster's way of telling you to set up monitoring On Wed, Sep 22, 2010 at 8:47 AM, Carl Bruecken wrote: >  On 9/22/10 9:37 AM, Jonathan Ellis wrote: >> >> it's easy to tell from tpstats which stage(s) are overloaded >> >> On Wed, Sep 22, 2010 at 8:29 AM, Carl Bruecken >>  wrote: >>>

Re: dropped messages

2010-09-22 Thread Carl Bruecken
On 9/22/10 9:37 AM, Jonathan Ellis wrote: it's easy to tell from tpstats which stage(s) are overloaded On Wed, Sep 22, 2010 at 8:29 AM, Carl Bruecken wrote: With current implementation, it's impossible to tell from logs what the message types (verb) were dropped. I read this was changed f

Re: dropped messages

2010-09-22 Thread Jonathan Ellis
it's easy to tell from tpstats which stage(s) are overloaded On Wed, Sep 22, 2010 at 8:29 AM, Carl Bruecken wrote: >  With current implementation, it's impossible to tell from logs what the > message types (verb) were dropped.  I read this was changed for spamming, > but I think the behavior shou

dropped messages

2010-09-22 Thread Carl Bruecken
With current implementation, it's impossible to tell from logs what the message types (verb) were dropped. I read this was changed for spamming, but I think the behavior should be configurable, either aggregate counts of dropped messages or log individual occurrences with the message verb.

Hudson build is back to normal : Cassandra #543

2010-09-22 Thread Apache Hudson Server
See