There are two ways to use HBase. One is as part of a map reduce program. The other is as a NoSQL data store.
If you are writing a m/r job, you really don't want to create any DAO layer or even think about a JPA layer. Sorry but the access API is too simple to require any JPA and you're not writing to multiple data sources so you really don't want to do any abstraction...
Keep It Simple.
If you are writing an app to access HBase outside of a map reduce job, most of the same arguments apply. HBase access patterns are too simple to require any abstraction.
YMMV, so take what I say with a grain of salt.
Sent from a remote device. Please excuse any typos...
On Oct 14, 2011, at 3:54 PM, Christian Schäfer <[EMAIL PROTECTED]> wrote:
> Hi St.Ack
> yes I'm currently using Data Nucleus...and thought I missed that there is a JDBC-Driver
> Von: Stack <[EMAIL PROTECTED]>
> An: [EMAIL PROTECTED]; Christian Schäfer <[EMAIL PROTECTED]>
> Gesendet: 18:35 Freitag, 14.Oktober 2011
> Betreff: Re: Persist to HBase with JPA using HBql-JDBC-Driver (Examples)?
> On Fri, Oct 14, 2011 at 1:26 PM, Christian Schäfer <[EMAIL PROTECTED]> wrote:
>> just saw that there is a JDBC-Driver for HBase.
>> So I wonder if it's possible to persist to HBase via JPA using that JDBC-Driver?
>> For now I still saw in the examples that there are Annotations included in HBql what seems not so far away from JPA-Annotations.
>> JPA-HBql-. Examples (I didnt find any) would be welcome :-)
> I think you might need to temper your expectation a little. I think
> that jdbc driver is for hbql -- least thats what it understands.
> Then I'm not sure of the state of hbql.
> The above seems a little dodgy to be building a jpa bridge upon? If
> you google jpa and hbase there seem to be a few possibilities
> (datanucleus for one).