[
https://issues.apache.org/jira/browse/HBASE-22623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16903241#comment-16903241
]
Andrew Purtell commented on HBASE-22623:
----------------------------------------
Just to be clear because I used the word "hostile" which can have negative
connotations - I don't mean it in a negative way. An opinion that we should
have more and more coprocessor interfaces to address new use cases is valid. An
opinion that coprocessors are too invasive and should be 'cleaned up' is also
valid. An opinion that the compatibility headaches of coprocessor interfaces
are annoying is valid. An opinion that Phoenix can be considered as a valid use
case when considering interface changes is valid. An opinion that only HBase
level concerns should motivate API changes is valid. These opinions are
strawmen. I think they approach actual positions in the community but I do not
imply any specific person has one of them. These strawmen are at least
partially contradictory. It is going to be an ongoing process to sort them out
into something that makes sense and can get consensus.
> 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)
