Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AE7A1E58E for ; Sun, 3 Mar 2013 03:08:43 +0000 (UTC) Received: (qmail 67984 invoked by uid 500); 3 Mar 2013 03:08:42 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 67780 invoked by uid 500); 3 Mar 2013 03:08:42 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 67761 invoked by uid 99); 3 Mar 2013 03:08:42 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 03 Mar 2013 03:08:42 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of otis.gospodnetic@gmail.com designates 209.85.216.178 as permitted sender) Received: from [209.85.216.178] (HELO mail-qc0-f178.google.com) (209.85.216.178) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 03 Mar 2013 03:08:36 +0000 Received: by mail-qc0-f178.google.com with SMTP id j34so555473qco.37 for ; Sat, 02 Mar 2013 19:08:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=iHMf4LuALAYhvr2KE4ZpMIsOv8fHn4NfycGDEZyoTjo=; b=eX5InJjkbVsPoT7u9p2G69x91Qw8gpPkum0hV2YFtDorfxTcrbvt9QYXOvtDubx+DA 3uIPH3GGSX+FfFjgIfRHTzDiT96Yh6PlekLBC1IkMcCIi0qMs5HIMukc2U6VIOf6zJUz z31p3XvJ9uYSuTtzlfnhGaopijYC5V6mnadDK6YDL94pXB0KgPC9SUPYEfww78ph/X0E CM5/A2/qe8N5wrGzkbT5sHWKSrxNg0V6GDyPykhOPwnbD4bGIqRo2Bjqjstzn/dz3snx xUvI2I4YwJFEgQsFK2PlG2SsjuvcDiWzBrPeFDKE7sowgClRwecdXWLxLWVnjr1YyE3t jBuw== MIME-Version: 1.0 X-Received: by 10.224.222.73 with SMTP id if9mr22754921qab.30.1362280095631; Sat, 02 Mar 2013 19:08:15 -0800 (PST) Received: by 10.224.52.77 with HTTP; Sat, 2 Mar 2013 19:08:15 -0800 (PST) Date: Sat, 2 Mar 2013 22:08:15 -0500 Message-ID: Subject: Publishing HLog entries to a bus? From: Otis Gospodnetic To: dev@hbase.apache.org Content-Type: multipart/alternative; boundary=20cf3074b47c2f4e8504d6fc8d9d X-Virus-Checked: Checked by ClamAV on apache.org --20cf3074b47c2f4e8504d6fc8d9d Content-Type: text/plain; charset=ISO-8859-1 Hi, I was looking at http://engineering.linkedin.com/data-replication/open-sourcing-databus-linkedins-low-latency-change-data-capture-systemand then at https://github.com/apache/hbase/tree/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserverand wondering... .... would it be possible/interesting/better to "open up" a little bit and implement something that puts HLog events on a bus like that Databus and thus allow *anyone* to do *anything* with data being written to (or deleted from) HBase? Replication itself, secondary indexing, etc. Thanks, Otis -- HBASE Performance Monitoring http://sematext.com/spm/hbase-performance-monitoring/ --20cf3074b47c2f4e8504d6fc8d9d--