Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of jdcryans@gmail.com designates
 209.85.161.41 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=bcc:mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type;
        b=H84jNwK2hfISPrfHAOhlHQ4Ys2tm0n9eJ7FEFsom4QQzgd3/X3yy+vcVtKGH0JaZyy
         PdsiaIrcSe3j7LQr94TKY5vIDXCZFkfL/zaP9XhjjNLzmR3tF5oZNTL7R3MV+jBwFVog
         6o5Fdryjy3a6FOrm7rl0jz1NYQp33KTVrO4d4=
MIME-Version: 1.0
Sender: jdcryans@gmail.com
In-Reply-To: <loom.20110222T125315-873@post.gmane.org>
References: <loom.20110222T125315-873@post.gmane.org>
Date: Tue, 22 Feb 2011 13:24:49 -0500
Message-ID: <AANLkTik8sPX0CdntZyHC=JjmVHeNuXzSADgCC_c9V1g3@mail.gmail.com>
Subject: Re: hbase table creation
From: Jean-Daniel Cryans <jdcryans@apache.org>
To: user@hbase.apache.org
Content-Type: text/plain; charset=ISO-8859-1

(moving to the user ML)

in the shell (bin/hbase shell), type: help "create"

And then you will have the help for creating table along with examples.

Regarding the actual modeling of your table, putting the userid as the
row key (no need for a family) could be a viable option but the rest
seems weird. Maybe a better option would be to have a very tall table,
and followup comments would have a row key that would place them
directly next to the commented comment. Something like

eventid_comment1
eventid_comment1_comment1
eventid_comment1_comment2
eventid_comment1_comment2_comment1
eventid_comment2
eventid_comment2_comment1

This way a single scan can return all the comments regarding the event
that's originally being commented on, while enabling deep levels of
comments. Then you only need 1 family that describes all the
attributes of that comments (userid, whatnot).

I would try to use some sort of data in the row key component of a
comment, not numbering like in my example. Also watch out for the size
of those row keys, the bigger the more space every value will take.

J-D

On Tue, Feb 22, 2011 at 6:54 AM, Davison <sreejithpk@nesote.com> wrote:
> i am new to hbase and hadoop. Any how i have succeeded in setting up a hadoop
> cluster which consists of 3 machines. Now i need some help on building up the
> database. I have a table "comments" contains fields(column families)
> 1)user id
> 2)comments
> 3)comments on comments(which can be more than one) and a status field to the
> same say,
>
> Could any one help me out to build the same using hbase/shell??
>
> Regards
>
>