Re: problem with sliceQuery with composite column

2012-02-16 Thread Deno Vichas
so i flipped the composite around to; create column family StockHistory with comparator = 'CompositeType(UTF8Type,LongType)' and default_validation_class = 'UTF8Type' and key_validation_class = 'UTF8Type'; and now i'm getting what i expected the first time. i can get a range of typ

Re: problem with sliceQuery with composite column

2012-02-16 Thread Deno Vichas
On 2/16/2012 12:46 AM, aaron morton wrote: split this CF into two? Or change the order of the column components as suggested. as suggested - where? are you saying if the flip the composite i'll be able to ask for a range by type? and cassandra is going to order by columns like; ticks:1 t

Re: problem with sliceQuery with composite column

2012-02-16 Thread aaron morton
> but it still seem a bit strange coming from years and years of sql. Think of the composite column name as a composite key. You want to write an efficient query that uses a seek and partial scan of the index b-tree, rather than a full scan. > split this CF into two? Or change the order of t

Re: problem with sliceQuery with composite column

2012-02-16 Thread Deno Vichas
thanks for the reply. i understand why, but it still seem a bit strange coming from years and years of sql. so if i want to avoid the extra load from fetching way more than i needed would i be best off split this CF into two? thanks, deno On 2/13/2012 10:41 AM, aaron morton wrote: My unde

Re: problem with sliceQuery with composite column

2012-02-13 Thread aaron morton
7;t the result be as desired? > > > - Original Message - > From: "aaron morton" > Sent: Mon, February 13, 2012 13:41 > Subject: Re: problem with sliceQuery with composite column > > My understanding is you expected to see > > 111:ticks > 222:

Re: problem with sliceQuery with composite column

2012-02-13 Thread Dave Brosius
if the composite column was rearranged as ticks:111wouldn't the result be as desired? - Original Message -From: "aaron morton" >;aa...@thelastpickle.com

Re: problem with sliceQuery with composite column

2012-02-13 Thread aaron morton
My understanding is you expected to see 111:ticks 222:ticks 333:ticks 444:ticks But instead you are getting 111:ticks 111:quote 222:ticks 222:quote 333:ticks 333:quote 444:ticks If that is the case things are working as expected. The slice operation gets a column range. So if you start at 1

problem with sliceQuery with composite column

2012-02-10 Thread Deno Vichas
all, could somebody clue me to why the below code doesn't work. my schema is; create column family StockHistory with comparator = 'CompositeType(LongType,UTF8Type)' and default_validation_class = 'UTF8Type' and key_validation_class = 'UTF8Type'; the time part works but i'm gettin