Return-Path: 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 E88131065E for ; Tue, 22 Oct 2013 15:19:23 +0000 (UTC) Received: (qmail 10057 invoked by uid 500); 22 Oct 2013 15:19:23 -0000 Delivered-To: apmail-accumulo-user-archive@accumulo.apache.org Received: (qmail 9889 invoked by uid 500); 22 Oct 2013 15:19:22 -0000 Mailing-List: contact user-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@accumulo.apache.org Delivered-To: mailing list user@accumulo.apache.org Received: (qmail 9881 invoked by uid 99); 22 Oct 2013 15:19:22 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Oct 2013 15:19:22 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of arusahni@gmail.com designates 209.85.215.172 as permitted sender) Received: from [209.85.215.172] (HELO mail-ea0-f172.google.com) (209.85.215.172) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Oct 2013 15:19:17 +0000 Received: by mail-ea0-f172.google.com with SMTP id r16so4318043ead.3 for ; Tue, 22 Oct 2013 08:18:56 -0700 (PDT) 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=3bYVlfSe+37Rl1Xo2l6Vp9m/JiUEsVkKnSeTFgLae4Q=; b=rWn4ad7y3YEPK80PF/KO9A3TpqC5yaWSDGz7sdY+/YCMyBmQeo337taNLxIK5HxTVh MZZxW6gUj0N/39dpAi0jhXnmxKiD28PVGEOrQHsH4t1ah/3hM1GUphrH1efr0v/ZizIE D/YDbWyt9CBQ37W5+/4wu9LTPFGVOky3fvNbLFBfmwjQ1ISytc/cV45NM2r7S65t9Irf OMDAYh7UE/sBPFi8JKcLhACNZsy+ZuUM5uDSVquvCY0vwE0rLVtqE5RvCoOfqOkjo2j1 xVzRbpTV6d7/Iyuv/abRoTQMHc7b4ZkZLA8TPSQ3nyVoki/Blkp4zTHiWmBJ/7dNlwzb s/TA== MIME-Version: 1.0 X-Received: by 10.14.219.198 with SMTP id m46mr29045978eep.41.1382455135999; Tue, 22 Oct 2013 08:18:55 -0700 (PDT) Received: by 10.14.53.73 with HTTP; Tue, 22 Oct 2013 08:18:55 -0700 (PDT) Received: by 10.14.53.73 with HTTP; Tue, 22 Oct 2013 08:18:55 -0700 (PDT) In-Reply-To: References: Date: Tue, 22 Oct 2013 11:18:55 -0400 Message-ID: Subject: Re: Pyaccumulo deletions From: Aru Sahni To: user@accumulo.apache.org Content-Type: multipart/alternative; boundary=047d7b60399c4c9f8a04e955ebab X-Virus-Checked: Checked by ClamAV on apache.org --047d7b60399c4c9f8a04e955ebab Content-Type: text/plain; charset=ISO-8859-1 Thanks! The timestamp workaround did the trick. On Oct 22, 2013 10:32 AM, "Eric Newton" wrote: > ACCUMULO-1800 has been fixed in the 1.4, 1.5 and master branches. > > -Eric > > On Tue, Oct 22, 2013 at 10:12 AM, Eric Newton > wrote: > > Thanks for the report. I've confirmed the problem and created > ACCUMULO-1800. > > > > If you set the timestamp on your mutation (to the current time in > > millis) it should work. > > > > -Eric > > > > > > On Tue, Oct 22, 2013 at 8:05 AM, Aru Sahni wrote: > >> Hi, > >> > >> I'm new to Accumulo and am still trying to wrap my head around its > ways. To > >> further that challenge, I'm using Pyaccumulo, which doesn't present > much in > >> terms of available reference material. > >> > >> Right now I'm trying to understand how Accumulo manages record > (key-value > >> pair) deletions. > >> > >> conn = Accumulo(host, port, user, password) > >> table = 'test_table' > >> conn.create_table(table) > >> writer = conn.create_batch_writer(table) > >> mut = Mutation('mut_01') > >> mut.put(cf='item', cq='name', value='car') > >> writer.add_mutation(mut) > >> writer.close() > >> conn.close() > >> > >> Will generate a record (found via a shell scan): > >> > >> mut_01 item:name [] car > >> > >> However the subsequent mutation... > >> > >> writer = conn.create_batch_writer(table) > >> mut = Mutation('mut_01') > >> mut.put(cf='item', cq='name', is_delete=True) > >> writer.add_mutation(mut) > >> writer.close() > >> > >> Results in: > >> > >> mut_01 item:name [] > >> > >> How should one expect the deleted row to be represented? That record > sticks > >> around even after I force a compaction of the table. I was expecting > it to > >> not show up in any iterators, or at least provide an easy way to see if > the > >> cell has been deleted. > >> > >> Thanks in advance for the help, > >> ~A > --047d7b60399c4c9f8a04e955ebab Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Thanks! The timestamp workaround did the trick.

On Oct 22, 2013 10:32 AM, "Eric Newton"= ; <eric.newton@gmail.com>= ; wrote:
ACCUMULO-1800 has been fixed in the 1.4, 1.5 and master branches.

-Eric

On Tue, Oct 22, 2013 at 10:12 AM, Eric Newton <eric.newton@gmail.com> wrote:
> Thanks for the report. =A0I've confirmed the problem and created A= CCUMULO-1800.
>
> If you set the timestamp on your mutation (to the current time in
> millis) it should work.
>
> -Eric
>
>
> On Tue, Oct 22, 2013 at 8:05 AM, Aru Sahni <arusahni@gmail.com> wrote:
>> Hi,
>>
>> I'm new to Accumulo and am still trying to wrap my head around= its ways. To
>> further that challenge, I'm using Pyaccumulo, which doesn'= t present much in
>> terms of available reference material.
>>
>> Right now I'm trying to understand how Accumulo manages record= (key-value
>> pair) deletions.
>>
>> conn =3D Accumulo(host, port, user, password)
>> table =3D 'test_table'
>> conn.create_table(table)
>> writer =3D conn.create_batch_writer(table)
>> mut =3D Mutation('mut_01')
>> mut.put(cf=3D'item', cq=3D'name', value=3D'car= ')
>> writer.add_mutation(mut)
>> writer.close()
>> conn.close()
>>
>> Will generate a record (found via a shell scan):
>>
>> mut_01 item:name [] =A0 =A0car
>>
>> However the subsequent mutation...
>>
>> writer =3D conn.create_batch_writer(table)
>> mut =3D Mutation('mut_01')
>> mut.put(cf=3D'item', cq=3D'name', is_delete=3DTrue= )
>> writer.add_mutation(mut)
>> writer.close()
>>
>> Results in:
>>
>> mut_01 item:name []
>>
>> How should one expect the deleted row to be represented? That reco= rd sticks
>> around even after I force a compaction of the table. =A0I was expe= cting it to
>> not show up in any iterators, or at least provide an easy way to s= ee if the
>> cell has been deleted.
>>
>> Thanks in advance for the help,
>> ~A
--047d7b60399c4c9f8a04e955ebab--