[
https://issues.apache.org/jira/browse/HBASE-10648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13925003#comment-13925003
]
stack commented on HBASE-10648:
-------------------------------
All of the above is good by me Anoop including the bit about more than one
snapshot. Yeah, current implementation only allows one. I was thinking of an
implementation that might carry N ... but this fact can be contained inside the
actual implementation. It does not need to escape. In fact, it could be
argued that this 'snapshotting' is an implementation detail of the default
memstore and it should really be more generic... prepareForFlush instead of
snapshot but.... we can do this in later issues. Important thing is make what
we have is pluggable. When you start to do the second implementation, you will
have a better idea of what changes are needed in the Interface.
> Pluggable Memstore
> ------------------
>
> Key: HBASE-10648
> URL: https://issues.apache.org/jira/browse/HBASE-10648
> Project: HBase
> Issue Type: Sub-task
> Reporter: Anoop Sam John
> Assignee: Anoop Sam John
> Attachments: HBASE-10648.patch, HBASE-10648_V2.patch,
> HBASE-10648_V3.patch
>
>
> Make Memstore into an interface implementation. Also make it pluggable by
> configuring the FQCN of the impl.
> This will allow us to have different impl and optimizations in the Memstore
> DataStructure and the upper layers untouched.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
