Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of asaf.mesika@gmail.com
 designates 209.85.214.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAGNSiSYceyzroh7eOY2T1WznBoB5BJC8=ec=LC2fmLSBpQbqxQ@mail.gmail.com>
References: 
 <CAGNSiSYceyzroh7eOY2T1WznBoB5BJC8=ec=LC2fmLSBpQbqxQ@mail.gmail.com>
Date: Tue, 4 Jun 2013 06:57:23 +0300
Message-ID: 
 <CA+r7YvnaWJLZWXR=NsjysqjR4hXbrpTs9nMMNP=gmKdyQ-kUuA@mail.gmail.com>
Subject: Re: Change data capture tool for hbase
From: Asaf Mesika <asaf.mesika@gmail.com>
To: "user@hbase.apache.org" <user@hbase.apache.org>
Content-Type: multipart/alternative; boundary=001a11c2eba023fbe804de4c1429

--001a11c2eba023fbe804de4c1429
Content-Type: text/plain; charset=UTF-8

What's wrong with HBase native Master Slave replicate, or am I missing
something here?


On Mon, Jun 3, 2013 at 12:16 PM, yavuz gokirmak <ygokirmak@gmail.com> wrote:

> Hi all,
>
> Currently we are working on a hbase change data capture (CDC) tool. I want
> to share our ideas and continue development according to your feedback.
>
> As you know CDC tools are used for tracking the data changes and take
> actions according to these changes[1].  For example in relational
> databases, CDC tools are mainly used for replication. You can replicate
> your source system continuously to another location or db using CDC tool.So
> whenever an insert/update/delete is done on the source system, you can
> reflect the same operation to the replicated environment.
>
> As I've said, we are working on a CDC tool that can track changes on a
> hbase table and reflect those changes to any other system in real-time.
>
> What we are trying to implement the tool in a way that he will behave as a
> slave cluster. So if we enable master-master replication in the source
> system, we expect to get all changes and act accordingly. Once the proof of
> concept cdc tool is implemented ( we need one week ) we will convert it to
> a flume source. So using it as a flume source we can direct data changes to
> any destination (sink)
>
> This is just a summary.
> Please write your feedback and comments.
>
> Do you know any tool similar to this proposal?
>
> regards.
>
>
>
>
>
> 1- http://en.wikipedia.org/wiki/Change_data_capture
>

--001a11c2eba023fbe804de4c1429--