On 11 April 2010 07:59, Lucifer Dignified <vineetdan...@gmail.com> wrote:
> For a very simple query wherin we need to check username and password I > think keeping incremental numeric id as key and keeping the name and value > same in the column family should work. > It is highly unlikely that your application has enough usernames/passwords that you need Cassandra to store them in. If you have < 1Bn rows, I really think you should reconsider whether Cassandra is the best solution. Remember that you pay for Cassandra's high availability / scalability features with a lack of these other features (secondary indexes, joins, query optimiser) - be sure it's worth it. There are workarounds, but they essentially involve rewriting your RDBMS to use Cassandra as a back-end. This is not a simple task, nor one which should be necessary. Remember that if you have SOME big data, and some small data, you don't need to keep it all in the same place. A common use-case is to keep your big stuff (heavy write workloads etc) in Cassandra and the others in a more familiar database. Mark
