[
https://issues.apache.org/jira/browse/HBASE-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-2406.
--------------------------
Resolution: Fixed
I'm resolving this issue. We have unit tests that demo what we have, and now
I've commiitted doc. that describes how hbase currently does versions with a
listing of limitations. Other issues have been opened to address these
limitations (linked off this issue) which I believe cover the concerns raised
in here. Lets open new issues to address holes in the doc. I'm adding or to
add unit tests if not already coverage of how we think versioning is working in
HBase.
> Define semantics of cell timestamps/versions
> --------------------------------------------
>
> Key: HBASE-2406
> URL: https://issues.apache.org/jira/browse/HBASE-2406
> Project: HBase
> Issue Type: Task
> Components: documentation
> Reporter: Todd Lipcon
> Assignee: Pranav Khaitan
> Priority: Critical
> Fix For: 0.90.0
>
> Attachments: 2406.txt, versions.html
>
>
> There is a lot of general confusion over the semantics of the cell timestamp.
> In particular, a couple questions that often come up:
> - If multiple writes to a cell have the same timestamp, are all versions
> maintained or just the last?
> - Is it OK to write cells in a non-increasing timestamp order?
> Let's discuss, figure out what semantics make sense, and then move towards
> (a) documentation, (b) unit tests that prove we have those semantics.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
