hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anoop Sam John (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-11920) Interface changes needed for creating CP hooks for ReplicationEndPoint
Date Tue, 09 Sep 2014 17:28:29 GMT

    [ https://issues.apache.org/jira/browse/HBASE-11920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127268#comment-14127268
] 

Anoop Sam John commented on HBASE-11920:
----------------------------------------

We need change in ReplicationEndpoint for this?
CP hook around the creation of the ReplicationEndpoint using conf value would be sufficient?

HRS side
1. pre hook in RegionServerObserver -> This can return an Object of type ReplicationEndpoint.
If not null just use that.
2. Create the ReplicationEndpoint impl object. The class name is specified in conf.
3. post hook in RegionServerObserver -> pass the object created #2. This can return an
Object of type ReplicationEndpoint. If not null use that.

Using this way VC can impl the post hook and create a wrapper impl of ReplicationEndpoint
delegating the calls to the actual impl object.

Will this work out Ram?

> Interface changes needed for creating CP hooks for ReplicationEndPoint
> ----------------------------------------------------------------------
>
>                 Key: HBASE-11920
>                 URL: https://issues.apache.org/jira/browse/HBASE-11920
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Replication, security
>            Reporter: ramkrishna.s.vasudevan
>             Fix For: 2.0.0, 0.98.7, 0.99.1
>
>
> If we want to create internal replication endpoints other than the one created thro configuration
we may need new hooks. This is something like an internal scanner that we create during compaction
so that the actual compaction scanner can be used as a delegator.
> [~enis]
> If I can give a patch by tomorrow will it be possible to include in the RC?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message