cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Erickson <>
Subject Re: IndexOperator LT/LTE/GT/GTE Implementation
Date Fri, 10 Sep 2010 02:20:00 GMT
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 nothing for me to set EQ on.  I could work around this by
creating a column for every row with a known value like 0 and include
that column in the index clause, but that seems silly.


On Thu, Sep 9, 2010 at 4:41 PM, Jonathan Ellis <> wrote:
> 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 able to get the
>> secondary indices working for me, and queryable with IndexOperator.EQ.
>>  I have an additional index that I need to use IndexOperator.LTE on
>> for LongType, which I tried to use but the equivalent of a
>> NotImplementedException was thrown for anything other than .EQ.  I
>> found the commit introducing this:
>> 283e365196cdad3fb352de0b6d7a8c0ddd1d784a however what puzzles me is
>> the same commit claims to fix issue 1401 "allow all operators in
>> secondary clauses to index query"
>> (, and introduces
>> a test for the GTE operator.  So my question is why is the
>> ThriftValidator disallowing these queries?
>> Thanks,
>> David
> --
> Jonathan Ellis
> Project Chair, Apache Cassandra
> co-founder of Riptano, the source for professional Cassandra support

View raw message