hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Daniel Cryans <jdcry...@apache.org>
Subject Re: Rest, Stargate or Thrift ?
Date Thu, 05 Nov 2009 04:55:49 GMT
The new REST API called Stargate is currently considered not yet
production-ready by its author, committer Andrew Purtell. I'll leave
him expand further. If there's a bug or a feature is missing, the best
thing to do is to write to the list and/or open a jira.

The Thrift API is lagging in features compared to the current Java
API. There's currently no official support from any core dev. At SU we
use it but we are still considering other options; the main problem is
that the implementation in some languages are buggy and hard to work

Both APIs have little overhead since they act as thin clients over the
fat Java client. I would consider running the API servers directly on
the client machines and have the application code bind on localhost
rather than going on the network.


On Wed, Nov 4, 2009 at 6:06 PM, Kevin Peterson <kpeterson@biz360.com> wrote:
> On Wed, Nov 4, 2009 at 5:10 PM, Joost Ouwerkerk <joost@openplaces.org>wrote:
>> Language-independent RPC services for HBase: is there concensus on
>> preference?  Architecturally, I imagine they are equivalent.
>> Performance-wise, I imagine Thrift is most optimal.  As for support and
>> maintenance by core HBase contributors, is Thrift also privileged?
> Yes, use Thrift.
> I was not able to get Stargate or the legacy REST API working acceptably at
> the time 0.20 was released. I don't remember what my problems were -- I
> think Stargate doesn't yet support scanners, and I couldn't find a working
> ruby client for REST.
> The only downside we've had is that our developers on Windows can't seem to
> get the thrift ruby gem installed.
> I don't see what Stargate could offer that would get sites like Stumbleupon
> to migrate away from Thrift, so even if Stargate improves, Thrift support
> will likely continue.

View raw message