[
https://issues.apache.org/jira/browse/HBASE-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12611197#action_12611197
]
Sebastien Rainville commented on HBASE-724:
-------------------------------------------
It's not related to HBASE-702 because in that bug there was a different
behavior in between deleteAll(row) and deleteAll(row, column). In this case,
the different behavior is in between get(), getFull() and the scanners. Also,
chatting with Jim Kellerman he confirmed that the branch 0.1 was not affected
by HBASE-702.
And it's good to know i'm not the only one in Montreal working with hbase :P
> Deleted rows reappear after a HStore.flushCache() and/or
> HStore.compactStores()
> -------------------------------------------------------------------------------
>
> Key: HBASE-724
> URL: https://issues.apache.org/jira/browse/HBASE-724
> Project: Hadoop HBase
> Issue Type: Bug
> Components: regionserver
> Affects Versions: 0.1.3
> Reporter: Sebastien Rainville
> Attachments: testdeleteall.patch
>
>
> When deleting a row, that row seems to be deleted and everything to be normal
> but some time afterwards that row somehow reappears (HTable.get() and
> scanners find it again). Looking at the log files it seems like deleted rows
> reappear after a flush of the memcache or after the compaction...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
