Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 12 Jul 2016 22:14:20 +0000 (UTC)
From: "Sai Teja Ranuva (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12988439.1468273403000.8175.1468361660833@Atlassian.JIRA>
In-Reply-To: <JIRA.12988439.1468273403000@Atlassian.JIRA>
References: <JIRA.12988439.1468273403000@Atlassian.JIRA> <JIRA.12988439.1468273403782@arcas>
Subject: [jira] [Comment Edited] (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
archived-at: Tue, 12 Jul 2016 22:14:22 -0000


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

Sai Teja Ranuva edited comment on HBASE-16210 at 7/12/16 10:14 PM:
-------------------------------------------------------------------

HBASE-16210.master.2.patch - removed the setting of timestamp by the Master(This was causing failure of two unit tests at the client) as we are using only one type of timestamp now. But after HLC is introduced and is made the default timestamp type, the master will have to set the timestamp to default(i.e HLC) if not set by user. This will help transitioning to HLC tables for the newly created tables.


was (Author: saitejar):
HBASE-16210.master.2.patch - removed the setting of timestamp by the Master(This was causing failure of two unit tests at the client) as only one type of timestamp is present right now. But after HLC is introduced and is the default timestamp type, the master might have to set the timestamp to default(i.e HLC) if not set by user. This will help transitioning to HLC tables for the newly created tables.

> 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
>
>
> 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. 
> 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.
> Suggestions are welcome. 
> [~enis] - The timestamp class is the one written by you, I have not made any changes. I just changed the default timestamp of the table to Custom. 
> [~jon@cloudera.com], [~stack]


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)