Hi, Thanks for your answer.
> Cassandra's default is to store the rows randomly (using a hash of the > key), so there isn't a way of retrieving the keys that match some filter > without iterating through all of them. There are some things you can do, > like use an ordered partitioner to store the rows in order, but that is not > recommended because you wont get even distribution throughout our cluster. > > I think your best bet though is just use the master_id for your row key, > and then use composite columns that begin with the client_id. > In this case I believe that the supercolumn approach can be valid. This CF only store a little amount of data for any user and no often changes, i think a supercolumn and some file caching of results can be a nice solution with no penalty in performance. -- Juan Ezquerro LLanes <Sofistic Team> Telf: 618349107/964051479
