[
https://issues.apache.org/jira/browse/ACCUMULO-1800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13801850#comment-13801850
]
ASF subversion and git services commented on ACCUMULO-1800:
-----------------------------------------------------------
Commit ffd16c7adbfd99f7acbba08ad9934acd5c80a7df in branch
refs/heads/1.5.1-SNAPSHOT from [~ecn]
[ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=ffd16c7 ]
ACCUMULO-1800 fix deletes, added test
> 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)
