On Tue, Aug 7, 2012 at 2:32 AM, Baskar Sikkayan wrote:
>
> If i create one more column family based on my query instead of going with
> secondary index,
> Will it affect the write performance?
>
It won't affect writes much more than the built-in secondary indexes would,
and you'll get better read
Hi,
Thank you very much for your useful info.
I have one more doubt here.
If i create one more column family based on my query instead of going with
secondary index,
Will it affect the write performance?
Since i need to duplicate the data in the second column family as well
while writing data, Wi
Hi Baskar,
The key aspect here is, you have to think of your queries , and
denormalize. Here are my suggestions based on my understanding so far.
You seem to have 2 queries
A) what all users do I have
B) what organizations do the users belong to
The first can be a static column family- these are
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-relation
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 - (
