+1
Best regards,
- Andy
On Mar 22, 2012, at 9:24 AM, lars hofhansl <[email protected]> wrote:
> +1
> That seems like a hole in the coprocessor framework that we missed when we
> did added the rollback logic.
>
>
>
> ________________________________
> From: Ramkrishna.S.Vasudevan <[email protected]>
> To: [email protected]
> Cc: 'rama krishna' <[email protected]>
> Sent: Thursday, March 22, 2012 7:59 AM
> Subject: Providing coprocessor hooks in rollbackMemStore while doing puts
>
> 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.
>
> Can we add hooks like preRollbackMemstore and postRollBackMemstore so that I
> will be atleast able to rollback the entries?
>
> Can we raise a JIRA for solving this.
