Skip to content
A fully asynchronous, non-blocking, thread-safe, high-performance HBase client. http://github.com/stumbleupon/asynchbase
Java Shell
Find file
Pull request Compare This branch is 161 commits behind OpenTSDB:master.
Latest commit a2a3f7f @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.
Failed to load latest commit information.
.mvn-compat/src Maven SDL compatibility & plugin updates.
build-aux Clean up any stale temporary file if we already have the right file.
src Properly clean up when connection fails before being opened.
test
third_party Update suasync to 1.3.2.
.gitignore Update all dependencies.
AUTHORS Add Viral to AUTHORS for his work on ScanFilter.
COPYING Base copyright on an AUTHORS file.
HACKING Document how to run integration tests.
INSTALL Base copyright on an AUTHORS file.
Makefile Add more scanner filters.
NEWS Update NEWS / THANKS.
README Initial commit: import the code.
THANKS Update NEWS / THANKS.
logback.xml Initial commit: import the code.
pom.xml.in

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.
Something went wrong with that request. Please try again.