[ https://issues.apache.org/jira/browse/HBASE-5617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13240981#comment-13240981 ]
Anoop Sam John commented on HBASE-5617: --------------------------------------- {quote} Do we need two hooks for memstore rollback ? {quote} +1 for pre and post... As per the use case one can use pre or post hook... > Provide coprocessor hooks in put flow while rollbackMemstore. > ------------------------------------------------------------- > > Key: HBASE-5617 > URL: https://issues.apache.org/jira/browse/HBASE-5617 > Project: HBase > Issue Type: Improvement > Components: coprocessors > Reporter: ramkrishna.s.vasudevan > Assignee: ramkrishna.s.vasudevan > Fix For: 0.96.0 > > Attachments: HBASE-5617_1.patch > > > With coprocessors hooks while put happens we have the provision to create new > puts to other tables or regions. These puts can be done with writeToWal as > false. > In 0.94 and above the puts are first written to memstore and then to WAL. If > any failure in the WAL append or sync the memstore is rollbacked. > Now the problem is that if the put that happens in the main flow fails there > is no way to rollback the > puts that happened in the prePut. > We can add coprocessor hooks to like pre/postRoolBackMemStore. Is any one > hook enough here? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira