Versioning can be used to see the previous state of a record. Some people need this feature, others don't.
One thing that may be worth a review is this... http://hbase.apache.org/book.html#keysize ... and specifically the fact about all the values being freighted with timestamp (aka version) too. I don't know your use case, and I'm not sure I have the time to understand it, but 1 million versions seems like a lot. You're going to use a lot of space doing that. On 8/17/11 11:53 AM, "Mark" <[email protected]> wrote: >I'm trying to fully understand all the possibilities of what HBase has >to offer but I can determine a valid use case for multiple versions. Can >someone please explain some real life use cases for this? > >Also, at what point is there "too many versions". For example to store >all the queries a user has performed couldn't we create a column family >and have max versions set to something really high (1M). Using this >method we could then ask for the last X amount of queries by setting the >max versions to X. It seems like this can also be accomplished by >creating a separate row for each query but I'm not sure why one strategy >would be better than the other. > >Please help me understand. Thanks!
