Return-Path: 
 <user-return-17373-apmail-hbase-user-archive=hbase.apache.org@hbase.apache.org>
Delivered-To: apmail-hbase-user-archive@www.apache.org
Received: (qmail 89827 invoked from network); 20 Mar 2011 19:52:51 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 20 Mar 2011 19:52:51 -0000
Received: (qmail 16627 invoked by uid 500); 20 Mar 2011 19:52:49 -0000
Delivered-To: apmail-hbase-user-archive@hbase.apache.org
Received: (qmail 16595 invoked by uid 500); 20 Mar 2011 19:52:49 -0000
Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@hbase.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@hbase.apache.org>
List-Post: <mailto:user@hbase.apache.org>
List-Id: <user.hbase.apache.org>
Reply-To: user@hbase.apache.org
Delivered-To: mailing list user@hbase.apache.org
Received: (qmail 16587 invoked by uid 99); 20 Mar 2011 19:52:49 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 20 Mar 2011 19:52:49 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of oruchovets@gmail.com
 designates 74.125.82.169 as permitted sender)
Received: from [74.125.82.169] (HELO mail-wy0-f169.google.com) (74.125.82.169)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 20 Mar 2011 19:52:45 +0000
Received: by wyf19 with SMTP id 19so6543486wyf.14
        for <user@hbase.apache.org>; Sun, 20 Mar 2011 12:52:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:in-reply-to:references:date
         :message-id:subject:from:to:content-type;
        bh=gonT/UDMC/IBTp/DYmnict1L7bK7U0IPA8Gx9RdmGIk=;
        b=ggJ+hKsnkiRbS7I6+a2+qzzFjcsy9bKLdKru4oWkQWI51kUIgXvTvxO+toI2EHjJlP
         AFHe2KB6u2vnlkw77xm2Rew6hiMHJ5SDCdgHZAGU7yJ5m/mqCF+ZNRm1aQi34BqHYl1Q
         L+YvOvlOzFGv7VpC7urNNvTrUYLs7QtheP53w=
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=jXcD1FRWHA5MfSB1csr00ulPiaJ+2Bv1g/ycng7VDWIKzrHxzKX06nqFwXJDRZMvrn
         SUaj5iG+0xMfmZlAthrhcOEt23Us2urgxQJGZwZR4GVkEIXq2xExFBxklgucGTpQFBMQ
         LisERMWjEfid9nwUzrHTqONiC8Mz5kMARz2W0=
MIME-Version: 1.0
Received: by 10.216.234.203 with SMTP id s53mr3705708weq.54.1300650744584;
 Sun, 20 Mar 2011 12:52:24 -0700 (PDT)
Received: by 10.216.164.142 with HTTP; Sun, 20 Mar 2011 12:52:24 -0700 (PDT)
In-Reply-To: <B0278095-A144-4E4F-8DE3-D0404B2A4436@email.com>
References: <AANLkTikQJXGAO_s9=-DtxR9U+0+0cFXr5svnL=MsYFRG@mail.gmail.com>
	<AANLkTim0zdRoQbkoA2sfJKp+rRd3G+LKy2cywz85YujE@mail.gmail.com>
	<AANLkTinQjGccTQaOtz_-2w6v0q=G+w6OUGDxsF6=tQVN@mail.gmail.com>
	<B0278095-A144-4E4F-8DE3-D0404B2A4436@email.com>
Date: Sun, 20 Mar 2011 21:52:24 +0200
Message-ID: <AANLkTimBRUu=M3y2zqHaTemMaD1V2MDM6wfaEhm-5=Xk@mail.gmail.com>
Subject: Re: hash function per table
From: Oleg Ruchovets <oruchovets@gmail.com>
To: user@hbase.apache.org
Content-Type: multipart/alternative; boundary=000e0cd4cd7c9b9cf2049eef59c3

--000e0cd4cd7c9b9cf2049eef59c3
Content-Type: text/plain; charset=ISO-8859-1

Actually discussion started from this post:


http://search-hadoop.com/m/XX3nW68JsY1/hbase+insertion+optimisation&subj=hbase+insertion+optimisation+

Simply inserting the data in which row key <date>_<somedata> I noticed that
only one node works (region to which data were writing). In case we have
10-15 nodes I think it is inefficient to write data to only one region. I
want to get an effect that data will be inserted to  as much as possible
nodes  simultaneously. Correct me guys ,  but in this case  writing job
will take less time , am I write?

Oleg.

On Sun, Mar 20, 2011 at 8:57 PM, Chris Tarnas <cft@email.com> wrote:

> There is none - HBase uses a total order partitioner. The straight key
> value itself determines which region a row is put into. This allows for very
> rapid scans of sequential data, among other things but does mean it is
> easier to hotspot regions. Key design is very important.
>
> -chris
>
> On Mar 20, 2011, at 11:41 AM, Lior Schachter wrote:
>
> > the hash function that distributes the rows between the regions.
> >
> > On Sun, Mar 20, 2011 at 8:36 PM, Stack <stack@duboce.net> wrote:
> >
> >> Hash?  Which hash are you referring to sir?
> >> St.Ack
> >>
> >> On Sun, Mar 20, 2011 at 10:06 AM, Lior Schachter <liors@infolinks.com>
> >> wrote:
> >>> Hi,
> >>> What is the API or configuration for changing the default hash function
> >> for
> >>> a specific htable.
> >>>
> >>> thanks,
> >>> Lior
> >>>
> >>
>
>

--000e0cd4cd7c9b9cf2049eef59c3--