Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D1DBF18840 for ; Wed, 1 Jul 2015 19:47:23 +0000 (UTC) Received: (qmail 91086 invoked by uid 500); 1 Jul 2015 19:47:21 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 91008 invoked by uid 500); 1 Jul 2015 19:47:21 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 90995 invoked by uid 99); 1 Jul 2015 19:47:21 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jul 2015 19:47:21 +0000 X-ASF-Spam-Status: No, hits=2.8 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of amansk@gmail.com designates 209.85.213.182 as permitted sender) Received: from [209.85.213.182] (HELO mail-ig0-f182.google.com) (209.85.213.182) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jul 2015 19:45:08 +0000 Received: by igrv9 with SMTP id v9so42296669igr.1 for ; Wed, 01 Jul 2015 12:46:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=aoS4zFuZc8ul1089Ktq4UmwmPS/yhx6UZLUFrwpiVU0=; b=S9E246tKBLnvgIk+e80uT6tjzQxLao2J5r+0k0dNq1pBKdBFIaFBK7WPsfPOMVjQ14 MoLTIqnphPa7gb8mAn/4DQF1J+f94bsSD0K+6FJXz8STciart2GhInA/rQgHAOnxqLhG /zOhWJYA9XcVuX23jTnTJHeHxZ8mo8Mp35uVF7r+Gs5vF4vNdTxaUT/T8zuwXCnJm7+3 oZe3nTvkodD+4Z86nTLgUFIeKDBT1qI/y/ePWzV9HEm219TQoz0DAdcpxZ2WYhaMFYGK EQSlrpXJubJ2Tsg4gyY5tuInEVKGtk0QPNzeWtfgJuAiS7J/+lKU+tEYk3O1G8xL5s5f nyDQ== X-Received: by 10.50.64.244 with SMTP id r20mr34712201igs.33.1435780014834; Wed, 01 Jul 2015 12:46:54 -0700 (PDT) MIME-Version: 1.0 Received: by 10.79.30.65 with HTTP; Wed, 1 Jul 2015 12:46:15 -0700 (PDT) In-Reply-To: References: From: Amandeep Khurana Date: Wed, 1 Jul 2015 12:46:15 -0700 Message-ID: Subject: Re: Time series scheme design To: "user@hbase.apache.org" Content-Type: multipart/alternative; boundary=047d7bea3d22c28ce00519d59545 X-Virus-Checked: Checked by ClamAV on apache.org --047d7bea3d22c28ce00519d59545 Content-Type: text/plain; charset=UTF-8 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 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 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 < > jneidi.sleiman@gmail.com> > > 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 > > > > > > --047d7bea3d22c28ce00519d59545--