[
https://issues.apache.org/jira/browse/HBASE-17277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15732712#comment-15732712
]
stack commented on HBASE-17277:
-------------------------------
bq. This means normally the alternate BM impl has to extend the existing one
right?
I should change it from private. Will see what implementators want to do
([~jrottinghuis] and [~vrushalic]) first.
bq. Can we allow some sort of a callback impl or when the BM tries and fails to
flush the mutations in buffered? The impl of such a callback can work with the
spooling? We would allow some way to clear off the buffer also then. Just
random thoughts...
Yeah. This sounds like the way to go. AP will change. AP is too complicated.
Exposing a few points of transition seems way to go.
> Allow alternate BufferedMutator implementation
> ----------------------------------------------
>
> Key: HBASE-17277
> URL: https://issues.apache.org/jira/browse/HBASE-17277
> Project: HBase
> Issue Type: Sub-task
> Reporter: stack
> Assignee: stack
> Attachments: HBASE-17277.master.001.patch,
> HBASE-17277.master.002.patch
>
>
> Allow being able to supply alternate BufferedMutator implementation. For
> example, the parent issue would like to spool writes to the filesystem if
> hbase is down.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
