Re: IndexOperator LT/LTE/GT/GTE Implementation

2010-09-09 Thread David Erickson
Jonathan, Thanks again for the reply, good to know. Do you have a 'best practices' suggestion on how I could map objects (currently row per object, column per property) while meeting the following 2 requirements: -Able to do the range scan on an object property, a time stamp, that is not unique, a

Re: IndexOperator LT/LTE/GT/GTE Implementation

2010-09-09 Thread Jonathan Ellis
Short version: It's dictated by indexes being CFs underneath. Your "workaround" would be substantially less efficient than not using an index at all and just using range scan. On Thu, Sep 9, 2010 at 9:20 PM, David Erickson wrote: > Hi Jonathan, > Thanks for the reply.  Why is there a limitation

Re: IndexOperator LT/LTE/GT/GTE Implementation

2010-09-09 Thread David Erickson
Hi Jonathan, Thanks for the reply. Why is there a limitation of requiring an EQ? In my case I am modeling my CF with one object per row, with columns for object properties. The query I'd like to issue is give me all objects with timestamps earlier than a specified time. In this query there is no

Re: IndexOperator LT/LTE/GT/GTE Implementation

2010-09-09 Thread Jonathan Ellis
as the validation error ("No indexed columns present in index clause with operator EQ") explains, you need at least one at EQ after which you can add others w/ other operators On Thu, Sep 9, 2010 at 1:08 PM, David Erickson wrote: > Hi all, > I have been running the nightly of Cassandra and was ab