Until the secondary indexes do not read before write is in a release and stabilized you should follow Ed ENuff s blog and do your indexing yourself with composites.

On Thursday, December 13, 2012, aaron morton <aaron@thelastpickle.com> wrote:
> The IndexClause for the get_indexed_slices takes a start key. You can page the results from your secondary index query by making multiple calls with a sane count and including a start key. 
> Cheers
> -----------------
> Aaron Morton
> Freelance Cassandra Developer
> New Zealand
> @aaronmorton
> http://www.thelastpickle.com
> On 13/12/2012, at 6:34 PM, Chengying Fang <cyfang@ngnsoft.com> wrote:
>
> You are right, Dean. It's due to the heavy result returned by query, not index itself. According to my test, if the result  rows less than 5000, it's very quick. But how to limit the result? It seems row limit is a good choice. But if do so, some rows I wanted  maybe miss because the row order not fulfill query conditions.
> For example: CF User{I1,C1} with Index I1. Query conditions:I1=foo, order by C1. If I1=foo return 10000 limit 100, I can't get the right result of C1. Also we can not always set row range fulfill the query conditions when doing query. Maybe I should redesign the CF model to fix it.
>  
> ------------------ Original ------------------
> From:  "Hiller, Dean"<Dean.Hiller@nrel.gov>;
> Date:  Wed, Dec 12, 2012 10:51 PM
> To:  "user@cassandra.apache.org"<user@cassandra.apache.org>;
> Subject:  Re: Why Secondary indexes is so slowly by my test?
>  
> You could always try PlayOrm's query capability on top of cassandra ;)….it works for us.
>
> Dean
>
> From: Chengying Fang <cyfang@ngnsoft.com<mailto:cyfang@ngnsoft.com>>
> Reply-To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" <user@cassandra.apache.org<mailto:user@cassandra.apache.org>>
> Date: Tuesday, December 11, 2012 8:22 PM
> To: user <user@cassandra.apache.org<mailto:user@cassandra.apache.org>>
> Subject: Re: Why Secondary indexes is so slowly by my test?
>
> Thanks to Low. We use CompositeColumn to substitue it in single not-equality and definite equalitys query. And we will give up cassandra because of the weak query ability and unstability. Many times, we found our data in confusion without definite  cause in our cluster. For example, only two rows in one CF, row1-columnname1-columnvalue1,row2-columnname2-columnvalue2, but some times, it becomes row1-columnname1-columnvalue2,row2-columnname2-columnvalue1. Notice the wrong column value.
>
>
> ------------------ Original ------------------
> From:  "Richard Low"<rlow@acunu.com<mailto:rlow@acunu.com>>;
> Date:  Tue, Dec 11, 2012 07:44 PM
> To:  "user"<user@cassandra.apache.org<mailto:user@cassandra.apache.org>>;
> Subject:  Re: Why Secondary indexes is so slowly by my test?
>
> Hi,
>
> Secondary index lookups are more complicated than normal queries so will be slower. Items have to first be queried in the index, then retrieved from their actual location. Also, inserting into indexed CFs will be slower (but will get substantially faster in 1.2 due