A fully asynchronous, non-blocking, thread-safe, high-performance HBase client.
Java Shell
Pull request Compare This branch is 179 commits behind OpenTSDB:master.
Latest commit a2a3f7f Jun 7, 2013 @tsuna tsuna Properly clean up when connection fails before being opened.
This can happen when we attempt to connect to a RegionServer, and we
buffer some RPCs to send once connected, but we never successfully
connect, because of a connection timeout.

Bug reported by Viral Bajaria.
Permalink
Failed to load latest commit information.
.mvn-compat/src Maven SDL compatibility & plugin updates. Mar 6, 2012
build-aux Clean up any stale temporary file if we already have the right file. May 6, 2012
src Properly clean up when connection fails before being opened. Jun 7, 2013
test Add a new helper function to produce better errors during tests. Apr 29, 2013
third_party Update suasync to 1.3.2. May 30, 2013
.gitignore
AUTHORS
COPYING Base copyright on an AUTHORS file. Feb 9, 2012
HACKING Document how to run integration tests. Apr 29, 2013
INSTALL Base copyright on an AUTHORS file. Feb 9, 2012
Makefile Add more scanner filters. Apr 29, 2013
NEWS Update NEWS / THANKS. May 23, 2013
README Initial commit: import the code. Sep 8, 2010
THANKS Update NEWS / THANKS. May 23, 2013
logback.xml Initial commit: import the code. Sep 8, 2010
pom.xml.in Update all dependencies. Feb 15, 2013

README

  ,--------------------.
  | Asynchronous HBase |
  `--------------------'

This is an alternative Java library to use HBase in applications that require
a fully asynchronous, non-blocking, thread-safe, high-performance HBase API.

This HBase client differs significantly from HBase's client (HTable).
Switching to it is not easy as it requires to rewrite all the code that was
interacting with any HBase API.  This pays off in applications that are
asynchronous by nature or that want to use several threads to interact
efficiently with HBase.

Please read the Javadoc starting from the HBaseClient class.  This class
replaces all your HTable instances.  Unlike HTable, you should have only
one instance of HBaseClient in your application, regardless of the number
of tables or threads you want to use.  The Javadoc also spells out rules
you have to follow in order to use the API properly in a multi-threaded
application.