On Tue, Dec 15, 2009 at 1:03 AM, stack <st...@duboce.net> wrote:
> HBase requires java 6 (1.6) or above.
> St.Ack
>
> On Mon, Dec 14, 2009 at 7:41 PM, Paul Smith <psm...@aconex.com> wrote:
>
>> Just wondering if anyone knows of an existing Hbase utility library that is
>> open sourced that can assist those that have Java5 and above. I'm starting
>> off in Hbase, and thinking it'd be great to have API calls similar to the
>> Google Collections framework. If one doesn't exist, I think I could start
>> off a new project in Google Code (ASL it). I think Hbase is targetted <
>> Java 5, so can't take advantage of this yet internally.
>>
>> The sorts of API functions I thought would be useful to make code more
>> readable would be something like:
>>
>>
>> HTable hTable = new
>> TableBuilder(hbaseConfiguration).withTableName("foo")
>> .withSimpleColumnFamilies("bar", "eek",
>> "moo").deleteAndRecreate();
>>
>> and
>>
>> ResultScanner scanner = new
>> ResultScannerBuilder(hTable).withColumnFamilies(
>> "family1", "family2").build();
>>
>>
>> taking advantage of varargs liberally and using nice Patterns etc. While
>> the Bytes class is useful, I'd personally benefit from an API that can
>> easily pack arbitrary multiple ints (and other data types) together into
>> byte[] for RowKeyGoodness(tm) ala:
>>
>> byte[] rowKey = BytePacker.pack(fooId, barId, eekId, mooId);
>>
>> (behind the scenes this is a vararg method that recursively packs each into
>> into byte[] via Bytes.add(byte[] b1, byte[] b2) etc.
>>
>> If anyone knows of a library that does this, pointers please.
>>
>> cheers,
>>
>> Paul
>
I could see this being very useful. My first barrier to hbase was
trying to figure out how to turn what I knew of as an SQL select cause
into a set of HBaser server side filters. Mostly, I pieced this
together with help from the list, and the Test Cases. That could be
frustrating for some. Now that I am used to it, I notice that the
HBase way is actually much cleaner and much less code.
So, yes a helper library is a great thing.
As part of the "proof of concept" I am working on, large sections of
it are mostly descriptions of doing things like column projections in
both SQL and HBase with filters. So I think both are very helpful for
making Hbase more attractive to an end user.
