[
https://issues.apache.org/jira/browse/HBASE-18824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167392#comment-16167392
]
Chia-Ping Tsai commented on HBASE-18824:
----------------------------------------
The HConstants.LATEST_TIMESTAMP(Long.MAX_VALUE) is a *notation*. Any PUT cell
having the *notation* will be replaced it's timestamp with server's
{{currentTimeMillis}}. If you change the description from {{currentTimeMillis}}
to {{Long.MAX_VALUE}}, that may confuse user because the timestamp of cell we
store is server's {{currentTimeMillis}}.
> Default timestamp for Put and Delete is not System.currentTimeMillis(), but
> Long.MAX_VALUE
> ------------------------------------------------------------------------------------------
>
> Key: HBASE-18824
> URL: https://issues.apache.org/jira/browse/HBASE-18824
> Project: HBase
> Issue Type: Bug
> Components: documentation
> Reporter: Xiang Li
> Assignee: Xiang Li
> Priority: Minor
> Attachments: HBASE-18824.master.000.patch
>
>
> In http://hbase.apache.org/book.html#versions,
> 1. In chapter 27.2.4 Put
> bq. Doing a put always creates a new version of a cell, at a certain
> timestamp. {color:#205081}By default the system uses the server’s
> currentTimeMillis{color}, ...
> 2. In chapter 27.2.5 Delete
> bq. Deletes work by creating tombstone markers. For example, let’s suppose we
> want to delete a row. For this you can specify a version, or else
> {color:#205081}by default the currentTimeMillis is used.{color}...
> Checking the code, when timestamp is not specified,
> HConstants.LATEST_TIMESTAMP is used, which is Long.MAX_VALUE, rather than
> System.currentTimeMillis()
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
