Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of yuzhihong@gmail.com
 designates 209.85.161.41 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=cCNBqNWl0ut6pxDoVuUUmA0UYxulAISIMFdrZCNqGgxPa7pN7xWoM+tUEk25t0bXZ5
         xnuz2EGpJ84VLQ337Lc0JhaxH2LI+q1k7+W5U2QZ98mEYSmFDBFjasclZX3w0v6PUwV4
         bW1kjq5n+jXhCJCNJZtWEBBOiF4w1hLw2iHdc=
MIME-Version: 1.0
In-Reply-To: <1300550031.7248.10.camel@niels-laptop>
References: <1300550031.7248.10.camel@niels-laptop>
Date: Sat, 19 Mar 2011 09:30:58 -0700
Message-ID: <AANLkTimnV7mxy_14N1zGis7pxYe8Oz0iP2L4ZyQtZcSO@mail.gmail.com>
Subject: Re: Newbie question concerning schema design
From: Ted Yu <yuzhihong@gmail.com>
To: user@hbase.apache.org
Content-Type: multipart/alternative; boundary=001517491d5460424f049ed86bd1

--001517491d5460424f049ed86bd1
Content-Type: text/plain; charset=ISO-8859-1

See:
http://search-hadoop.com/m/zbKmE14o0Js/wide+tall+hbase+table&subj=Re+Parent+child+relation+go+vertical+horizontal+or+many+tables+

You can also search for related discussion on tall vs. wide tables.

On Sat, Mar 19, 2011 at 8:53 AM, Niels Nuyttens <niels.nuyttens@gmail.com>wrote:

> Hi all,
>
> I'm need a database scaled for large datasets and high throughput. HBase
> seemed like the way to go. However, while designing my database schema I
> started to doubt my choice, due to the conversion of the current
> relational schema to a NoSQL variant. I can't get my head around the
> efficient implementation of many-to-many relations.
>
> For example: Users and Roles. How would you model that for HBase. I was
> thinking about storing associated roles in a column of a user row, and
> vice versa.
>
> Furthermore there are lots of one-to-many relations that also need
> converting.
>
> So, in conclusion, my question is: is it possible to convert a
> relation-oriented schema to a nosql one? If so, how can this modeling be
> done efficiently?
>
> Lots of thanks,
>
> Niels
>
>

--001517491d5460424f049ed86bd1--