Hi Alex, Oh no, you do NOT want to use column families that way. The are semi static and should not be changed too often nor should there be too many. Adding a CF requires disabling the table too.
Use columns, row keys or timestamps for that use-case. Lars On Nov 25, 2010, at 17:31, Nanheng Wu <[email protected]> wrote: > Hello, > > I am very new to HBase and I hope to get some feedback from the > community on this: I want to use HBase to store some data with pretty > simple structure: each key has ~50 attributes. These data are computed > daily and loaded into HBase everyday. Almost all of the keys will have > updated values for some attributes, some keys may be delete and some > may be added. What I'd like to have is versioning on the dataset, > HBase will only serve queries using one of the versions and I will > have metadata to keep track of which version should be used. My > question is should I use a ColumnFamily for each version? I would need > to create new ColumnFamilies on every load, and occasionally remove > them if they are too old. Are ColumnFamilies meant to be used this > way? > > Thanks! > Alex
