For that, I think you'll have to create a separate table with the reverse relationship.
On Wed, Jul 1, 2015 at 12:07 PM, Sleiman Jneidi <[email protected]> wrote: > Hi Amandeep, thanks for that . I've read it already as well as your book. > But I believe that it doesn't discuss the "feed" problem , ie: get latest > posts from the 2k people I follow. That's for me is the challenge. I would > really appreciate any ideas. > Thank you. > On Wed, 1 Jul 2015 at 7:57 pm Amandeep Khurana <[email protected]> wrote: > > > Hi Sleiman > > > > Take a look at this for some ideas: > > > > > http://0b4af6cdc2f0c5998459-c0245c5c937c5dedcca3f1764ecc9b2f.r43.cf2.rackcdn.com/9353-login1210_khurana.pdf > > > > -Amandeep > > > > On Wed, Jul 1, 2015 at 11:53 AM, Sleiman Jneidi < > [email protected]> > > wrote: > > > > > Hello everyone, I am working on a scheme design for a time series > > database. > > > Something very similar to Twitter where people can follow each other > and > > > see their posts. I've looked at opentsdb but I think my problem is more > > > complicated because I don't have the leading "metricid" in the row key. > > > I've made several attempts so far but I am not happy with the > > performance. > > > > > > 1. Md5(user)+timestamp . The problem with is when I want to query the > > feed, > > > I have to do a scan with the highest user ( alphabetical order) and the > > > lowest and then add column column filter. Getting the next batch is > hard. > > > > > > 2. Md5(user)+day and then put the posts of the day in the columns with > > > timestamp in the qualifier name. Not optimal, getting the next batch is > > > hard. > > > > > > So... What do you guys think? Any ideas for making this efficient or > > > possible? > > > > > > Thanks for your time in reading this. > > > Sleiman > > > > > >
