Hi all, Not too long ago their were some discussions related to implementing transactions and/or replication strategies that made use of column versions. I can't remember whether the discussions happened in this forum or in one or more Jira tickets. Regardless, my question is whether there will indeed be a reliance on cell versions to implement either of these features. I ask because currently, the API allows the caller to decide what value is used for the version stamp. It doesn't have to be a timestamp. In fact, some folks have talked about not even using versions as versions, but rather as an additional data dimension.
So my question really boils down to whether HBase would need to restrict the use of versions if versions were indeed used to implement transactions and/or replication. Thanks. -brian
