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 F0498186F9 for ; Sun, 13 Dec 2015 23:30:14 +0000 (UTC) Received: (qmail 50784 invoked by uid 500); 13 Dec 2015 23:30:13 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 50711 invoked by uid 500); 13 Dec 2015 23:30:13 -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 50699 invoked by uid 99); 13 Dec 2015 23:30:12 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 13 Dec 2015 23:30:12 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 679A31A01E0 for ; Sun, 13 Dec 2015 23:30:12 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.879 X-Spam-Level: ** X-Spam-Status: No, score=2.879 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id iejnzn1HOqJ0 for ; Sun, 13 Dec 2015 23:30:11 +0000 (UTC) Received: from mail-qk0-f177.google.com (mail-qk0-f177.google.com [209.85.220.177]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 0868E42989 for ; Sun, 13 Dec 2015 23:30:11 +0000 (UTC) Received: by qkck189 with SMTP id k189so77035690qkc.0 for ; Sun, 13 Dec 2015 15:30:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=nF8GZZMOAwI9q3ALasxOl11A3yh4HEy+evBd7r7Hp+o=; b=k+L44S9a7jbkujueECEc1x6p4MOStW3/xQQ91h2f74XVnCnzbZbEGr33du6R9YILW4 gvKZE9OsKT91KJOtY6h9sj/atS6tdMKFOmoBrMiDPjMnK2DEOs4uqi92u6vHh4gZP2oz x7lBuf8WzDomaJgR/3r3ji09ofJKStTbtWK2iZuapDRDFAdugCHFrMFszyG05rnPuop+ bk8FjHURNi1AZ2FlUsDH6oPcYsBni89HbYcpMWF+JRgY1e3Qx1Vh7PWCsDz67lmNdZ6x n7eekYJWD1NdfjkLJondmcLVDs94tOljSmhZNfQByXwMQ9kB1IICBYIoc4BuKDoBc3QO cmJA== MIME-Version: 1.0 X-Received: by 10.129.90.85 with SMTP id o82mr18100632ywb.97.1450049404416; Sun, 13 Dec 2015 15:30:04 -0800 (PST) Received: by 10.37.56.202 with HTTP; Sun, 13 Dec 2015 15:30:04 -0800 (PST) In-Reply-To: References: Date: Sun, 13 Dec 2015 15:30:04 -0800 Message-ID: Subject: Re: Can a put delete other values? From: Ted Yu To: "user@hbase.apache.org" Content-Type: multipart/alternative; boundary=001a11492426a838790526cfef15 --001a11492426a838790526cfef15 Content-Type: text/plain; charset=UTF-8 The Maximum Number of Versions for a Column Family applies to the row. In your case, subsequent writes cause the max versions to be reached, leading to the behavior you observed. See also http://hbase.apache.org/book.html#specify.number.of.versions Cheers On Sun, Dec 13, 2015 at 2:39 PM, Mike Thomsen wrote: > I think our TTL is whatever is or functionally is "forever." We have a max > of 3 versions on those column families. When I do that put several times > (it's in a Storm topology, so it might get sent a dozen times if another > bolt fails), will that overwrite just the affected cells or affect > everything in the column family or even the entire row? > > Thanks, > > Mike > > On Sun, Dec 13, 2015 at 5:14 PM, Ted Yu wrote: > > > The put for q4, q5, q6 and q7 wouldn't overwrite existing rows. > > > > When were the columns q1 to q3 written ? > > What is the TTL for your table ? > > > > Thanks > > > > On Sun, Dec 13, 2015 at 12:36 PM, Mike Thomsen > > wrote: > > > > > I noticed that our test data set is suddenly missing a lot of data, > and I > > > am wondering if it's because I'm misunderstanding how HBase handles > puts. > > > > > > Suppose we have 3 families: ca, cb and cc. > > > > > > Before on row abcde-fgh-ijkl > > > > > > ca:q1=.... > > > ca:q2=.... > > > ca:q3=.... > > > cb:q1=.... > > > cb:q2=.... > > > cc:q1=.... > > > > > > We send a put that adds q4, q5, q6 and q7. > > > > > > Now the row looks like this: > > > ca:q4=.... > > > ca:q5=.... > > > ca:q6=.... > > > ca:q7=.... > > > > > > I thought a PUT would just add data. It looks like it's overwriting the > > > entire row. > > > > > > --001a11492426a838790526cfef15--