hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henning Blohm <henning.bl...@zfabrik.de>
Subject Re: Question on efficient, ordered composite keys
Date Wed, 15 Jan 2014 08:18:20 GMT
Thanks Ted. So in effect it is relevant but there is nothing available 
OOTB.

On 01/14/2014 04:02 PM, Ted Yu wrote:
> Please take a look at HBASE-8089 which is an umbrella JIRA.
> Some of its subtasks are in 0.96
>
> bq. claiming that short keys (as well as short column names) are relevant
> bq. Is that also true in 0.94.x?
>
> That is true in 0.94.x
>
> Cheers
>
>
> On Tue, Jan 14, 2014 at 6:56 AM, Henning Blohm <henning.blohm@zfabrik.de>wrote:
>
>> Hi,
>>
>> for an application still running on Hbase 0.90.4 (but moving to 0.94.6) we
>> are thinking about using more efficient composite row keys compared what we
>> use today (fixed length strings with "/" separator).
>>
>> I ran into http://hbase.apache.org/book/rowkey.design.html claiming that
>> short keys (as well as short column names) are relevant also when using
>> compression (as there is no compression in caches/indices). Is that also
>> true in 0.94.x?
>>
>> If so, is there some support for efficient, correctly ordered, byte[]
>> serialized composite row keys? I ran into HBASE-7221 <
>> https://issues.apache.org/jira/browse/HBASE-7221> and HBASE-7692.
>>
>> For some time it seemed Orderly (https://github.com/ndimiduk/orderly) was
>> suggested but then abandoned again in favor of ... nothing really.
>>
>> So, in short, do you have any favorite / suggested implementation?
>>
>> Thanks,
>> Henning
>>


-- 
Henning Blohm

*ZFabrik Software KG*

T: 	+49 6227 3984255
F: 	+49 6227 3984254
M: 	+49 1781891820

Lammstrasse 2 69190 Walldorf

henning.blohm@zfabrik.de <mailto:henning.blohm@zfabrik.de>
Linkedin <http://www.linkedin.com/pub/henning-blohm/0/7b5/628>
ZFabrik <http://www.zfabrik.de>
Blog <http://www.z2-environment.net/blog>
Z2-Environment <http://www.z2-environment.eu>
Z2 Wiki <http://redmine.z2-environment.net>


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message