Hi, I have been studying the mysql plugin that keeps a database in synch with a rocketmq topic. The first way that comes to my mind to listen to HBase updates on a table, is by using co-processors (akin to BigTable Observers): https://blogs.apache.org/hbase/entry/coprocessor_introduction With co-processors it is possible to insert hooks for data manipulation events (e.g., put, delete). It is also possible to intercept WAL (Write-Ahead Log that keeps track of updates on a table) writing of events. The co-processors reside on the server side and are distributed automatically alongside HBase region servers. Co-processor custom implementations require modifications in the HBase configuration. By not using co-processors, it would be possible to access directly the WAL on HDFS (in case WAL writing is not disabled).
These are the two main ways (co-processors or accessing WAL directly) I can see to listen to HBase table updates. Using co-processors seems the most natural way to go. For example, implementing a WALObserver and keep track of the last position that was replicated to the rocketmq topic. Do you agree? Thanks! On Mon, Jun 4, 2018 at 7:15 AM, Von Gosling <vongosl...@apache.org> wrote: > Hi, > > I would like to split this topic from AMQP project, we could discuss in > the current thread :-) > > Best Regards, > Von Gosling > > > > 在 2018年6月4日，11:30，Xin Wang <data.xinw...@gmail.com> 写道： > > You can just follow your plan, starting the work for integrating RocketMQ > > >
