Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 5F3B9200B51 for ; Mon, 18 Jul 2016 06:37:22 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 5DC92160A7C; Mon, 18 Jul 2016 04:37:22 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id A5E38160A6C for ; Mon, 18 Jul 2016 06:37:21 +0200 (CEST) Received: (qmail 3168 invoked by uid 500); 18 Jul 2016 04:37:20 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 3153 invoked by uid 99); 18 Jul 2016 04:37:20 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Jul 2016 04:37:20 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 81ADC2C0370 for ; Mon, 18 Jul 2016 04:37:20 +0000 (UTC) Date: Mon, 18 Jul 2016 04:37:20 +0000 (UTC) From: "Sai Teja Ranuva (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-16210) Add Timestamp class to the hbase-common and Timestamp type to HTable. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 18 Jul 2016 04:37:22 -0000 [ https://issues.apache.org/jira/browse/HBASE-16210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15381701#comment-15381701 ] Sai Teja Ranuva commented on HBASE-16210: ----------------------------------------- [~stack] Yes, this patch is a part of the parent patch, the code is taken from the parent patch. I guess by making it sub issue I assumed it implicitly. I have added it now. Thank you for pointing it out. Changed a few ideas in the last patch. Did not post it to review board yet, as it is failing hadoop checks, trying to figure it out. Can you also check the patch - HBASE-16210.master.8.1.patch. > Add Timestamp class to the hbase-common and Timestamp type to HTable. > --------------------------------------------------------------------- > > Key: HBASE-16210 > URL: https://issues.apache.org/jira/browse/HBASE-16210 > Project: HBase > Issue Type: Sub-task > Reporter: Sai Teja Ranuva > Assignee: Sai Teja Ranuva > Priority: Minor > Labels: patch, testing > Attachments: HBASE-16210.master.1.patch, HBASE-16210.master.2.patch, HBASE-16210.master.3.patch, HBASE-16210.master.4.patch, HBASE-16210.master.5.patch, HBASE-16210.master.6.patch, HBASE-16210.master.7.patch, HBASE-16210.master.8.1.patch, HBASE-16210.master.8.patch > > > This is a sub-issue of [HBase-14070|https://issues.apache.org/jira/browse/HBASE-14070]. This JIRA is a small step towards completely adding Hybrid Logical Clocks(HLC) to HBase. The main idea of HLC is described in [HBase-14070|https://issues.apache.org/jira/browse/HBASE-14070] along with the motivation of adding it to HBase. > This patch takes the code from part of the patch in the parent which self contained. > The parent patch is pretty big to review at once. So, plan is to get code reviewed in smaller patches and > in the process take suggestions and change things if necessary. > What is this patch/issue about ? > This issue attempts to add a timestamp class to hbase-common and timestamp type to HTable. > This is a part of the attempt to get HLC into HBase. This patch does not interfere with the current working of HBase. > Why Timestamp Class ? > Timestamp class can be as an abstraction to represent time in Hbase in 64 bits. > It is just used for manipulating with the 64 bits of the timestamp and is not concerned about the actual time. > There are three types of timestamps. System time, Custom and HLC. Each one of it has methods to manipulate the 64 bits of timestamp. > HTable changes: Added a timestamp type property to HTable. This will help HBase exist in conjunction with old type of timestamp and also the HLC which will be introduced. The default is set to custom timestamp(current way of usage of timestamp). default unset timestamp is also custom timestamp as it should be so. The default timestamp will be changed to HLC when HLC feature is introduced completely in HBase. > Check HBASE-16210.master.6.patch. > Suggestions are welcome. -- This message was sent by Atlassian JIRA (v6.3.4#6332)