Return-Path: Delivered-To: apmail-hadoop-hbase-user-archive@minotaur.apache.org Received: (qmail 84184 invoked from network); 10 Nov 2009 22:45:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 10 Nov 2009 22:45:23 -0000 Received: (qmail 12554 invoked by uid 500); 10 Nov 2009 22:45:22 -0000 Delivered-To: apmail-hadoop-hbase-user-archive@hadoop.apache.org Received: (qmail 12505 invoked by uid 500); 10 Nov 2009 22:45:22 -0000 Mailing-List: contact hbase-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hbase-user@hadoop.apache.org Delivered-To: mailing list hbase-user@hadoop.apache.org Received: (qmail 12495 invoked by uid 99); 10 Nov 2009 22:45:22 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Nov 2009 22:45:22 +0000 X-ASF-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of clint.a.m@gmail.com designates 209.85.210.194 as permitted sender) Received: from [209.85.210.194] (HELO mail-yx0-f194.google.com) (209.85.210.194) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Nov 2009 22:45:20 +0000 Received: by yxe32 with SMTP id 32so519874yxe.5 for ; Tue, 10 Nov 2009 14:44:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=bKOidDaLfarmTMMqfK8tKQIS1QVqGSLwSg+Q5S7i1Es=; b=hYmQu5nyoeVIK4RDnmF8eKnFBov+zNsHZqFuIGrquv8A4okcg3CwoY90TRrIMSJRDg FszCHQhbC+6Id7JcMQX+EOyIkJw8C755kNjiJ9rRz6fY3ONsFNZiOnbvlK1wK2HrXlCp /8DtanOVMc4TmfDQqDMXFcvpdgeSzMbsvDR94= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=Uss7rgx8pwN69nZ2NIjVE+lx5R+Zuy0Qs8bhqWCs+Mbj/DRxHKMxZMFXCPkjRqw2uv wTGPyRwNk4BScqmfKDLYOzESd/I9Ynf/mjhef0Y2WxMqofseOMi6tAp2yq7jxjD2U3MM 7w8JjA7gIWqz5LZNvRIwhIYciztiD3X5ADr4o= MIME-Version: 1.0 Sender: clint.a.m@gmail.com Received: by 10.101.115.4 with SMTP id s4mr1057899anm.81.1257893099339; Tue, 10 Nov 2009 14:44:59 -0800 (PST) In-Reply-To: <7c962aed0911101300j58ba7699je5c16eb56d103cca@mail.gmail.com> References: <7c962aed0911101300j58ba7699je5c16eb56d103cca@mail.gmail.com> Date: Tue, 10 Nov 2009 14:44:59 -0800 X-Google-Sender-Auth: b07bf21082ffd2dc Message-ID: Subject: Re: Multiple puts with same timestamp From: Clint Morgan To: hbase-user@hadoop.apache.org Content-Type: multipart/alternative; boundary=001636ed6d4359ff8204780c0ff7 --001636ed6d4359ff8204780c0ff7 Content-Type: text/plain; charset=ISO-8859-1 Yep, thanks for the pointer. On Tue, Nov 10, 2009 at 1:00 PM, stack wrote: > See HBASE-1485. Is this what you are asking about? > St.Ack > > On Tue, Nov 10, 2009 at 10:41 AM, Clint Morgan >wrote: > > > I have a couple questions about behavior of Puts with the same > timestamps: > > > > If I do two puts with LATEST timestamp, and they both get added with the > > same value for now, will the last put be the visible one? > > > > > > > If I do two puts with the same manual timestamp, will the last put be the > > visible one? > > > > I'll investigate this latter, but was wondering if someone already had an > > idea about how it works now. And how it should work.. > > > > cheers, > > -clint > > > --001636ed6d4359ff8204780c0ff7--