[
https://issues.apache.org/jira/browse/HBASE-10504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13898904#comment-13898904
]
Gabriel Reid commented on HBASE-10504:
--------------------------------------
I would echo [~phunt]'s points -- having these interfaces public and stable
would be great.
I think that from the point of view of the hbase-indexer project, the main
contact points that are involved are
o.a.h.h.replication.regionserver.ReplicationSource and o.a.h.h.Server, as well
as the generated AdminProtos, although I assume that the scope of this ticket
will be a fair bit wider than that.
If we're going to move to having a published stable API, now is also probably
the time to make any changes that may be needed. The one thing I can think of
right now that would be nice is a better hook into
o.a.h.h.replication.regionserver.ReplicationSource#removeNonReplicableEdits.
Right now we override that method to do additional filtering on HLog entries
that we know we don't want do send to the indexer, but it would be good to make
that into a public method with some kind of filter interface.
> Define Replication Interface
> ----------------------------
>
> Key: HBASE-10504
> URL: https://issues.apache.org/jira/browse/HBASE-10504
> Project: HBase
> Issue Type: Task
> Reporter: stack
> Assignee: stack
> 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.1.5#6160)
