[jira] [Updated] (HBASE-10504) Define Replication Interface

["Enis Soztutar (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HBASE-10504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Enis Soztutar updated HBASE-10504:
----------------------------------

    Attachment: hbase-10504_v1.patch

Attaching the first version patch as an inclusion candidate. Would be good to have this in 1.0. 

Patch adds a new plugin point ReplicationEndpoint. ReplicationSource tails the log, ReplicationEndpoint implementations are responsible for actually shipping the edits to the other (hbase or non-hbase) cluster. 

ReplicationEndpoint can be defined per peer. Default inter-cluster replication works without any changes (lily etc should still work). 

RB here: 
https://reviews.apache.org/r/22490/


> Define Replication Interface
> ----------------------------
>
>                 Key: HBASE-10504
>                 URL: https://issues.apache.org/jira/browse/HBASE-10504
>             Project: HBase
>          Issue Type: Task
>            Reporter: stack
>            Assignee: stack
>            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)