[
https://issues.apache.org/jira/browse/HBASE-10504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13999804#comment-13999804
]
Gabriel Reid commented on HBASE-10504:
--------------------------------------
{quote}I think I don't fully understand why would you want to have a proxy
layer as a separate service (other than isolation issues).{quote}
Process isolation and deployment isolation are indeed the two main issues. The
process isolation side of things probably speaks for itself. Deployment
isolation is another issue however. Keeping dependencies of hbase-indexer in
line with all deps in hbase is an issue (as all hbase-indexer jars would need
to be deployed into the HBase lib for this approach to work), and all
configuration, config changes, and restarting would also become directly linked
to HBase.
> 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
>
> Attachments: 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.2#6252)
