hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bruno Dumon (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-2406) Define semantics of cell timestamps/versions
Date Tue, 20 Jul 2010 08:09:51 GMT

    [ https://issues.apache.org/jira/browse/HBASE-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12890210#action_12890210
] 

Bruno Dumon commented on HBASE-2406:
------------------------------------

bq. I commented on this on the blog post. This is not the case, we do support this by setting
max to be the timestamp+1

My problem there was not the 'less than or equal' but rather getting the most recent version
at some past point-in-time. I now (finally) understand this can be achieved by setting the
range from 0 to the desired timestamp and max versions to 1. I'll update the blog to reflect
this.

Concerning resurfacing puts: I do not see this as a problem, just as an interesting effect
of how things work.

> 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
>            Priority: Critical
>             Fix For: 0.90.0
>
>
> 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.


Mime
View raw message