Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6B74BE490 for ; Thu, 14 Feb 2013 03:59:16 +0000 (UTC) Received: (qmail 65553 invoked by uid 500); 14 Feb 2013 03:59:14 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 65388 invoked by uid 500); 14 Feb 2013 03:59:13 -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 65339 invoked by uid 99); 14 Feb 2013 03:59:11 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Feb 2013 03:59:11 +0000 X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=FREEMAIL_REPLY,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of yuzhihong@gmail.com designates 209.85.160.173 as permitted sender) Received: from [209.85.160.173] (HELO mail-gh0-f173.google.com) (209.85.160.173) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Feb 2013 03:59:04 +0000 Received: by mail-gh0-f173.google.com with SMTP id g2so1693088ghb.32 for ; Wed, 13 Feb 2013 19:58:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=bThJi58fI+iYQnTlfBriiWoB8tuMYqzQ71t45QYt7pM=; b=bKNWOSepTGjB5RQJ08Ze6y1MqQ6MnUu5MeWbOrO9MBywEHQp12mFpFRAFQzZNSXMUD JAmh887323CWeCdhxPCNJmwHmxkqx3mM1MDlBDy5fKKr0tQkDNxNPc/vslOdJ7zSG7Ch 3U3I2infM+HukN9A7Be9kzeODINe8QMPImmGhnXe0C9fQ2x6ozo7KlLO8Th6oUhk4NwW s4/EPfZ2oBVgLUubKEZYiHcYncQlrYFxgY4Xc9qbnREYjuYEGaJxztGvjBZvo75mNkb8 pU3ZpqlTUpaC51JV1TGn3MTJ4ce/EPoKyAfuYH/eN0NiJU4oDOI93BbQcVpU+fWEsqeR kL1w== MIME-Version: 1.0 X-Received: by 10.236.121.42 with SMTP id q30mr29583977yhh.24.1360814323671; Wed, 13 Feb 2013 19:58:43 -0800 (PST) Received: by 10.100.81.18 with HTTP; Wed, 13 Feb 2013 19:58:43 -0800 (PST) In-Reply-To: <6670454D-5AE4-40BD-A5E2-43FA1D70E33B@gmail.com> References: <1360803001.75692.YahooMailNeo@web140601.mail.bf1.yahoo.com> <6670454D-5AE4-40BD-A5E2-43FA1D70E33B@gmail.com> Date: Wed, 13 Feb 2013 19:58:43 -0800 Message-ID: Subject: Re: RowKey design with hashing From: Ted Yu To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=20cf300e519f5e216e04d5a746c3 X-Virus-Checked: Checked by ClamAV on apache.org --20cf300e519f5e216e04d5a746c3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable My name is Ted, not Lars :-) On Wed, Feb 13, 2013 at 7:41 PM, Mehmet Simsek wr= ote: > Thanks Lars > > M.Nurettin =C5=9Eim=C5=9Fek > > On 14 =C5=9Eub 2013, at 05:18, Ted Yu 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 / prefi= x > > 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 to > >> some blog/doc? How it works, what it is, etc.? > >> > >> Thanks, > >> > >> JM > >> > >> 2013/2/13, lars hofhansl : > >>> 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 pref= ix > >>> block encoding (FAST_DIFF). > >>> > >>> -- Lars > >>> > >>> > >>> > >>> ________________________________ > >>> From: Nurettin =C5=9Eim=C5=9Fek > >>> 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 > >> > --20cf300e519f5e216e04d5a746c3--