[
https://issues.apache.org/jira/browse/HBASE-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715178#action_12715178
]
Billy Pearson commented on HBASE-1261:
--------------------------------------
currently with timestamps being provided by the client we can not do #3 in a
minor compaction/merge
the reason is we might delete the wrong version if we are not aware of all
version with all timestamps.
also I thank last time I checked we are doing #2 in minor compaction/merge
> Improvements to flushing, compacting, and splitting
> ---------------------------------------------------
>
> Key: HBASE-1261
> URL: https://issues.apache.org/jira/browse/HBASE-1261
> Project: Hadoop HBase
> Issue Type: Improvement
> Components: documentation, master, regionserver
> Affects Versions: 0.19.0
> Reporter: Evgeny Ryabitskiy
> Assignee: Evgeny Ryabitskiy
>
> This issue concludes my task for GSoC 2009
> The idea is to make all futures from Bigtable paper and other ideas in this
> processes of to flushing, compacting and splitting.
> Some talk in IRC related to this issue creation:
> [22:37] <jgray2> bigtable has an optimization which, when flushing the
> memcache, will actually write out a new storefile that merges the existing
> storefile with the memcache
> [22:37] <jgray2> that way you don't have more than one storefile
> [22:37] <jgray2> which is a huge inefficiency
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
