[
https://issues.apache.org/jira/browse/HBASE-17333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15761854#comment-15761854
]
ramkrishna.s.vasudevan commented on HBASE-17333:
------------------------------------------------
See my description. I was actually not sure on the purpose of that HBASE-17294.
Ya I agree that first we commit the change in such a way that we ensure all
tests pass. Later we make check the bug that occurs due to HBASE-17294 and fix
it up.
And my other request would be that - as part of HBASE-17294 what ever test was
added to work with NONE - should just keep working without adding any change.
That would ensure we are fine with all cases. And it ensures that we have moved
over to Compacting MS.
> HBASE-17294 always ensures CompactingMemstore is default
> --------------------------------------------------------
>
> Key: HBASE-17333
> URL: https://issues.apache.org/jira/browse/HBASE-17333
> Project: HBase
> Issue Type: Bug
> Reporter: ramkrishna.s.vasudevan
> Assignee: ramkrishna.s.vasudevan
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: HBASE-17333.patch, HBASE-17333_1.patch
>
>
> Was the purpose of HBASE-17294 is to make Compacting Memstore as default? Am
> not sure on that. But that patch makes DefaultMemstore as a Noop. This JIRA
> is to discuss and revert back to default memstore only if the family is not
> configured for in memory flush/compaction.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)