On Fri, Jan 7, 2011 at 11:38 PM, Rajkumar Gupta wrote:
> In the twissandra example,
> http://www.riptano.com/docs/0.6/data_model/twissandra#adding-friends ,
> I find that they have split the materialized view of a user's homepage
> (like his followers list, tweets from friends) into several
> colu
In the twissandra example,
http://www.riptano.com/docs/0.6/data_model/twissandra#adding-friends ,
I find that they have split the materialized view of a user's homepage
(like his followers list, tweets from friends) into several
columnfamilies instead of putting in supercolumns inside a single
Supe
The fact that subcolumns inside the supercolumns aren't indexed
currently may suck here, whenever a small no (10-20 ) of subcolumns
need to be retreived from a large list of subcolumns of a supercolumn
like MyPostsIdKeysList.
On Fri, Jan 7, 2011 at 9:58 PM, Raj wrote:
> My question is in context
My question is in context of a social network schema design
I am thinking of following schema for storing a user's data that is
required as he logs in & is led to his homepage:-
(I aimed at a schema design such that through a single row read query
all the data that would be required to put up the
