hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ian Varley <ivar...@salesforce.com>
Subject Re: HBase Client.
Date Wed, 20 Mar 2013 16:23:27 GMT
Pradeep -

One more to add to your list of clients is Phoenix:


It's a "SQL skin", built on top of the standard Java client with various optimizations; it
exposes HBase via a standard JDBC interface, and thus might let you easily plug into other
tools for testing performance.


On Mar 20, 2013, at 4:49 AM, Vivek Mishra wrote:

I have used Kundera, persistence overhead on HBase API is minimal considering feature set
available for use within Kundera.

From: Viral Bajaria [viral.bajaria@gmail.com]
Sent: 20 March 2013 12:30
To: user@hbase.apache.org<mailto:user@hbase.apache.org>
Subject: Re: HBase Client.

Most of the clients listed below are language specific, so if your
benchmarking scripts are written in JAVA, you are better off running the
java client.
HBase Shell is more for running something interactive, not sure how you
plan to benchmark that.
REST is something that you could use, but I can't comment on it's
performance since I have
HappyBase is for python.
Kundera, can't comment since I have not used it.

You can look at AsyncHBase, if you don't mind wrapping your head around it.
But it's a bigger rewrite since the API is not compatible with existing

On Tue, Mar 19, 2013 at 11:25 PM, Pradeep Kumar Mantha <pradeepm66@gmail.com<mailto:pradeepm66@gmail.com>


       I would like to benchmark HBase using some of our distributed
applications using custom developed benchmarking scripts/programs.
I found the following clients are available. Could you please let me
know which of the following provides best performance.

1. Java direct interface to  HBASE.
2. HBase Shell
3. via Rest
4. HappyBase
5. Kundera

Please let me know if there is any other client which provides better



NOTE: This message may contain information that is confidential, proprietary, privileged or
otherwise protected by law. The message is intended solely for the named addressee. If received
in error, please destroy and notify the sender. Any use of this email is prohibited when received
in error. Impetus does not represent, warrant and/or guarantee, that the integrity of this
communication has been maintained nor that the communication is free of errors, virus, interception
or interference.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message