Just like any typical social network site users can create profiles and post contents (short messages or pics) to their designated page. Others can visit it and read/view posts. The posts will be chronologically ordered and visitors can browse through them using year / month aggregation like in blogs. My doubt is for such a system should I create a common table for contents of all users or create separate table for each individual user to store their posts. There is no limit for number of users and posts. And also it should support full text search as well. I would like to know pros and cons of single table v/s multiple tables.
Thanks, Jyothish On Sat, Aug 27, 2011 at 10:00 PM, Sonal Goyal <[email protected]> wrote: > Jyothish, > > Unless each user is generating billions and billions of records, a table per > user may be too excessive. Could you please explain your case in greater > detail? > > Best Regards, > Sonal > Crux: Reporting for HBase <https://github.com/sonalgoyal/crux> > Nube Technologies <http://www.nubetech.co> > > <http://in.linkedin.com/in/sonalgoyal> > > > > > > On Sat, Aug 27, 2011 at 9:56 PM, Jyothish Maniyath > <[email protected]>wrote: > >> Hi, >> >> I'm new to HBase database system. I wonder creating a table per user >> to store user generated content will be an appropriate or efficient >> database design with HBase. >> >> Thanks, >> Jyothish >> > -- http://member.acm.org/~jyosh
