From 5672fbcbfa82032a320ce7105ffcfed89d96dda4 Mon Sep 17 00:00:00 2001 From: Xiang Li Date: Tue, 19 Sep 2017 23:10:31 +0800 Subject: [PATCH] HBASE-18824 Add meaningful comment to HConstants.LATEST_TIMESTAMP to explain why it is MAX_VALUE --- hbase-common/src/main/java/org/apache/hadoop/hbase/HConstants.java | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/hbase-common/src/main/java/org/apache/hadoop/hbase/HConstants.java b/hbase-common/src/main/java/org/apache/hadoop/hbase/HConstants.java index 7577644d32..da76815214 100644 --- a/hbase-common/src/main/java/org/apache/hadoop/hbase/HConstants.java +++ b/hbase-common/src/main/java/org/apache/hadoop/hbase/HConstants.java @@ -549,8 +549,11 @@ public final class HConstants { /** * Timestamp to use when we want to refer to the latest cell. - * This is the timestamp sent by clients when no timestamp is specified on - * commit. + * + * On client side, this is the timestamp set by default when no timestamp is specified. + * On server side, this acts as a notation. The timestamp of Put cell having the notation will be replaced with + * server's current time. + * So that is why it is named as "latest" but assigned as Long's max value. */ public static final long LATEST_TIMESTAMP = Long.MAX_VALUE; -- 2.14.1