Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of elliott.neil.clark@gmail.com
 designates 209.85.219.54 as permitted sender)
MIME-Version: 1.0
Sender: elliott.neil.clark@gmail.com
In-Reply-To: 
 <CALte62yWcr16_G6+dmc+rgqDHMgV67MasYk+V19RMDB=164PgQ@mail.gmail.com>
References: 
 <CAKyG0H2WdO2vhKy=2ef_xBq_LnVGbUT-HFquvz2ZT+j9Cez8qw@mail.gmail.com>
	<CALte62y2Rc1Zk18XCrqDiZFiyR1_8HhxdmgO3tyoihJXZMBCxw@mail.gmail.com>
	<CAKyG0H3s7QxU7xbppwRnRRLa2WE4zN3vJTCThNNT9Xpj+Pdicw@mail.gmail.com>
	<CALte62yWcr16_G6+dmc+rgqDHMgV67MasYk+V19RMDB=164PgQ@mail.gmail.com>
Date: Tue, 11 Dec 2012 22:47:52 -0800
Message-ID: 
 <CALvzVW0ctxkqb8dsta3WXo3PN2+xgbWVgRtMwj28FOx-828d1A@mail.gmail.com>
Subject: Re: ClientService protobuf RPC service implementation?
From: Elliott Clark <eclark@apache.org>
To: dev@hbase.apache.org
Content-Type: multipart/alternative; boundary=f46d041826327c97b104d0a22d3f

--f46d041826327c97b104d0a22d3f
Content-Type: text/plain; charset=ISO-8859-1

The blocking interface is just used to tie the request type to a response
type.  The actual non-blocking/blocking part is implemented in  HBaseRPC
(it actually uses nio to do the io).

If you want to create your own client that's non-blocking you'll have to
create your own version of HBaseRPC and the serialization.  Here's
something close to what you were talking about that I created.  It can read
root and meta but not much more:
https://github.com/elliottneilclark/hbase/tree/webscale_client

Though currently in trunk lots of changes have been made for how HBase
sends KeyValues across the wire.


On Tue, Dec 11, 2012 at 9:08 PM, Ted Yu <yuzhihong@gmail.com> wrote:

> protobuf is used in HBase for serialization.
>
> I searched the files under
> hbase-protocol/src/main/java/org/apache/hadoop/hbase/protobuf/generated but
> didn't see any non-blocking interface.
>
> A brief search on the web resulted in:
> https://groups.google.com/forum/?fromgroups=#!topic/protobuf/s7jAGvJKgmA
>
> But that thread was really old.
>
> Would do more searching.
>
> Cheers
>
> On Tue, Dec 11, 2012 at 6:05 PM, Mick Hittesdorf
> <mick.hittesdorf@gmail.com>wrote:
>
> > Thanks for the information. I was wondering why the ClientProtocol
> > specifically implements the BlockingInterface? I want to write a
> > non-blocking, event-driven, asynchronous, multi-threaded client similar
> to
> > asynchhbase (https://github.com/OpenTSDB/asynchbase) but in C++.  Am I
> > going to need to 'hide' the blocking semantics implemented by HBase in my
> > client in order to achieve this?
> >
> > Thanks in advance! Mick
> >
> > On Mon, Dec 10, 2012 at 11:00 PM, Ted Yu <yuzhihong@gmail.com> wrote:
> >
> > > src/main/java/org/apache/hadoop/hbase/client/ClientProtocol.java
> > >
> >
>

--f46d041826327c97b104d0a22d3f--