Mailing-List: contact hbase-user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-user@hadoop.apache.org
Received-SPF: pass (nike.apache.org: domain of jdcryans@gmail.com designates
 209.85.210.189 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type;
        b=f7bbuROP9pi+/qdyrmOhLwSSN49Y5NQ334wH4Xr+7ffOq9WGaEmZYq9Jl/AdyvuTkZ
         1uyyC/26V8VZXZ/yEG8qpBQDXKxNpCWWcoHeUqls2lqEM32hINsc/h0m3cx3k+N1/QK7
         Jm3pNM5peDci1Z4YWCXwspSBsrdMEvZUcvnag=
MIME-Version: 1.0
Sender: jdcryans@gmail.com
In-Reply-To: <259844.3302.qm@web65512.mail.ac4.yahoo.com>
References: <1e7471d51002090830l28e8d648vfedd0a8395951eaf@mail.gmail.com>
	 <31a243e71002090953q7f615b0ch63e6211f58110ad0@mail.gmail.com>
	 <259844.3302.qm@web65512.mail.ac4.yahoo.com>
Date: Tue, 9 Feb 2010 10:27:32 -0800
Message-ID: <31a243e71002091027y2413ffa6w74c4572c83cf775e@mail.gmail.com>
Subject: Re: Hbase thrift status 0.20.3
From: Jean-Daniel Cryans <jdcryans@apache.org>
To: hbase-user@hadoop.apache.org
Content-Type: multipart/alternative; boundary=001485f7c3ee3aeb39047f2f122f

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

That's a very nifty ascii drawing Andy ;)

I like your detailed answer, maybe that should be part of the FAQ?

J-D

On Tue, Feb 9, 2010 at 10:24 AM, Andrew Purtell <apurtell@apache.org> wrote:

> The Thrift and REST connectors have different aims. My rule of thumb
> is this:
>
> If you need cross platform/language compatibility in a single tenant
> deployment, use the Thrift connector, especially if you anticipate a
> high rate of small data operations. It offers performance near the
> Java native API for this type of use.
>
> If you need cross platform/language compatibility in a *multi* tenant
> deployment, use the REST connector (Stargate) in a servlet deployment
> and configure authorization/authentication according to the
> capabilities of the servlet container. You can also stack the REST
> option in a layered architecture:
>
>             clients
>               /|\
>                |
>               \|/
>    +-------------------------+
>    |  cache (reverse proxy)  |
>    +-------------------------+
>    |     authentication      |
>    +-------------------------+
>    |REST connector (Stargate)|
>
>    +-------------------------+
>               /|\
>                |
>               \|/
>              HBase
>
> Stargate is cache aware. Cache and authentication can be combined:
> http://linuxdevcenter.com/pub/a/linux/2001/08/09/authen_squid.html
> There's no comparable stacking on the Thrift side that I'm aware.
>
>   - Andy
>
>
>
> ----- Original Message ----
> > From: Jean-Daniel Cryans <jdcryans@apache.org>
> > To: hbase-user@hadoop.apache.org
> > Sent: Tue, February 9, 2010 9:53:08 AM
> > Subject: Re: Hbase thrift status 0.20.3
> >
> > We use thrift in production to communicate with HBase here at Stumbleupon
> > and the Stargate REST API is also well supported (and has a nice ruby
> client
> > http://github.com/greglu/hbase-stargate).
> >
> > J-D
> >
> > On Tue, Feb 9, 2010 at 8:30 AM, Saptarshi Guha wrote:
> >
> > > Hello
> > > Currently what is the best way to communicate with hbase outside of
> > > java? I think thrift appears to be the best , is it still very much
> > > part of Hbase 0.20.3?
> > >
> > > Thank you
> > > saptarshi
> > >
>
>
>
>
>
>

--001485f7c3ee3aeb39047f2f122f--