Cassandra modeling is well documented on the web and a bit too complex to be explained in one mail.
I advice you reading a lot before you make modeling choices. You may start with these links : http://www.datastax.com/docs/1.1/ddl/about-data-model#comparing-the-cassandra-data-model-to-a-relational-database http://maxgrinev.com/2010/07/12/do-you-really-need-sql-to-do-it-all-in-cassandra/ and this link seem interesting, but I haven't read it yet (about indexes) : http://www.anuff.com/2011/02/indexing-in-cassandra.html I hope you'll find your answers within this documentation. Alain 2012/8/6 Baskar Sikkayan <baskar....@gmail.com>: > Hi, > Just wanted to learn Cassandra and trying to convert RDBMS design to > Canssandra. > Considered my app is being deployed in multiple Data centers. > > DB Design : > > A) CF : USER > 1) email_id - primary key > 2) fullname > 3) organization - ( I didnt create a separate table for > organization ) > > B) CF : ORG_USER > > 1) organization - Primary Key > 2) email_id > > Here, my intention is to get users belong to an > organization. > Here, I can make the organization in the user table as > secondary index, but heard that, this may hit the performance. > Could you please clarify me which is the better approach? > > > Thanks, > Baskar.S
