Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CB97710837 for ; Wed, 15 Jan 2014 00:18:21 +0000 (UTC) Received: (qmail 2030 invoked by uid 500); 15 Jan 2014 00:18:18 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 1912 invoked by uid 500); 15 Jan 2014 00:18:18 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 1904 invoked by uid 99); 15 Jan 2014 00:18:18 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Jan 2014 00:18:18 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ichhabra@rocketfuelinc.com designates 74.125.245.90 as permitted sender) Received: from [74.125.245.90] (HELO na3sys010aog111.obsmtp.com) (74.125.245.90) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Jan 2014 00:18:11 +0000 Received: from mail-ob0-f172.google.com ([209.85.214.172]) (using TLSv1) by na3sys010aob111.postini.com ([74.125.244.12]) with SMTP ID DSNKUtXTrsAw8ITPfylmXrvQC3yg058Ftf0I@postini.com; Tue, 14 Jan 2014 16:17:51 PST Received: by mail-ob0-f172.google.com with SMTP id vb8so417596obc.3 for ; Tue, 14 Jan 2014 16:17:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rocketfuel.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=xtbhGQSRw8PaII3TPZH+ms3MYqs4wG3CMQGXVfW5j70=; b=AhxQjfA5nPDhLxri2XmDeNB38ibiy15j42obVyxAwN/7qFOzYCVS0gMJnVnPXvE2LB tHCPXKyxYlUgMePvao4oaGlE1RSo7S4QGz0VgqF2akelr2e+lWQ0+6n4oKU4tPJqgErO fXNLrdZheFcM3LcPcmqpyKUJYiATZcd5s1aiE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=xtbhGQSRw8PaII3TPZH+ms3MYqs4wG3CMQGXVfW5j70=; b=Gj7oiLOl5UowCXmNqN3psyHFBtmAabIqg5MERUo6CrE5wEaLdjFhvNnnJOt7aNzbma pzzNch8qGDCWyXRE7YPhEkfnllKLhdDMpjkey5nE4c1dzAmqLhD/dEaJOdiavcQmonE6 5jMqBmAyR86NU7ufII757BkDp/DF/TTWMw4k6KUoMegnf9FKtvA14gbMUr2fUL6KRU4q uVFfgcfzxu+A4ZNSAhC8+xDUk5iWwBD1TUDBAozyBL+rElanEffmPFugmkhKq7wBSA1o WVKi+KyvqBlgse96FcMSqxzcLqvCROwJYIzh0SvSrXuqdlwQVJrqiBWd8kMl74jVgCfz hv8A== X-Gm-Message-State: ALoCoQldMCgdyEopE3lavb+1bgx7yYUF4ZCq+fTyUukFmFGf3y8nyrHe6/qdrTnpXKmwZiksYKGgEiCxj2nN9mx0JPDBPM1nwvUJzi5FT96Y4ZPaCoMLsXR0sjwuhwnAJ7OZNJRDPAt6C8cu0MGWMfAqtNhZ3ZdizFP7BF4bzNMg/IpCC6HpAe4= X-Received: by 10.60.83.17 with SMTP id m17mr3625637oey.62.1389745069625; Tue, 14 Jan 2014 16:17:49 -0800 (PST) X-Received: by 10.60.83.17 with SMTP id m17mr3625630oey.62.1389745069483; Tue, 14 Jan 2014 16:17:49 -0800 (PST) MIME-Version: 1.0 Received: by 10.76.25.229 with HTTP; Tue, 14 Jan 2014 16:17:09 -0800 (PST) In-Reply-To: References: From: Ishan Chhabra Date: Tue, 14 Jan 2014 16:17:09 -0800 Message-ID: Subject: Re: Interaction of SequenceID and timestamps To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=089e011832d431ff6104eff73ddd X-Virus-Checked: Checked by ClamAV on apache.org --089e011832d431ff6104eff73ddd Content-Type: text/plain; charset=ISO-8859-1 Thanks for pointing out the code. My understanding is correct. Thanks! On Tue, Jan 14, 2014 at 3:40 PM, Ted Yu wrote: > Please take a look at the following method in > KeyValueHeap#KVScannerComparator > : > > public int compare(KeyValueScanner left, KeyValueScanner right) { > > Cheers > > > On Tue, Jan 14, 2014 at 3:26 PM, Ishan Chhabra >wrote: > > > I am trying to understand the interaction of sequenceId and timestamps > for > > KVs, and what was the real issue behind > > https://issues.apache.org/jira/browse/HBASE-6590 which says that > bulkload > > can be used only to update only historical data and not current data. > > > > Taking an example: > > > > Lets say I have a KV (r, c, val1, 10), where 10 is the timestamp already > in > > HBase. > > Now, if I bulkload a KV (r, c, val2, 20) without the patch, will that be > > sorted behind the previous KV since the file created has a sequenceID 0, > or > > will it be correctly be the new returned value during a scan for the > (r,c). > > > > I conducted some experiments myself and concluded that timestamp has a > > priority over sequenceId and sequenceId is used to break a tie only when > > the timestamp is the same, but I need to make sure that my understanding > is > > correct. > > > > Thanks! > > > > -- > > *Ishan Chhabra *| Rocket Scientist | RocketFuel Inc. > > > -- *Ishan Chhabra *| Rocket Scientist | RocketFuel Inc. --089e011832d431ff6104eff73ddd--