[
https://issues.apache.org/jira/browse/HBASE-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-2406:
-------------------------
Attachment: 2406.txt
versions.html
Here is a section on hbase versions based on Bruno's article w/ some updates
and a bit of preamble on what hbase versions are about.
As per Brunos' article, it explains how timestamping works for get, scan, put,
and delete. It has a section on limitiations. It also explicitly answers the
questions that todd raises at head of this issue.
While I was at it, I added some docbook config. up in the pom and also removed
the sample illustrative article I'd added to show how we could do articles only
in docbook.
I also added a 'quick start' section at head of the book as well as other clean
up.
> 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.