You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@hbase.apache.org by 蔡忠达 <10...@qq.com> on 2011/08/29 09:17:38 UTC
hbase-orm
Great that you have thought of doing an ORM for HBase.
recently, our company has a project base on the hbase, and i'am a newcomer, who just graduated from university last June.
for study ,I need the lightweight ORM for Hbase which you had writen.
it is my pleasure to do everything i can do for you， such as write test case for the orm.
thanks.
Re: hbase-orm
Posted by Jean-Daniel Cryans <jd...@apache.org>.
mmm who are you talking to exactly?
J-D
2011/8/29 蔡忠达 <10...@qq.com>:
> Great that you have thought of doing an ORM for HBase.
>
> recently, our company has a project base on the hbase, and i'am a newcomer, who just graduated from university last June.
>
> for study ,I need the lightweight ORM for Hbase which you had writen.
>
> it is my pleasure to do everything i can do for you， such as write test case for the orm.
> thanks.
Re: hbase-orm
Posted by John Hancock <jh...@gmail.com>.
Zhang_xzhi,
In case you did not know, there is also at least one ORM for HBase project
already in existence that you may be interested in.
https://code.google.com/p/kundera/
https://github.com/impetus-opensource/Kundera/wiki/HBase-Specific-Features
If you have questions about Kundera please direct ask them in the Kundera
forum: https://groups.google.com/forum/#!forum/kundera-discuss
-John
On Sun, Jan 5, 2014 at 1:10 PM, Asaf Mesika <as...@gmail.com> wrote:
> One strong storage efficient feature would be to serialize your Pojo to
> binary using Avro (as one example) and saving it as a column. This saves
> you on storage since you don't have to write your row key for every column.
> If you load the entire Pojo it will save on read time. Also it enables to
> support nested fields in your Pojo.
>
>
> On Sunday, January 5, 2014, zhang_xzhi wrote:
>
> > Did u still work on hbase now, I am writing a hbase ORM, would you give
> me
> > some suggestion.
> > Thank.
> >
> > https://github.com/zhang-xzhi/simplehbase
> >
> >
> >
> > --
> > View this message in context:
> >
> http://apache-hbase.679495.n3.nabble.com/hbase-orm-tp4020855p4054489.html
> > Sent from the HBase User mailing list archive at Nabble.com.
> >
>
Re: hbase-orm
Posted by Asaf Mesika <as...@gmail.com>.
One strong storage efficient feature would be to serialize your Pojo to
binary using Avro (as one example) and saving it as a column. This saves
you on storage since you don't have to write your row key for every column.
If you load the entire Pojo it will save on read time. Also it enables to
support nested fields in your Pojo.
On Sunday, January 5, 2014, zhang_xzhi wrote:
> Did u still work on hbase now, I am writing a hbase ORM, would you give me
> some suggestion.
> Thank.
>
> https://github.com/zhang-xzhi/simplehbase
>
>
>
> --
> View this message in context:
> http://apache-hbase.679495.n3.nabble.com/hbase-orm-tp4020855p4054489.html
> Sent from the HBase User mailing list archive at Nabble.com.
>
Re: hbase-orm
Posted by zhang_xzhi <zh...@163.com>.
Did u still work on hbase now, I am writing a hbase ORM, would you give me
some suggestion.
Thank.
https://github.com/zhang-xzhi/simplehbase
--
View this message in context: http://apache-hbase.679495.n3.nabble.com/hbase-orm-tp4020855p4054489.html
Sent from the HBase User mailing list archive at Nabble.com.