You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2009/03/19 21:53:50 UTC
[jira] Commented: (HBASE-1261) Improvements to flushing,
compacting, and splitting
[ https://issues.apache.org/jira/browse/HBASE-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683607#action_12683607 ]
stack commented on HBASE-1261:
------------------------------
I added this issue up here: http://wiki.apache.org/general/SummerOfCode2009
> 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.