Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of yuzhihong@gmail.com designates
 209.85.220.51 as permitted sender)
References: 
 <CAEVCm6VkJz11O7qf2C47GFT9VpvGR3c5HhuT0+2w2QysUg2pAQ@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: 
 <CAEVCm6VkJz11O7qf2C47GFT9VpvGR3c5HhuT0+2w2QysUg2pAQ@mail.gmail.com>
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <6A60EF94-70B1-4077-B293-10CE95B298E8@gmail.com>
Cc: "user@hbase.apache.org" <user@hbase.apache.org>
From: Ted <yuzhihong@gmail.com>
Subject: Re: schema design: rows vs wide columns
Date: Sun, 7 Apr 2013 11:58:16 -0700
To: "user@hbase.apache.org" <user@hbase.apache.org>

If you store service Id by month, how do you deal with time range in query t=
hat spans partial month(s) ?

With regard to number of column families, 3 is the recommended maximum.=20

Cheers

On Apr 7, 2013, at 1:03 AM, shawn du <shawndowell@gmail.com> wrote:

> Hello,
>=20
> I am newer for hbase, but i have some experience on cassandra. In the
> official document, it is said prefer to use rows instead of columns. I
> don't know whether I should follow.
> This is my user case:
> I have about hundreds of services. each service is stored by a
> number(service id). we try to store users registration for specific servic=
e
> in a day.
> so there are two solutions for this:
> rows:
> rowkey: month(2013-03) columns will be each service ids. values will be th=
e
> number for each service.
> wide columns:
> rowkey: serviceId, columns/values will be months and numbers.
>=20
> Query requirement:
> we only query for a specific service id and time between a start time and
> end time.
>=20
> so which solution is better?
>=20
> also another question:
> it is said that we 'd better desgin less than 3 column families. it is
> true? can i create as many as tables i need in hbase?
>=20
> Thanks in advance.
>=20
> BR.Shawn