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 nanhengwu@gmail.com
 designates 209.85.214.169 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:content-transfer-encoding;
        b=uPfmZznAf6EDKwfwpDQ02908HNYzb8NYLgfhe8yEDVdh4uqtO6z3Mou6npAYODaOSb
         HhGrjOig4b35t5TH1K/jvAIKWuklKhhCpXJaQ+ao/y8Kp/TS3lU213lMDZr6f+nleIVe
         kt2H762rnkIUcLCSpkiJ40zgSkpKMDGRXIJ/I=
MIME-Version: 1.0
In-Reply-To: <AANLkTin6hK5A9zBNJ_=4xGk5A-C7mOXPDCCfTKSENFY4@mail.gmail.com>
References: <AANLkTikUy-g_=rEbySY7BTuJfkch8NByTahnHpHCjMQT@mail.gmail.com>
	<AANLkTikjLiWsQQmZq=4ETz5yA9swf8DD+aQmtoGHU2A-@mail.gmail.com>
	<AANLkTimEWNbZ6=DL7i=4myvXytrw6sA0Se8HmUBZSsL3@mail.gmail.com>
	<AANLkTik-hiGiSig+KpAP5e-EROR3LoMFLE50qAFahcS8@mail.gmail.com>
	<AANLkTinZ7S00msMmvvB809JsVoT0F+fJKoZTk5GY3jUc@mail.gmail.com>
	<AANLkTin6hK5A9zBNJ_=4xGk5A-C7mOXPDCCfTKSENFY4@mail.gmail.com>
Date: Fri, 28 Jan 2011 09:38:05 -0800
Message-ID: <AANLkTinC6J+HoEGx3gwzgaFFe470xF5bWwGX8vL38N1z@mail.gmail.com>
Subject: Re: Use loadtable.rb with compressed data?
From: Nanheng Wu <nanhengwu@gmail.com>
To: user@hbase.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Stack,

  Get doesn't work either. It was a fresh table created by
loadtable.rb. Finally, the uncompressed version had the same number of
regions (8 total). I totally understand you guys shouldn't be patching
the older version, upgrading for me is an option but will be pretty
painful. I wonder if I can figure something out by comparing the two
version's Hfile. Thanks again!

On Fri, Jan 28, 2011 at 9:14 AM, Stack <stack@duboce.net> wrote:
> On Thu, Jan 27, 2011 at 9:35 PM, Nanheng Wu <nanhengwu@gmail.com> wrote:
>> In the compressed case, there are 8 regions and the region start/end
>> keys do line up. Which actually is confusing to me, how can hbase read
>> the files if they are compressed? does each hfile have some metadata
>> in it that has compression info?
>
> You got it.
>
>> Anyway, the regions are the same
>> (numbers and boundaries are same) in both compressed and uncompressed
>> version. So what else should I look into to fix this? Thanks again!
>
> You can't scan. Can you Get from the table at all? =A0Try getting start
> key from a few of the regions you see in .META.
>
> Did this table preexist or was this a fresh creation?
>
> When you created this table uncompressed, how many regions was it?
>
> How about just running uncompressed while you are on 0.20.6? =A0We'd
> rather be fixing bugs in the new stuff, not the version that we are
> leaving behind?
>
> Thanks,
> St.Ack
>