Return-Path: Delivered-To: apmail-hbase-user-archive@www.apache.org Received: (qmail 79366 invoked from network); 26 Oct 2010 21:50:27 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 26 Oct 2010 21:50:27 -0000 Received: (qmail 3284 invoked by uid 500); 26 Oct 2010 21:50:26 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 3260 invoked by uid 500); 26 Oct 2010 21:50:26 -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 3252 invoked by uid 99); 26 Oct 2010 21:50:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Oct 2010 21:50:26 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of saint.ack@gmail.com designates 74.125.82.51 as permitted sender) Received: from [74.125.82.51] (HELO mail-ww0-f51.google.com) (74.125.82.51) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Oct 2010 21:50:19 +0000 Received: by wwb13 with SMTP id 13so1741062wwb.20 for ; Tue, 26 Oct 2010 14:49:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:content-type:content-transfer-encoding; bh=7MPV03dd6qXv/Mky1nRcKO+TnBrSuOHmrVLAGTvTe7U=; b=RBshd1gyUwtSUSR7Kcgycub5nmsN1bs5EfXymypjpGFlOC+HmN4n0F4H6XzTIzwRHv //RZEGqbkARTE5iysbb4yi7EI17ejBpDteN3fU9QJNO/viyIrsFbUXBMGDja+IiWRXTe ecuKAa8lzXgxffKgcOFqUhg3P6AvZfYwyQdUU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=pZwYAPEjOvzFTXB33k3m7hSQov0YVYleoik3kd9Sg2JvVaHxUGwHxPBElOi7AkwaLM OowJnsASyZZukWmoQftlDgTghwgwgMd74CYac7kdqc0yeXWQqPPlLiWemHjw4D9PBLLO U9IFzuQRHk0TY7cl1HKgleZxA4JkuThuEtnIc= MIME-Version: 1.0 Received: by 10.216.38.84 with SMTP id z62mr2497wea.70.1288129798452; Tue, 26 Oct 2010 14:49:58 -0700 (PDT) Sender: saint.ack@gmail.com Received: by 10.216.45.74 with HTTP; Tue, 26 Oct 2010 14:49:58 -0700 (PDT) In-Reply-To: References: Date: Tue, 26 Oct 2010 14:49:58 -0700 X-Google-Sender-Auth: yEsaOmE7LMgERmQ81_LPLd3_Ous Message-ID: Subject: Re: question about bulk loader From: Stack To: user@hbase.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Tue, Oct 26, 2010 at 2:34 PM, Jack Levin wrote: > Hi, suppose we run bulk loader yesterday, and today, the regions names > on the same table no longer exist because of region splits, etc.? > What happens to the data when its 'loaded' into the hbase region > directories? =A0Will it make 'older' regions per, from 24 hours ago? Or > cause some sort of an issue and an exception? > > It does the right thing. It adjusts to the new lay of the land splitting the bulk written files to match new region layout as needed. See http://hbase.apache.org/docs/r0.89.20100924/xref/org/apache/hadoop/hba= se/mapreduce/LoadIncrementalHFiles.html#181 St.Ack