There´s a simple comparison that helped me a lot taking my first steps with cassandra:
keyspace = database CF = table ;o) And this one: http://arin.me/blog/wtf-is-a-supercolumn-cassandra-data-model Btw, love the new secondary indexes in cassandra 0.7, this saves a lot of time and work! But don´t use beta-3! It has some buggy limitations. ;o) Instead, svn check out the latest branch from here: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7/ Than make a: $ ant clean $ ant jar in that directory to build the project. And you are good to go. Works for me. :o) I hope his helps a bit starting your project. ;o) greetings André from Germany 2010/11/19 Nanheng Wu <nanhen...@gmail.com> > Hi, > > Our team decided to use Cassandra as storage solution to a dataset. > I am very new to the NoSQL world and Cassandra so I am hoping to get > some help from the community: The dataset is pretty simple, we have > for each key a number of columns with values. Each day we compute a > new version of this dataset, the new version will mostly update > existing keys but could also add and delete some keys. (And we'll > build a service that queries Cassandra). A key requirement for us is > we want to keep versions of the dataset and keep N versions around, > this is in case we discover problems in the current version and need > to "roll up" to an older one. I thought about creating a Column Family > per version, this means we will create a new column family every day > and occasionally delete column families according to some truncation > policy. I know Cassandra 0.7 now makes changing schema easier, but is > this a good way to go? I would really like to hear what you guys think > is the better way to handle this. Thank you. > > Best, > Alex >
