[
https://issues.apache.org/jira/browse/HBASE-10504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13898543#comment-13898543
]
Patrick Hunt commented on HBASE-10504:
--------------------------------------
My 0.02. Being able to receive notifications in NRT when things change in HBase
is useful. Having a stable API for this would be great. The hbase-indexer
service that [~stack] linked to in the description does indeed use the
replication API to get notifications and update a Solr/Lucene based index, this
provides an NRT secondary index(es) of sorts on HBase. In our case (indexer) we
are using the interface to be notified of changes in real time, which then
update the index immediately. This has worked extremely well (reliable, secure,
allows filtering, etc...), however we have hit issues with the fact that the
interface is private. Each release tends to have some changes to this interface
(or it's supporting code) that impacts the indexer. We get around this by
updating the code, but it's non-optimal. It would be great if this interface
could be made public/stable.
> 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)
