hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8086) Major compact should flush memstore firstly
Date Wed, 13 Mar 2013 05:50:17 GMT

    [ https://issues.apache.org/jira/browse/HBASE-8086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13600854#comment-13600854
] 

stack commented on HBASE-8086:
------------------------------

Indeed they do not.  You can flush the table first and then major compact from the shell but
I think you want the two linked... move on to the major compaction after the flush happens?
                
> Major compact should flush memstore firstly
> -------------------------------------------
>
>                 Key: HBASE-8086
>                 URL: https://issues.apache.org/jira/browse/HBASE-8086
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver
>    Affects Versions: 0.94.5
>            Reporter: Raymond Liu
>            Priority: Minor
>
> From the user point of view, If I want to invoke a major compact manually, What I want
is that all separate file and the memstore is combined into one file. If I don't write anything
new there, from the user point of view, I will assume that it will end up in a single store
file per region. And all the VERSIONS limit etc staffs will be respected. I don't wish it
flush memstore later and create another small store file. At present,it seems to me both major_compact
and compact API and hbase shell cmd don't do memstore flush.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message