2009/4/18 stack <[email protected]> > > I don't think it would be too hard adding a generalized system atop hbase > that would allow use of protobuf, json, thrift or avro, etc. The tools are > there to do such a thing, I believe. The column descriptor -- and maybe > even the table descriptor (would need to check) -- can take random key/value > attributes. The serializing layer could write metadata describing libs > used, etc., serializing to the table descriptor and then into column > descriptor column family attributes describing column family specifics.
Do you mean cassandra or voldemort in your original posting? After looking at the voldemort link you posted, in it's case at least, they are just a key/value store so they need to do some fancy-dancing to give illusion of "columns" (The yahoo PNUTs system does similar). I think a system on top of hbase that did the serialization/deserialization from java to something like json with the json schema persisted into the table column descriptor would be a nice hbase addition. Have you looked at any of the hbase ORM objects mentioned up on the wiki? St.Ack
