Interface | Description |
---|---|
Admin |
The administrative API for HBase.
|
AdvancedScanResultConsumer |
This is the low level API for asynchronous scan.
|
AdvancedScanResultConsumer.ScanController |
Used to suspend or stop a scan, or get a scan cursor if available.
|
AdvancedScanResultConsumer.ScanResumer |
Used to resume a scan.
|
AsyncAdmin |
The asynchronous administrative API for HBase.
|
AsyncAdminBuilder |
For creating
AsyncAdmin . |
AsyncBufferedMutator |
Used to communicate with a single HBase table in batches.
|
AsyncBufferedMutatorBuilder |
For creating
AsyncBufferedMutator . |
AsyncConnection |
The asynchronous version of Connection.
|
AsyncTable<C extends ScanResultConsumerBase> |
The interface for asynchronous version of Table.
|
AsyncTable.CoprocessorCallback<R> |
The callback when we want to execute a coprocessor call on a range of regions.
|
AsyncTableBuilder<C extends ScanResultConsumerBase> |
For creating
AsyncTable . |
AsyncTableRegionLocator |
The asynchronous version of RegionLocator.
|
Attributes | |
BufferedMutator |
Used to communicate with a single HBase table similar to
Table but meant for batched,
asynchronous puts. |
BufferedMutator.ExceptionListener |
Listens for asynchronous exceptions on a
BufferedMutator . |
ColumnFamilyDescriptor |
An ColumnFamilyDescriptor contains information about a column family such as the number of
versions, compression settings, etc.
|
Connection |
A cluster connection encapsulating lower level individual connections to actual servers and a
connection to zookeeper.
|
CoprocessorDescriptor |
CoprocessorDescriptor contains the details about how to build a coprocessor.
|
RegionInfo |
Information about a region.
|
RegionLocator |
Used to view region location information for a single HBase table.
|
RequestController |
An interface for client request scheduling algorithm.
|
RequestController.Checker |
Picks up the valid data.
|
ResultScanner |
Interface for client-side scanning.
|
Row |
Has a row.
|
RpcRetryingCaller<T> | |
ScanResultConsumer |
Receives
Result for an asynchronous scan. |
ScanResultConsumerBase |
The base interface for scan result consumer.
|
ServiceCaller<S,R> |
Delegate to a protobuf rpc call.
|
Table |
Used to communicate with a single HBase table.
|
TableBuilder |
For creating
Table instance. |
TableDescriptor |
TableDescriptor contains the details about an HBase table such as the descriptors of all the
column families, is the table a catalog table,
hbase:meta , if the table is read
only, the maximum size of the memstore, when the region split should occur, coprocessors
associated with it etc... |
Class | Description |
---|---|
Append |
Performs Append operations on a single row.
|
BalancerDecision |
History of balancer decisions taken for region movements.
|
BalanceRequest |
Encapsulates options for executing a run of the Balancer.
|
BalanceRequest.Builder |
Builder for constructing a
BalanceRequest |
BalanceResponse |
Response returned from a balancer invocation
|
BalancerRejection |
History of detail information that balancer movements was rejected
|
BufferedMutatorParams |
Parameters for instantiating a
BufferedMutator . |
CheckAndMutate |
Used to perform CheckAndMutate operations.
|
CheckAndMutate.Builder |
A builder class for building a CheckAndMutate object.
|
CheckAndMutateResult |
Represents a result of a CheckAndMutate operation
|
ColumnFamilyDescriptorBuilder | |
ConnectionFactory |
A non-instantiable class that manages creation of
Connection s. |
CoprocessorDescriptorBuilder |
Used to build the
CoprocessorDescriptor |
Cursor |
Scan cursor to tell client where server is scanning
Scan.setNeedCursorResult(boolean)
Result.isCursor() Result.getCursor() |
Delete |
Used to perform Delete operations on a single row.
|
Get |
Used to perform Get operations on a single row.
|
HTableMultiplexer | Deprecated
since 2.2.0, will be removed in 3.0.0, without replacement.
|
HTableMultiplexer.HTableMultiplexerStatus | Deprecated
since 2.2.0, will be removed in 3.0.0, without replacement.
|
Increment |
Used to perform Increment operations on a single row.
|
LogEntry |
Abstract response class representing online logs response from ring-buffer use-cases e.g
slow/large RPC logs, balancer decision logs
|
LogQueryFilter | Deprecated
as of 2.4.0.
|
Mutation | |
NormalizeTableFilterParams |
A collection of criteria used for table selection.
|
OnlineLogRecord |
Slow/Large Log payload for hbase-client, to be used by Admin API get_slow_responses and
get_large_responses
|
Operation |
Superclass for any type that maps to a potentially application-level query.
|
OperationWithAttributes | |
Put |
Used to perform Put operations for a single row.
|
Query |
Base class for HBase read operations; e.g.
|
RegionLoadStats |
POJO representing region server load
|
RequestControllerFactory |
A factory class that constructs an
RequestController . |
Result | |
RowMutations |
Performs multiple mutations atomically on a single row.
|
Scan |
Used to perform Scan operations.
|
SnapshotDescription |
The POJO equivalent of HBaseProtos.SnapshotDescription
|
TableDescriptorBuilder |
Convenience class for composing an instance of
TableDescriptor . |
TableDescriptorUtils |
Enum | Description |
---|---|
CompactionState |
POJO representing the compaction state
|
CompactType |
Currently, there are only two compact types:
NORMAL means do store files compaction;
MOB means do mob files compaction. |
Consistency |
Consistency defines the expected consistency level for an operation.
|
Durability |
Enum describing the durability guarantees for tables and
Mutation s Note that the items
must be sorted in order of increasing durability |
IsolationLevel |
Specify Isolation levels in Scan operations.
|
MasterSwitchType |
Represents the master switch type
|
MobCompactPartitionPolicy |
Enum describing the mob compact partition policy types.
|
RequestController.ReturnCode | |
Scan.ReadType | |
ServerType |
Select server type i.e destination for RPC request associated with ring buffer.
|
SnapshotType |
POJO representing the snapshot type
|
Exception | Description |
---|---|
DoNotRetryRegionException |
Similar to RegionException, but disables retries.
|
LockTimeoutException | |
NoServerForRegionException |
Thrown when no region server can be found for a region
|
RegionOfflineException |
Thrown when a table can not be located
|
RetriesExhaustedException |
Exception thrown by HTable methods when an attempt to do something (like commit changes) fails
after a bunch of retries.
|
RetriesExhaustedWithDetailsException |
This subclass of
RetriesExhaustedException is thrown when
we have more information about which rows were causing which exceptions on what servers. |
RowTooBigException |
Gets or Scans throw this exception if running without in-row scan flag set and row size appears
to exceed max configured size (configurable via hbase.table.max.rowsize).
|
WrongRowIOException |
To administer HBase, create and drop tables, list and alter tables,
use Admin
. Once created, table access is via an instance
of Table
. You add content to a table a row at a time. To
insert, create an instance of a Put
object. Specify value,
target column and optionally a timestamp. Commit your update using
Table.put(Put)
.
To fetch your inserted value, use Get
. The Get can be
specified to be broad -- get all on a particular row -- or narrow; i.e. return only a single cell
value. After creating an instance of
Get, invoke Table.get(Get)
.
Use Scan
to set up a scanner -- a Cursor- like access.
After creating and configuring your Scan instance, call
Table.getScanner(Scan)
and then
invoke next on the returned object. Both Table.get(Get)
and Table.getScanner(Scan)
return a
Result
.
Use Delete
to remove content.
You can remove individual cells or entire families, etc. Pass it to
Table.delete(Delete)
to execute.
Puts, Gets and Deletes take out a lock on the target row for the duration of their operation. Concurrent modifications to a single row are serialized. Gets and scans run concurrently without interference of the row locks and are guaranteed to not to return half written rows.
Client code accessing a cluster finds the cluster by querying ZooKeeper.
This means that the ZooKeeper quorum to use must be on the client CLASSPATH.
Usually this means make sure the client can find your hbase-site.xml
.
Once you have a running HBase, you probably want a way to hook your application up to it. If your application is in Java, then you should use the Java API. Here's an example of what a simple client might look like. This example assumes that you've created a table called "myTable" with a column family called "myColumnFamily".
import java.io.IOException; import org.apache.hadoop.hbase.HBaseConfiguration; import org.apache.hadoop.hbase.TableName; import org.apache.hadoop.hbase.client.Connection; import org.apache.hadoop.hbase.client.ConnectionFactory; import org.apache.hadoop.hbase.client.Get; import org.apache.hadoop.hbase.client.Table; import org.apache.hadoop.hbase.client.Put; import org.apache.hadoop.hbase.client.Result; import org.apache.hadoop.hbase.client.ResultScanner; import org.apache.hadoop.hbase.client.Scan; import org.apache.hadoop.hbase.util.Bytes; // Class that has nothing but a main. // Does a Put, Get and a Scan against an hbase table. // The API described here is since HBase 1.0. public class MyLittleHBaseClient { public static void main(String[] args) throws IOException { // You need a configuration object to tell the client where to connect. // When you create a HBaseConfiguration, it reads in whatever you've set // into your hbase-site.xml and in hbase-default.xml, as long as these can // be found on the CLASSPATH Configuration config = HBaseConfiguration.create(); // Next you need a Connection to the cluster. Create one. When done with it, // close it. A try/finally is a good way to ensure it gets closed or use // the jdk7 idiom, try-with-resources: see // https://docs.oracle.com/javase/tutorial/essential/exceptions/tryResourceClose.html // // Connections are heavyweight. Create one once and keep it around. From a Connection // you get a Table instance to access Tables, an Admin instance to administer the cluster, // and RegionLocator to find where regions are out on the cluster. As opposed to Connections, // Table, Admin and RegionLocator instances are lightweight; create as you need them and then // close when done. // Connection connection = ConnectionFactory.createConnection(config); try { // The below instantiates a Table object that connects you to the "myLittleHBaseTable" table // (TableName.valueOf turns String into a TableName instance). // When done with it, close it (Should start a try/finally after this creation so it gets // closed for sure the jdk7 idiom, try-with-resources: see // https://docs.oracle.com/javase/tutorial/essential/exceptions/tryResourceClose.html) Table table = connection.getTable(TableName.valueOf("myLittleHBaseTable")); try { // To add to a row, use Put. A Put constructor takes the name of the row // you want to insert into as a byte array. In HBase, the Bytes class has // utility for converting all kinds of java types to byte arrays. In the // below, we are converting the String "myLittleRow" into a byte array to // use as a row key for our update. Once you have a Put instance, you can // adorn it by setting the names of columns you want to update on the row, // the timestamp to use in your update, etc. If no timestamp, the server // applies current time to the edits. Put p = new Put(Bytes.toBytes("myLittleRow")); // To set the value you'd like to update in the row 'myLittleRow', specify // the column family, column qualifier, and value of the table cell you'd // like to update. The column family must already exist in your table // schema. The qualifier can be anything. All must be specified as byte // arrays as hbase is all about byte arrays. Lets pretend the table // 'myLittleHBaseTable' was created with a family 'myLittleFamily'. p.add(Bytes.toBytes("myLittleFamily"), Bytes.toBytes("someQualifier"), Bytes.toBytes("Some Value")); // Once you've adorned your Put instance with all the updates you want to // make, to commit it do the following (The HTable#put method takes the // Put instance you've been building and pushes the changes you made into // hbase) table.put(p); // Now, to retrieve the data we just wrote. The values that come back are // Result instances. Generally, a Result is an object that will package up // the hbase return into the form you find most palatable. Get g = new Get(Bytes.toBytes("myLittleRow")); Result r = table.get(g); byte [] value = r.getValue(Bytes.toBytes("myLittleFamily"), Bytes.toBytes("someQualifier")); // If we convert the value bytes, we should get back 'Some Value', the // value we inserted at this location. String valueStr = Bytes.toString(value); System.out.println("GET: " + valueStr); // Sometimes, you won't know the row you're looking for. In this case, you // use a Scanner. This will give you cursor-like interface to the contents // of the table. To set up a Scanner, do like you did above making a Put // and a Get, create a Scan. Adorn it with column names, etc. Scan s = new Scan(); s.addColumn(Bytes.toBytes("myLittleFamily"), Bytes.toBytes("someQualifier")); ResultScanner scanner = table.getScanner(s); try { // Scanners return Result instances. // Now, for the actual iteration. One way is to use a while loop like so: for (Result rr = scanner.next(); rr != null; rr = scanner.next()) { // print out the row we found and the columns we were looking for System.out.println("Found row: " + rr); } // The other approach is to use a foreach loop. Scanners are iterable! // for (Result rr : scanner) { // System.out.println("Found row: " + rr); // } } finally { // Make sure you close your scanners when you are done! // Thats why we have it inside a try/finally clause scanner.close(); } // Close your table and cluster connection. } finally { if (table != null) table.close(); } } finally { connection.close(); } } }
There are many other methods for putting data into and getting data out of HBase, but these examples should get you started. See the Table javadoc for more methods. Additionally, there are methods for managing tables in the Admin class.
If your client is NOT Java, then you should consider the Thrift or REST libraries.
See also the section in the HBase Reference Guide where it discusses HBase Client. It has section on how to access HBase from inside your multithreaded environment how to control resources consumed client-side, etc.
Copyright © 2007–2020 The Apache Software Foundation. All rights reserved.