[
https://issues.apache.org/jira/browse/HBASE-22623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16901629#comment-16901629
]
Duo Zhang commented on HBASE-22623:
-----------------------------------
For example, we will write some marker edits to WAL, and it will be used in
many places. If in the CP you delete it or overwrite it with other values, the
logic in HBase itself will be broken and cause unexpected behavior. That's what
we say 'messed up'. The upper level coprocessors can only effect user related
data, for example you can add more puts or deletes into a batch, but it will
not effect the internal things. And if you find other things which will break
the logic of HBase, please tell me, I will file issues to remove the CP methods.
Thanks.
> Add RegionObserver coprocessor hook for preWALAppend
> ----------------------------------------------------
>
> Key: HBASE-22623
> URL: https://issues.apache.org/jira/browse/HBASE-22623
> Project: HBase
> Issue Type: New Feature
> Reporter: Geoffrey Jacoby
> Assignee: Geoffrey Jacoby
> Priority: Major
> Fix For: 3.0.0, 1.5.0, 2.3.0
>
>
> While many coprocessor hooks expose the WALEdit to implementing coprocs,
> there aren't any that expose the WALKey before it's created and added to the
> WALEntry.
> It's sometimes useful for coprocessors to be able to edit the WALKey, for
> example to add extended attributes using the fields to be added in
> HBASE-22622.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
