[
https://issues.apache.org/jira/browse/HBASE-10504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14029791#comment-14029791
]
Enis Soztutar commented on HBASE-10504:
---------------------------------------
Thinking a bit more about this, if we want to provide isolation for the
replication services in hbase, we can have a simple host as another daemon
which hosts the ReplicationEndpoint implementation. RS's will use a built-in RE
to send the edits to this layer, and the host will delegate it to the RE
implementation.
The flow would be something like:
RS --> RE inside RS --> Host daemon for RE --> Actual RE implementation -->
third party system
But I am not sure whether we will have this daemon host layer implemented by
1.0.
> Define Replication Interface
> ----------------------------
>
> Key: HBASE-10504
> URL: https://issues.apache.org/jira/browse/HBASE-10504
> Project: HBase
> Issue Type: Task
> Reporter: stack
> Assignee: Enis Soztutar
> Priority: Blocker
> Fix For: 0.99.0
>
> Attachments: hbase-10504_v1.patch, hbase-10504_wip1.patch
>
>
> HBase has replication. Fellas have been hijacking the replication apis to do
> all kinds of perverse stuff like indexing hbase content (hbase-indexer
> https://github.com/NGDATA/hbase-indexer) and our [~toffer] just showed up w/
> overrides that replicate via an alternate channel (over a secure thrift
> channel between dcs over on HBASE-9360). This issue is about surfacing these
> APIs as public with guarantees to downstreamers similar to those we have on
> our public client-facing APIs (and so we don't break them for downstreamers).
> Any input [~phunt] or [~gabriel.reid] or [~toffer]?
> Thanks.
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
