[
https://issues.apache.org/jira/browse/HBASE-8086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13600861#comment-13600861
]
Raymond Liu commented on HBASE-8086:
------------------------------------
hmm, I don't know what is the design idea of what major compact's should do.
From my point of view, major compaction should include the flush process. If
not at API level, at least at shell level. Or as you mentioned before. A
parameter to config it?
> 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
