Return-Path: 
 <user-return-1846-apmail-accumulo-user-archive=accumulo.apache.org@accumulo.apache.org>
X-Original-To: apmail-accumulo-user-archive@www.apache.org
Delivered-To: apmail-accumulo-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 C441EE14F
	for <apmail-accumulo-user-archive@www.apache.org>;
 Thu, 17 Jan 2013 14:40:26 +0000 (UTC)
Received: (qmail 90634 invoked by uid 500); 17 Jan 2013 14:40:26 -0000
Delivered-To: apmail-accumulo-user-archive@accumulo.apache.org
Received: (qmail 90590 invoked by uid 500); 17 Jan 2013 14:40:26 -0000
Mailing-List: contact user-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@accumulo.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@accumulo.apache.org>
List-Post: <mailto:user@accumulo.apache.org>
List-Id: <user.accumulo.apache.org>
Reply-To: user@accumulo.apache.org
Delivered-To: mailing list user@accumulo.apache.org
Received: (qmail 90575 invoked by uid 99); 17 Jan 2013 14:40:26 -0000
Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Jan 2013 14:40:26 +0000
Received: from localhost (HELO mail-pb0-f46.google.com) (127.0.0.1)
  (smtp-auth username billie, mechanism plain)
  by minotaur.apache.org (qpsmtpd/0.29) with ESMTP;
 Thu, 17 Jan 2013 14:40:25 +0000
Received: by mail-pb0-f46.google.com with SMTP id wy7so1437593pbc.33
        for <user@accumulo.apache.org>; Thu, 17 Jan 2013 06:40:25 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.68.243.69 with SMTP id ww5mr14086328pbc.45.1358433625292;
 Thu, 17 Jan 2013 06:40:25 -0800 (PST)
Received: by 10.68.15.105 with HTTP; Thu, 17 Jan 2013 06:40:25 -0800 (PST)
In-Reply-To: <73780D65-F8DF-4BFF-B816-F4FEAC19CFB3@gmail.com>
References: <73780D65-F8DF-4BFF-B816-F4FEAC19CFB3@gmail.com>
Date: Thu, 17 Jan 2013 06:40:25 -0800
Message-ID: 
 <CAF1jEfDGzOxyCxzsouRYpxL8WG2X3oum8VKeJiwy4XMP+nFbSg@mail.gmail.com>
Subject: Re: Insert and delete row
From: Billie Rinaldi <billie@apache.org>
To: user@accumulo.apache.org
Content-Type: multipart/alternative; boundary=047d7b2e3d0cafc0ea04d37cf979

--047d7b2e3d0cafc0ea04d37cf979
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Jan 17, 2013 at 5:59 AM, Roshan Punnoose <roshanp@gmail.com> wrote:

> We had noticed some interesting behavior in our Accumulo instance. When we
> delete a row and add that exact same row (with the same timestamp) after
> the delete, the row still does not exist. It makes sense because the delete
> really just adds a delete row that tells Accumulo to ignore any row that is
> equal to it. Is there a way to bypass this? Where I could set up my own
> iterator to decide if a row should be deleted or not? (not sure how I would
> decide yet, but just seeing if it is possible to bypass the delete logic as
> is)
>

If you do a full compaction before re-inserting the entry, the deletion
entry will be removed.  I believe compacting a range is also sufficient
(available in newer versions of Accumulo).

Billie



>
> I tried to set up an Iterator in priority=1 to see if I could see a delete
> row, but it did not seem to make it to my iterator.
>
> Any ideas?
>
> Roshan Punnoose
> roshanp@gmail.com
>
>
>
>

--047d7b2e3d0cafc0ea04d37cf979
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Thu, Jan 17, 2013 at 5:59 AM, Roshan Punnoose <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:roshanp@gmail.com" target=3D"_blank">roshanp@gmail.com</a>&gt=
;</span> wrote:<br><div class=3D"gmail_quote"><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
">
We had noticed some interesting behavior in our Accumulo instance. When we =
delete a row and add that exact same row (with the same timestamp) after th=
e delete, the row still does not exist. It makes sense because the delete r=
eally just adds a delete row that tells Accumulo to ignore any row that is =
equal to it. Is there a way to bypass this? Where I could set up my own ite=
rator to decide if a row should be deleted or not? (not sure how I would de=
cide yet, but just seeing if it is possible to bypass the delete logic as i=
s)<br>
</blockquote><div><br>If you do a full compaction before re-inserting the e=
ntry, the deletion entry will be removed.=A0 I believe compacting a range i=
s also sufficient (available in newer versions of Accumulo).<br><br>Billie<=
br>
<br>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex">
<br>
I tried to set up an Iterator in priority=3D1 to see if I could see a delet=
e row, but it did not seem to make it to my iterator.<br>
<br>
Any ideas?<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Roshan Punnoose<br>
<a href=3D"mailto:roshanp@gmail.com">roshanp@gmail.com</a><br>
<br>
<br>
<br>
</font></span></blockquote></div><br>

--047d7b2e3d0cafc0ea04d37cf979--