accumulo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Keith Turner <>
Subject Re: Suggestions on modeling a composite row key
Date Wed, 27 Feb 2013 15:50:19 GMT
On Wed, Feb 27, 2013 at 3:03 AM, Christopher <> wrote:
> Check out Typo:
> What you're describing is the motivation for that little utility API.

Also, you do not have to use the Typo API.  You could use the
Lexicoders that you need inorder to encode things so that they sort
properly lexicographically.

> Alternatively, if you don't care about the overhead costs or human
> readability, you could use a modified base64 encoding of your binary
> key components that preserves the ordering (such as
> which I found with
> Google just now), encode them individually, and join them using a
> delimiter of your choosing (so long as your delimiter is
> lexicographically ordered prior to all the bytes in the output bytes
> of your order-preserving encoding).
> --
> Christopher L Tubbs II
> On Tue, Feb 26, 2013 at 8:51 PM, Mike Hugo <> wrote:
>> I need to build up a row key that consists of two parts, the first being a
>> URL (e.g. 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

View raw message