[
https://issues.apache.org/jira/browse/HBASE-10504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13902005#comment-13902005
]
Gabriel Reid commented on HBASE-10504:
--------------------------------------
Making the NRT listening of changes on HBase into a first-class API as
[~toffer] suggested sounds like an interesting idea, if there's interest in
going that far in actively supporting this use case.
If there is interest in doing that, the current hbase-sep library (which is the
current library used for latching in via replication and responding to changes
for the hbase-indexer project) could be a possible starting point. The current
API interfaces[1] as well as the impl are within sub-modules[2] of the
hbase-indexer project on GitHub.
[1]
https://github.com/NGDATA/hbase-indexer/tree/master/hbase-sep/hbase-sep-api/src/main/java/com/ngdata/sep
[2] https://github.com/NGDATA/hbase-indexer/tree/master/hbase-sep
> 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)
