[
https://issues.apache.org/jira/browse/HBASE-10504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13963281#comment-13963281
]
Jean-Daniel Cryans commented on HBASE-10504:
--------------------------------------------
bq. It doesn't have to be 'our' RPC, right JD?
Right, I guess I meant RPC protocol instead of mechanism.
bq. You just have to write the znode data in the same format that hbase expects
it to be in
You're right, so we just have to make it explicit. And also you need to be
authenticated if using security.
bq. The above statement makes it appear as though RPC protocol and zk
serialization are more brittle than they actually are.
Sorry, I was referring to the code that I had just linked to where they use our
internal APIs like ServerName and ZKUtil. Considering your two previous
comments, that part of my writeup is irrelevant.
> 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
>
>
> 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)
