accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1800) delete mutations not working through the Proxy
Date Tue, 22 Oct 2013 15:27:41 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-1800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13801913#comment-13801913
] 

Sean Busbey commented on ACCUMULO-1800:
---------------------------------------

For future searchers, [workaround per Eric|http://mail-archives.apache.org/mod_mbox/accumulo-user/201310.mbox/%3CCADxc9BmJzWkt3pyvEv%2BunXethJ%3DEzXkEKvQEm-MT8BZcExmqow%40mail.gmail.com%3E]

bq. If you set the timestamp on your mutation (to the current time in millis) it should work.

> delete mutations not working through the Proxy
> ----------------------------------------------
>
>                 Key: ACCUMULO-1800
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1800
>             Project: Accumulo
>          Issue Type: Bug
>          Components: proxy
>    Affects Versions: 1.4.4, 1.5.0
>            Reporter: Eric Newton
>            Assignee: Eric Newton
>            Priority: Critical
>             Fix For: 1.4.5, 1.5.1
>
>
> Aru Sahni writes:
> {quote}
> 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.
> {quote}
> [~ecn] has confirmed the problem.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message