Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CALte62yDAs63UoL9s5Uritf2uXR_KiRVBYzhZ7wmNf3keS-cXw@mail.gmail.com>
References: 
 <CAB_oDEfYF0v-j5TUw1=1_ay29OEBOWppZpwCW=NBCmcY84vuJw@mail.gmail.com>
 <1360803001.75692.YahooMailNeo@web140601.mail.bf1.yahoo.com>
 <CAPQV63XTfvA5EJofd_FJxjD9y-Aw0A4L6E-gNPupRy2kWLKWGQ@mail.gmail.com>
 <CALte62xxSteY2FhQb+ngb1ab+wSf7qAf2CQFJH45C=eqX_CDDg@mail.gmail.com>
 <6670454D-5AE4-40BD-A5E2-43FA1D70E33B@gmail.com>
 <CALte62yDAs63UoL9s5Uritf2uXR_KiRVBYzhZ7wmNf3keS-cXw@mail.gmail.com>
From: Jean-Marc Spaggiari <jean-marc@spaggiari.org>
Date: Sun, 24 Feb 2013 21:25:56 -0500
Message-ID: 
 <CAPQV63VUMA4AKFmonfiw8FvZ9iGJxv61gdch9H6xQzjBTt7BwQ@mail.gmail.com>
Subject: Re: RowKey design with hashing
To: user@hbase.apache.org
Content-Type: multipart/alternative; boundary=e89a8f234d090105a304d683449a

--e89a8f234d090105a304d683449a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Ted,

Thanks for pointing me to HBASE-4218. I will take a look at it.

JM

2013/2/13 Ted Yu <yuzhihong@gmail.com>

> My name is Ted, not Lars :-)
>
> On Wed, Feb 13, 2013 at 7:41 PM, Mehmet Simsek <nurettinsimsek@gmail.com
> >wrote:
>
> > Thanks Lars
> >
> > M.Nurettin =C5=9Eim=C5=9Fek
> >
> > On 14 =C5=9Eub 2013, at 05:18, Ted Yu <yuzhihong@gmail.com> wrote:
> >
> > > Jean-Marc:
> > > You can find almost all the details you need from this JIRA:
> > > HBASE-4218 Data Block Encoding of KeyValues (aka delta encoding /
> prefix
> > > compression)
> > >
> > > Cheers
> > >
> > > On Wed, Feb 13, 2013 at 6:09 PM, Jean-Marc Spaggiari <
> > > jean-marc@spaggiari.org> wrote:
> > >
> > >> Hi Lars,
> > >>
> > >> Can you please tell more about key prefix block encoding? Or refer t=
o
> > >> some blog/doc? How it works, what it is, etc.?
> > >>
> > >> Thanks,
> > >>
> > >> JM
> > >>
> > >> 2013/2/13, lars hofhansl <larsh@apache.org>:
> > >>> Depends on you search pattern.
> > >>> If you never care about scans ordering i.e. you only do point gets =
to
> > see
> > >>> whether you've already seen an email address, do the hash part.
> > >>>
> > >>> I'd perfer #1 over #2, because it would let you do efficient key
> prefix
> > >>> block encoding (FAST_DIFF).
> > >>>
> > >>> -- Lars
> > >>>
> > >>>
> > >>>
> > >>> ________________________________
> > >>> From: Nurettin =C5=9Eim=C5=9Fek <nurettinsimsek@gmail.com>
> > >>> To: user@hbase.apache.org
> > >>> Sent: Wednesday, February 13, 2013 12:35 AM
> > >>> Subject: RowKey design with hashing
> > >>>
> > >>> Hi All,
> > >>>
> > >>> In our project mail adresses are row key. Which rowkey design  we
> > should
> > >>> choose?
> > >>>
> > >>> 1) com.yahoo@xxxx (Reversed)
> > >>> 2) xxxx@yahoo.com
> > >>> 3) md5 hash(xxxx@yahoo.com)
> > >>> 4) Any other solution.
> > >>>
> > >>> Many thanks.
> > >>>
> > >>> --
> > >>> M. Nurettin =C5=9E=C4=B0M=C5=9EEK
> > >>
> >
>

--e89a8f234d090105a304d683449a--