[
https://issues.apache.org/jira/browse/HBASE-11367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14033280#comment-14033280
]
Hadoop QA commented on HBASE-11367:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12650696/hbase-11367_v1.patch
against trunk revision .
ATTACHMENT ID: 12650696
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 15 new
or modified tests.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/9782//console
This message is automatically generated.
> Pluggable replication endpoint
> ------------------------------
>
> Key: HBASE-11367
> URL: https://issues.apache.org/jira/browse/HBASE-11367
> Project: HBase
> Issue Type: Sub-task
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
> Priority: Blocker
> Fix For: 0.99.0
>
> Attachments: hbase-11367_v1.patch
>
>
> We need a pluggable endpoint for replication for more flexibility. See parent
> jira for more context.
> ReplicationSource tails the logs for each peer. This jira introduces
> ReplicationEndpoint which is customizable per peer. ReplicationEndpoint is
> run in the same RS process and instantiated per replication peer per region
> server. Implementations of this interface handle the actual shipping of WAL
> edits to the remote cluster.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
