[
https://issues.apache.org/jira/browse/HBASE-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12611147#action_12611147
]
Jean-Daniel Cryans commented on HBASE-724:
------------------------------------------
This seems related to HBASE-702.
{quote}
get() returns the cells in the order that it finds it... how can it be working?
i.e. how does the cells are returned in chronological order? I must just not
understand the algorithm but let's say there are multiple versions of the same
cell spanned in several mapfiles... all the mapfiles are read sequentially so
what garanties that the versions will be found in chronological order? are the
mapfiles somehow read in chronological order? and within a mapfile, are the
versions of a cell in chronological order as well?
{quote}
The rows are stored and sorted by their HStoreKey which is row+timestamp,
FYI. this kind of question belongs to the mailing list or you can also drop by
on IRC, it wil be nice to chat with someone else from Montreal ;)
> 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.
