Return-Path: X-Original-To: apmail-accumulo-user-archive@www.apache.org Delivered-To: apmail-accumulo-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 D9719EFC6 for ; Wed, 27 Feb 2013 04:52:15 +0000 (UTC) Received: (qmail 54299 invoked by uid 500); 27 Feb 2013 04:52:15 -0000 Delivered-To: apmail-accumulo-user-archive@accumulo.apache.org Received: (qmail 53686 invoked by uid 500); 27 Feb 2013 04:52:14 -0000 Mailing-List: contact user-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@accumulo.apache.org Delivered-To: mailing list user@accumulo.apache.org Received: (qmail 53567 invoked by uid 99); 27 Feb 2013 04:52:14 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Feb 2013 04:52:14 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.212.50] (HELO mail-vb0-f50.google.com) (209.85.212.50) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Feb 2013 04:52:07 +0000 Received: by mail-vb0-f50.google.com with SMTP id ft2so12092vbb.37 for ; Tue, 26 Feb 2013 20:51:46 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type:x-gm-message-state; bh=S7DnAjtj/qVBgNmvVI7m38/W2JercjIQZGeYlgaKOMo=; b=P6Bo552RFl9VMt6F5uRs84kDICtUuoCog06M0UccjH8wNZGflRBnO+hmNRIYiuZ9C6 Z8hDrg2BBzH42Eg0kTdpOIkac1mw+056NAE3PBpFY0BC39Znw6ibGcEX7YqyrScDmd3x oQhwWrM/dU9TRc1Uw1wEOmPHc9lEFVF+RrMujXFd/TZs9d652T2/YMVbWmvq++ATu0aP p8HA/eg5dBJ6wRVYiCngGqxgjgtES98iD9dKnoyBUU/ij75YFBhacAO5Vs+sRyECNVjK MiC2hMbUAN0QjKb0lvMR34r2tf4vzLtQcWB1+zwsPVO41Q9fTjBYmLLJSzo76dUwx1fr pqmQ== X-Received: by 10.52.66.41 with SMTP id c9mr316187vdt.32.1361940706707; Tue, 26 Feb 2013 20:51:46 -0800 (PST) MIME-Version: 1.0 Received: by 10.220.208.79 with HTTP; Tue, 26 Feb 2013 20:51:26 -0800 (PST) From: Mike Hugo Date: Tue, 26 Feb 2013 22:51:26 -0600 Message-ID: Subject: Suggestions on modeling a composite row key To: user@accumulo.apache.org Content-Type: multipart/alternative; boundary=20cf3071ca9c07957304d6ad880c X-Gm-Message-State: ALoCoQmTCmfs1xyxlnWiW7vbOfsnkS174RSXrT2WxEn48n4c6Vq7DT57a8hC68GmWtFcmKEsKmI1 X-Virus-Checked: Checked by ClamAV on apache.org --20cf3071ca9c07957304d6ad880c Content-Type: text/plain; charset=ISO-8859-1 I need to build up a row key that consists of two parts, the first being a URL (e.g. http://foo.com/dir/page%20name.htm) and the second being a number (e.g. "12"). To date we've been using \u0000 to delimit these two pieces of the key, but that has some headaches associated with it. I'm curious to know how other people have delimited composite row keys. Any best practices or suggestions? Thanks, Mike --20cf3071ca9c07957304d6ad880c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

I need to build up a row key that consists of two parts, t= he first being a URL (e.g. h= ttp://foo.com/dir/page%20name.htm) and the second being a number (e.g. = "12").

To date we've been using=A0\u0000 to delimit these two p= ieces of the key, but that has some headaches associated with it.

I'm curious to know how other people have delimit= ed composite row keys. =A0Any best practices or suggestions?

Thanks,

Mike

--20cf3071ca9c07957304d6ad880c--