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.
> View this message in context:
> Sent from the HBase User mailing list archive at Nabble.com.