Return-Path: Delivered-To: apmail-hbase-user-archive@www.apache.org Received: (qmail 42569 invoked from network); 10 Jan 2011 19:02:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 10 Jan 2011 19:02:37 -0000 Received: (qmail 63730 invoked by uid 500); 10 Jan 2011 19:02:35 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 63702 invoked by uid 500); 10 Jan 2011 19:02:35 -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 63694 invoked by uid 99); 10 Jan 2011 19:02:35 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Jan 2011 19:02:35 +0000 X-ASF-Spam-Status: No, hits=1.5 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of weishung@gmail.com designates 209.85.214.41 as permitted sender) Received: from [209.85.214.41] (HELO mail-bw0-f41.google.com) (209.85.214.41) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Jan 2011 19:02:29 +0000 Received: by bwz16 with SMTP id 16so20411496bwz.14 for ; Mon, 10 Jan 2011 11:02:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=W/adhfgfk+YEnwdevuXxvniMDw5jaP/6dtkbeIHJKiE=; b=TE4KUg6gtesEQe14C7ZQcuslJu3qQAu1GPUTK//ywU4kOxARX6s8xX5zOHGtJe3NpO HsKkueBtHzcn1ggcy6+asOTuolIdrkFj/iWSIVCPa7n7LytdA7oI2jZYaKqbTOksQl+z /Wvblk7DpMX6h8Nh/auzUVRNl+dNfmhWySKUs= 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=TURlJMTapiFDKSZEAPPPwEU1NTxyin7RPgILZ92pJKD2wkz6+buhoA9MpEfwPggwIx O9yo6oKfjXUMpAUwBSOI21ED1v/DCHTzpeXV9Gf9orzXq0RZ8cETDTEJ3/JkMQo4aOPp PFENDchMZxnVNlK6p8AZowEDl2souJ9O9SozU= MIME-Version: 1.0 Received: by 10.204.70.137 with SMTP id d9mr3407386bkj.141.1294686128812; Mon, 10 Jan 2011 11:02:08 -0800 (PST) Received: by 10.204.72.133 with HTTP; Mon, 10 Jan 2011 11:02:08 -0800 (PST) In-Reply-To: <2D6136772A13B84E95DF6DA79E85A9F001344778CB97@NSPEXMBX-A.the-lab.llnl.gov> References: <2D6136772A13B84E95DF6DA79E85A9F001344778CB97@NSPEXMBX-A.the-lab.llnl.gov> Date: Mon, 10 Jan 2011 13:02:08 -0600 Message-ID: Subject: Re: customize partitioning of regionserver From: Weishung Chung To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=001636c5aa55cdb4030499829a2d X-Virus-Checked: Checked by ClamAV on apache.org --001636c5aa55cdb4030499829a2d Content-Type: text/plain; charset=ISO-8859-1 Thanks for the reply. In my use case, I have to retrieve a range of data usually by month and operate on them before reinserting them, so it would be nice if i could partition by month but then I don't know how would the partition affect the mapreduce job. On Mon, Jan 10, 2011 at 12:48 PM, Buttler, David wrote: > Not to my knowledge. Partitions are dynamically determined. As your table > grows, regions become too large and are split roughly in half. This > prevents unbalanced regions. Any predetermined partitioning will ultimately > fail because you don't know your data as well as you think you do. > > Dave > > > -----Original Message----- > From: Weishung Chung [mailto:weishung@gmail.com] > Sent: Monday, January 10, 2011 10:14 AM > To: user@hbase.apache.org > Subject: customize partitioning of regionserver > > Does HBase have the capability to partition dataset by range like the MySQL > partitioning eg. partition the datetime, row key by month? > Thank you. > --001636c5aa55cdb4030499829a2d--