Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Plain View
HBase >> mail # user >> RowKey design with hashing


+
Nurettin Şimşek 2013-02-13, 08:35
+
lars hofhansl 2013-02-14, 00:50
+
Jean-Marc Spaggiari 2013-02-14, 02:09
+
Ted Yu 2013-02-14, 03:18
+
Mehmet Simsek 2013-02-14, 03:41
+
Ted Yu 2013-02-14, 03:58
Copy link to this message
-
Re: RowKey design with hashing
Hi Ted,

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

JM

2013/2/13 Ted Yu <[EMAIL PROTECTED]>

> My name is Ted, not Lars :-)
>
> On Wed, Feb 13, 2013 at 7:41 PM, Mehmet Simsek <[EMAIL PROTECTED]
> >wrote:
>
> > Thanks Lars
> >
> > M.Nurettin Şimşek
> >
> > On 14 Şub 2013, at 05:18, Ted Yu <[EMAIL PROTECTED]> 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 <
> > > [EMAIL PROTECTED]> wrote:
> > >
> > >> Hi Lars,
> > >>
> > >> Can you please tell more about key prefix block encoding? Or refer to
> > >> some blog/doc? How it works, what it is, etc.?
> > >>
> > >> Thanks,
> > >>
> > >> JM
> > >>
> > >> 2013/2/13, lars hofhansl <[EMAIL PROTECTED]>:
> > >>> 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 Şimşek <[EMAIL PROTECTED]>
> > >>> To: [EMAIL PROTECTED]
> > >>> 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) [EMAIL PROTECTED]
> > >>> 3) md5 hash([EMAIL PROTECTED])
> > >>> 4) Any other solution.
> > >>>
> > >>> Many thanks.
> > >>>
> > >>> --
> > >>> M. Nurettin ŞİMŞEK
> > >>
> >
>
+
Alexander Ignatov 2013-02-13, 08:40
+
Amit Sela 2013-02-13, 09:01
+
Nurettin Şimşek 2013-02-13, 09:42
+
Jean-Marc Spaggiari 2013-02-13, 12:06
+
Nurettin Şimşek 2013-02-13, 20:03