[
https://issues.apache.org/jira/browse/HBASE-10162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13848174#comment-13848174
]
Anoop Sam John commented on HBASE-10162:
----------------------------------------
Agree with you Gary.. Being a CP writer, this is my concern too.. Knowing that
much internal!!
Yes what ever you mentioned is the best way (as of now) I can also think
about.. Any other suggestions are most welcome.
> Add RegionObserver lifecycle hook to be called when region is available
> -----------------------------------------------------------------------
>
> Key: HBASE-10162
> URL: https://issues.apache.org/jira/browse/HBASE-10162
> Project: HBase
> Issue Type: Improvement
> Components: Coprocessors
> Reporter: Gary Helmling
>
> Over in HBASE-10161 and HBASE-10148, there is discussion of the need to
> modify existing coprocessors, which previously performed initialization only
> in postOpen(), in order to account for the new log replay mechanism happening
> post open.
> This points out that we have a hole in coprocessor lifecycle management which
> caused the use of region lifecycle hooks (postOpen()) in the first place.
> Instead of requiring coprocessor authors to hook into region lifecycle
> methods for initialization, we should provide an explicit lifecycle hook for
> coprocessor authors to use when region open, log replay, and any future
> requirements are complete, say initializeWhenAvailable() (open to better
> names).
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
