News for hackers. Stuff that matters.
Re:Cassandra By Example by strebler on Wednesday May 12, 2010 @04:21PM (#1342123)
In a database, yes, a single table with two indexes would efficiently look up followings/followers.

But in Cassandra there is no support for secondary indexes, so the follower/following data needs to be in separate column families. Then, they each have an index and can be looked up efficiently. (At least as far as I understand things in the NoSQL world)

Re:Cassandra By Example by dagheti on Thursday May 13, 2010 @07:38AM (#1343892)
So what happens when you create the follower but not followed index then realize you need it. Is there a way to create that new ColumnFamily without writing a object-by-object program that must traverse all the data? I suppose the concept of data locality doesn't apply, but what is the best way to do that sort of operation?
Re:Cassandra By Example by buss on Thursday May 13, 2010 @11:41AM (#1344565)
You'd write a MapReduce program to do it. Cassandra 0.6 has full support for Hadoop.