[
https://issues.apache.org/jira/browse/HBASE-10504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16137649#comment-16137649
]
stack edited comment on HBASE-10504 at 8/23/17 5:22 AM:
--------------------------------------------------------
What we going to do here? ReplicationEndpoint is broken in hbase-2.0 so if we
want to mess with Replication Interfaces, now is the time.
[~gabriel.reid] if you are listening or [~whoschek], looking at the SEP
implementation, it is broke for hbase2. The use of internal Admin protocols and
expectation that our protobuf is at com.google.protobuf no longer holds. Lets
figure this out lads.
was (Author: stack):
What we going to do here? ReplicationEndpoint is broken in hbase-2.0 so if we
want to mess with Replication Interfaces, now is the time.
> Define Replication Interface
> ----------------------------
>
> Key: HBASE-10504
> URL: https://issues.apache.org/jira/browse/HBASE-10504
> Project: HBase
> Issue Type: Task
> Components: Replication
> Reporter: stack
> Assignee: Enis Soztutar
> Priority: Blocker
> Fix For: 2.0.0-alpha-3
>
> 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.4.14#64029)
