Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of saint.ack@gmail.com
 designates 209.85.214.41 as permitted sender)
MIME-Version: 1.0
Sender: saint.ack@gmail.com
In-Reply-To: 
 <CAKyG0H2WdO2vhKy=2ef_xBq_LnVGbUT-HFquvz2ZT+j9Cez8qw@mail.gmail.com>
References: 
 <CAKyG0H2WdO2vhKy=2ef_xBq_LnVGbUT-HFquvz2ZT+j9Cez8qw@mail.gmail.com>
Date: Mon, 10 Dec 2012 21:05:25 -0800
Message-ID: 
 <CADcMMgGDVb-ScGvmK9APUuO2bXnAdhoOF=3TZUANp5vC=khTTQ@mail.gmail.com>
Subject: Re: ClientService protobuf RPC service implementation?
From: Stack <stack@duboce.net>
To: HBase Dev List <dev@hbase.apache.org>
Content-Type: multipart/alternative; boundary=00151747bd543d66f604d08ca106

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

On Mon, Dec 10, 2012 at 4:13 PM, Mick Hittesdorf
<mick.hittesdorf@gmail.com>wrote:

> Has any work been done to implement the ClientService protobuf server
> defined in the following proto file?
>
>
> http://svn.apache.org/viewvc/hbase/trunk/hbase-protocol/src/main/protobuf/Client.proto?view=markup
>
> I'd like to build an HBase client in C++ using the new protobuf-based
> client protocol. Where should I start?
>
> Thanks!
>

That described service is currently what client and server use in trunk.
 All communication is protobuf'd as of a commit today but we are working on
coming back some from the total protobuf'ing of all we pass, in particular,
the pb'ing of all KeyValues passed across the ipc chasm.  We will do
something more 'raw' passing the bigdata.  The issue we are discussing how
to pass big volumes of KeyValues is HBASE-7233.  It would be interesting to
get your input coming from your c++ perspective.

Thanks,
St.Ack
*
*

--00151747bd543d66f604d08ca106--