For such queries, looks like you may create a composite key as (user_id,age, salary).
Too much indexing always kills(irrespective of RDBMS or NoSQL). Remember every search request on secondary indexes will be passed on each node in ring. -Vivek On Tue, Aug 27, 2013 at 11:11 PM, Sávio Teles <savio.te...@lupa.inf.ufg.br>wrote: > Use a database that is designed for efficient range queries? ;D >> > > Is there no way to do this with Cassandra? Like using Hive, Sorl... > > > 2013/8/27 Robert Coli <rc...@eventbrite.com> > >> On Fri, Aug 23, 2013 at 5:53 AM, Sávio Teles <savio.te...@lupa.inf.ufg.br >> > wrote: >> >>> I need to perform range query efficiently. >>> >> ... >> >>> This query takes a long time to run. Any ideas to perform it >>> efficiently? >>> >> >> Use a database that is designed for efficient range queries? ;D >> >> =Rob >> >> > > > > -- > Atenciosamente, > Sávio S. Teles de Oliveira > voice: +55 62 9136 6996 > http://br.linkedin.com/in/savioteles > Mestrando em Ciências da Computação - UFG > Arquiteto de Software > Laboratory for Ubiquitous and Pervasive Applications (LUPA) - UFG >
