accumulo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Josh Elser <josh.el...@gmail.com>
Subject Re: HBase rowkey design guidelines
Date Wed, 04 Dec 2013 16:23:46 GMT
They have a couple of different encoding strategies in HFile v2 that are 
similar.

https://issues.apache.org/jira/browse/HBASE-4218
https://issues.apache.org/jira/browse/HBASE-4676

Not sure if there are any new slated approaches for HFile v3.

On 12/4/13, 12:28 AM, John Vines wrote:
> Also, I'm not sure if HBase has the encoding techniques that we utilize
> in our RFile
>
> On Wed, Dec 4, 2013 at 12:19 AM, Mike Drob <mdrob@mdrob.com
> <mailto:mdrob@mdrob.com>> wrote:
>
>     Well, yes and no.
>
>     Smaller keys still mean less network traffic, potentially less IO,
>     and maybe faster operations if you're trying to do application
>     logic. Using data or default or just d probably doesn't matter in
>     the long term (although there are certainly cases where it might).
>
>     On Dec 3, 2013 11:57 PM, "David Medinets" <david.medinets@gmail.com
>     <mailto:david.medinets@gmail.com>> wrote:
>
>         http://hbase.apache.org/book/rowkey.design.html - unless I am
>         misunderstanding much of the advice given for HBase simply
>         doesn't apply to Accumulo. For example "Try to keep the
>         ColumnFamily names as small as possible, preferably one
>         character (e.g. "d" for data/default)."
>
>

Mime
View raw message