Re: predicate queries (was: bitmap slices)

On Mon, Feb 1, 2010 at 1:55 PM, Jonathan Ellis wrote: > 2010/2/1 Ted Zlatanov : > here's the thing, though, and this is a main reason why cassandra > keeps things simple: doing work on the client typically results in > *less* load on the server. I agree with this in general, but while I'm not su

Re: predicate queries (was: bitmap slices)

2010/2/1 Ted Zlatanov : > My list of things I need for predicate queries across column and > supercolumn names: > > - bitmask (OR AND1 AND2 AND3 ...).  This would make my life easier and >  take load off our Cassandra servers.  Currently I have to scan the >  result sets on the client side to find

predicate queries (was: bitmap slices)

My list of things I need for predicate queries across column and supercolumn names: - bitmask (OR AND1 AND2 AND3 ...). This would make my life easier and take load off our Cassandra servers. Currently I have to scan the result sets on the client side to find the things I need. - date matchi

Re: Frequent timeout exceptions on Cassandra

One last thing, timeouts start happening to happen more frequently either with time or just more reads/writes. Suhail On Mon, Feb 1, 2010 at 9:31 AM, Suhail Doshi wrote: > So it turns out it's not socket related and it seems to only happen on my > second new node only not the first one with a h

Re: Frequent timeout exceptions on Cassandra

So it turns out it's not socket related and it seems to only happen on my second new node only not the first one with a higher load. I decommissioned the new node and replaced it with another new node from scratch but the issue persists: clients continue to timeout on it and eventual the node beco

Re: bitmap slices

2010/2/1 Ted Zlatanov : > On Mon, 1 Feb 2010 10:41:28 -0600 Jonathan Ellis wrote: > > JE> I don't think this is very useful for column names.  I could see it > JE> being useful for values but if we're going to add predicate queries > JE> then I'd rather do something more general. > > Do you have a

Re: bitmap slices

On Mon, 1 Feb 2010 10:41:28 -0600 Jonathan Ellis wrote: JE> I don't think this is very useful for column names. I could see it JE> being useful for values but if we're going to add predicate queries JE> then I'd rather do something more general. Do you have any ideas? Are you thinking of a ge

Re: bitmap slices

predicates for values would be nice, > < = and others would be quite useful jesse -- jesse mcconnell jesse.mcconn...@gmail.com On Mon, Feb 1, 2010 at 10:41, Jonathan Ellis wrote: > I don't think this is very useful for column names.  I could see it > being useful for values but if we're going

Re: bitmap slices

I don't think this is very useful for column names. I could see it being useful for values but if we're going to add predicate queries then I'd rather do something more general. 2010/2/1 Ted Zlatanov : > On Mon, 1 Feb 2010 09:42:16 -0600 Jonathan Ellis wrote: > > JE> 2010/2/1 Ted Zlatanov : >>>

Re: bitmap slices

On Mon, 1 Feb 2010 09:42:16 -0600 Jonathan Ellis wrote: JE> 2010/2/1 Ted Zlatanov : >> On Fri, 29 Jan 2010 15:07:01 -0600 Ted Zlatanov wrote: >> TZ> On Fri, 29 Jan 2010 12:06:28 -0600 Jonathan Ellis wrote: JE> On Fri, Jan 29, 2010 at 9:09 AM, Mehar Chaitanya JE> wrote: >   1. This would

Re: bitmap slices

how would this be different then the byte[] column name you can already match on? 2010/2/1 Ted Zlatanov : > On Fri, 29 Jan 2010 15:07:01 -0600 Ted Zlatanov wrote: > > TZ> On Fri, 29 Jan 2010 12:06:28 -0600 Jonathan Ellis > wrote: > JE> On Fri, Jan 29, 2010 at 9:09 AM, Mehar Chaitanya > JE> wro

Re: bitmap slices

On Fri, 29 Jan 2010 15:07:01 -0600 Ted Zlatanov wrote: TZ> On Fri, 29 Jan 2010 12:06:28 -0600 Jonathan Ellis wrote: JE> On Fri, Jan 29, 2010 at 9:09 AM, Mehar Chaitanya JE> wrote: >>>   1. This would lead to enourmous amount of duplication of data, in short >>>   if I now want to view the da

Build failed in Hudson: Cassandra #341

See Changes: [jaakko] handle empty lock root properly. CASSANDRA-704 -- [...truncated 122 lines...] [javadoc] Loading source file

Re: EOFException after upgrading to 0.5.0

Thanks for your reply. The issues have been solved. ~B On Thu, Jan 28, 2010 at 7:30 PM, Jonathan Ellis wrote: > please read NEWS.txt, both of your problems are covered there (flush > your commitlog, and don't mix 0.4 and 0.5 nodes in the same cluster) > > On Thu, Jan 28, 2010 at 6:44 AM, B R