[
https://issues.apache.org/jira/browse/HBASE-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13631791#comment-13631791
]
Himanshu Vashishtha commented on HBASE-4210:
--------------------------------------------
An end user should be aware that there are two places in the flow where
Pre/Post hooks are called in this flow. He should write his Observers keeping
that in mind.
So, this is how it looks now:
1) Pre Puts/Deletes
1.1) Take updateLock.readLock()
2) PreBatchMutate
3) Memstore, Wal, sync, mvcc.
4) PostBatchMutate
4.1) Release updateLock.readLock()
5) Post Puts/Deletes
Why do you need the readLock while calling pre/postBatchMutateXXX? Is it
necessary?
> Allow coprocessor to interact with batches per region sent from a client
> ------------------------------------------------------------------------
>
> Key: HBASE-4210
> URL: https://issues.apache.org/jira/browse/HBASE-4210
> Project: HBase
> Issue Type: New Feature
> Affects Versions: 0.94.6, 0.95.0
> Reporter: Lars Hofhansl
> Assignee: Anoop Sam John
> Fix For: 0.98.0, 0.94.6, 0.95.0
>
> Attachments: 4210_Trunk-V3.patch, HBASE-4210_94.patch,
> HBASE-4210_94-V2.patch, HBASE-4210_94-V3.patch, HBASE-4210_94-V4.patch,
> HBASE-4210_94-V5.patch, hbase-4210-addendum.patch, HBASE-4210_Trunk.patch,
> HBASE-4210_Trunk-V2.patch, HBASE-4210_Trunk-V3.patch
>
>
> Currently the coprocessor write hooks - {pre|post}{Put|Delete} - are strictly
> one row|cell operations.
> It might be a good idea to allow a coprocessor to deal with batches of puts
> and deletes as they arrive from the client.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
