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 yuzhihong@gmail.com
 designates 209.85.214.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <150xtipwh34np7wqv931gelm.1415286303933@email.android.com>
References: 
 <CAOF-KfhJhcTpvY2-9GjJX59xJzjaKxEafMMbszqFHnDfLAfBrA@mail.gmail.com>
	<150xtipwh34np7wqv931gelm.1415286303933@email.android.com>
Date: Thu, 6 Nov 2014 09:01:40 -0800
Message-ID: 
 <CALte62ywaytwnUsNafd8h+xqSkBC78rRR-=PE==knjGdsbPZ9w@mail.gmail.com>
Subject: Re: key byte pattern
From: Ted Yu <yuzhihong@gmail.com>
To: "user@hbase.apache.org" <user@hbase.apache.org>
Content-Type: multipart/alternative; boundary=089e013c5da6733af6050733a6cb

--089e013c5da6733af6050733a6cb
Content-Type: text/plain; charset=UTF-8

See http://hbase.apache.org/book.html#keysize

Cheers

On Thu, Nov 6, 2014 at 7:05 AM, David Larsen <dlarsen@connexity.com> wrote:

> You could simply take the timestamp as a Long and store it as as a byte
> array.
>
> What's the main advantage you are after with smaller keys?
>
>
> Sent from my Verizon Wireless 4G LTE smartphone
>
>
> -------- Original message --------
> From: Rita
> Date:11/06/2014 4:19 AM (GMT-08:00)
> To: hbase-user@hadoop.apache.org
> Subject: key byte pattern
>
> ATM, i have a key which is a string.
>
> "Z.1415276116.223232"
>
> Are there any algorithms or design patterns I should follow for something
> like this to decrease the key size? Obviously, storing it as a String is
> costly was wondering if there was a better way to store something like
> this?
> BTW, 1415276116.223232 is a epoch second
>
>
>
> --
> --- Get your facts first, then you can distort them as you please.--
>

--089e013c5da6733af6050733a6cb--