Package org.apache.hadoop.hbase.client
Table of Contents
Overview
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
.
Example API Usage
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.
Related Documentation
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.
-
ClassDescriptionHelper class for custom client scanners.This class is used to extend AP to process single action request, like delete, get etc.Base class for rpc based connection registry implementation.For describing the actual asynchronous rpc call.A Get, Put, Increment, Append, or Delete associated with it's region.The administrative API for HBase.This is the low level API for asynchronous scan.Used to suspend or stop a scan, or get a scan cursor if available.Used to resume a scan.A ScanResultCache that may return partial result.Performs Append operations on a single row.The asynchronous administrative API for HBase.For creating
AsyncAdmin
.Base class for all asynchronous admin builders.Additional Asynchronous Admin capabilities for clients.Retry caller for batch.Used to communicate with a single HBase table in batches.For creatingAsyncBufferedMutator
.The implementation ofAsyncBufferedMutatorBuilder
.The implementation ofAsyncBufferedMutator
.The asynchronous client scanner implementation.The asynchronous version of Connection.Timeout configs.The implementation of AsyncConnection.Just a wrapper ofRawAsyncHBaseAdmin
.Retry caller for a request call to master.The asynchronous locator for meta region.The asynchronous locator for regions other than meta.This class allows a continuous flow of requests.Contains the attributes of a task which will be executed byAsyncProcess
.The number of processed rows.Cache of RegionLocations for use byAsyncNonMetaRegionLocator
.The asynchronous region locator.Helper class for asynchronous region locator.The context used to wait for results from one submit call.AsyncRequestFutureImpl<CResult>The context, and return value, for a single submit/submitAll call.Sync point for calls to multiple replicas for the same user request (Get).Factory to create an AsyncRpcRetryCaller.Retry caller for scanning a region.Retry caller for a request call to region server.Retry caller for a single request, such as get, put, delete, etc.AsyncTable<C extends ScanResultConsumerBase>The interface for asynchronous version of Table.Deprecated.Since 2.4.0, will be removed in 4.0.0.Deprecated.Since 2.4.0, will be removed in 4.0.0.The callback when we want to execute a coprocessor call on a range of regions.Helper class for sending coprocessorService request that executes a coprocessor call on regions which are covered by a range.AsyncTableBuilder<C extends ScanResultConsumerBase>For creatingAsyncTable
.AsyncTableBuilderBase<C extends ScanResultConsumerBase>Base class for all asynchronous table builders.Just a wrapper ofRawAsyncTableImpl
.The asynchronous version of RegionLocator.The implementation of AsyncRegionLocator.TheResultScanner
implementation forRawAsyncTableImpl
.History of balancer decisions taken for region movements.Encapsulates options for executing a run of the Balancer.Builder for constructing aBalanceRequest
Response returned from a balancer invocationUsed in HMaster to build aBalanceResponse
for returning results of a balance invocation to callersHistory of detail information that balancer movements was rejectedA scan result cache for batched scan, i.e,scan.getBatch() > 0 && !scan.getAllowPartialResults()
.Used to communicate with a single HBase table similar toTable
but meant for batched, asynchronous puts.Listens for asynchronous exceptions on aBufferedMutator
.Used to communicate with a single HBase table similar toTable
but meant for batched, potentially asynchronous puts.Parameters for instantiating aBufferedMutator
.This should be implemented by the Get/Scan implementations that talk to replica regions.This class is used to unify HTable calls with AsyncProcess Framework.A Catalog replica selector decides which catalog replica to go for read requests when it is configured as CatalogReplicaMode.LoadBalance.Factory to create aCatalogReplicaLoadBalanceSelector
CatalogReplicaLoadBalanceReplicaSimpleSelector implements a simple catalog replica load balancing algorithm.StaleLocationCacheEntry is the entry when a stale location is reported by an client.Used to perform CheckAndMutate operations.A builder class for building a CheckAndMutate object.Represents a result of a CheckAndMutate operationClientAsyncPrefetchScanner implements async scanner behaviour.Client side rpc controller for coprocessor implementation.The class that is able to determine some unique strings for the client, such as an IP address, PID, and composite deterministic ID.Implements the scanner interface for the HBase client.A RegionServerCallable set to use the Client protocol.A client scanner for a region opened for read-only on the client side.ClientSimpleScanner implements a sync scanner behaviour.Internal methods on Connection that should not be used by user code.Fetch cluster id through special preamble header.A class that receives the cluster status, and provide it as a set of service to the client.Class to be extended to manage a new dead server.The interface to be implemented by a listener of a cluster status event.An ColumnFamilyDescriptor contains information about a column family such as the number of versions, compression settings, etc.An ModifyableFamilyDescriptor contains information about a column family such as the number of versions, compression settings, etc.POJO representing the compaction stateCurrently, there are only two compact types:NORMAL
means do store files compaction;MOB
means do mob files compaction.A scan result cache that only returns complete result.A cluster connection encapsulating lower level individual connections to actual servers and a connection to zookeeper.Configuration parameters for the connection.A non-instantiable class that manages creation ofConnection
s.Main implementation ofConnection
andClusterConnection
interfaces.LikeConnectionClosedException
but thrown from the checkClosed call which looks at the local this.closed flag.State of the MasterService connection/setup.The record of errors for servers.The record of errors for a server.Registry for meta information needed for connection setup to a HBase cluster.Factory class to get the instance of configured connection registry.A class for creatingRpcClient
and related stubs used byAbstractRpcBasedConnectionRegistry
.Utility used by client connections.Some tests shut down the master.Consistency defines the expected consistency level for an operation.CoprocessorDescriptor contains the details about how to build a coprocessor.Used to build theCoprocessorDescriptor
Scan cursor to tell client where server is scanningScan.setNeedCursorResult(boolean)
Result.isCursor()
Result.getCursor()
A wrapper for a runnable for a group of actions for a single regionserver.Used to perform Delete operations on a single row.Similar to RegionException, but disables retries.Enum describing the durability guarantees for tables andMutation
s Note that the items must be sorted in order of increasing durabilityKeeps track of repeated failures to any region server.A Callable for flushRegion() RPC.Used to perform Get operations on a single row.HBaseAdmin is no longer a client API.Future that waits on a procedure result.UseConnection.getHbck()
to obtain an instance ofHbck
instead of constructing an HBaseHbck directly.Hbck fixup tool APIs.An implementation ofRegionLocator
.An implementation ofTable
.Deprecated.since 2.2.0, will be removed in 3.0.0, without replacement.Helper to count the average over an interval until reset.Deprecated.since 2.2.0, will be removed in 3.0.0, without replacement.Deprecated.Deprecated.Deprecated.Immutable version of ScanUsed to perform Increment operations on a single row.Specify Isolation levels in Scan operations.Abstract response class representing online logs response from ring-buffer use-cases e.g slow/large RPC logs, balancer decision logsDeprecated.as of 2.4.0.A RetryingCallable for Master RPC operations.The implementation of a master based coprocessor rpc channel.A KeepAlive connection is not physically closed immediately after the close, but rather kept alive for a few minutes.Deprecated.Since 2.5.0, will be removed in 4.0.0.Represents the master switch typeA cache implementation for region locations from meta.Util class to DRY common logic between AsyncRegionLocationCache and MetaCacheThis class is for maintaining the various connection statistics and publishing them through the metrics interfaces.A container class for collecting details about the RPC call as it percolates.A lambda for dispatching to the appropriate metric factory methodEnum describing the mob compact partition policy types.Container for Actions (i.e.A container for Result objects, grouped by regionName.Callable that handles themulti
method call going against a single regionserver; i.e.An implementation of RegionInfo that adds mutable methods so can build a RegionInfo instance.Implementations make an rpc call against a RegionService via a protobuf Service.NonceGenerator interface.Class that acts as a NoOpInterceptor.A collection of criteria used for table selection.Used to instantiate an instance ofNormalizeTableFilterParams
.Thrown when no region server can be found for a regionSlow/Large Log payload for hbase-client, to be used by Admin API get_slow_responses and get_large_responsesSuperclass for any type that maps to a potentially application-level query.Thrown when a batch operation exceeds the operation timeoutA helper class used to access the package private field in o.a.h.h.client package.NonceGenerator implementation that uses client ID hash + random int as nonce group, and random numbers as nonces.The concreteRetryingCallerInterceptor
class that implements the preemptive fast fail feature.Used to perform Put operations for a single row.Base class for HBase read operations; e.g.The implementation of AsyncAdmin.RawAsyncHBaseAdmin.AdminRpcCall<RESP,REQ> RawAsyncHBaseAdmin.MasterRpcCall<RESP,REQ> The implementation of RawAsyncTable.RawAsyncTableImpl.Converter<D,I, S> RawAsyncTableImpl.RpcCall<RESP,REQ> Similar to RegionServerCallable but for the AdminService interface.Provides clients with an RPC connection to call Coprocessor EndpointService
s against a given table region.The implementation of a region based coprocessor rpc channel.Represents a coprocessor service method execution against a single region.Information about a region.Utility used composing RegionInfo for 'display'; e.g.POJO representing region server loadIndicate which row you want to locate.Used to view region location information for a single HBase table.Thrown when a table can not be locatedUtility methods which contain the logic for regions and replicas.RegionServerCallable<T,S> Implementations make a RPC call against a RegionService via a protobuf Service.The implementation of a region server based coprocessor rpc channel.Connection registry implementation for region server.Thread safe utility that keeps registry end points used byConnectionRegistry
up to date.An interface for client request scheduling algorithm.Picks up the valid data.A factory class that constructs anRequestController
.A completion service for the RpcRetryingCallerFactory.Interface for client-side scanning.Statistics update about a server/regionException thrown by HTable methods when an attempt to do something (like commit changes) fails after a bunch of retries.Data structure that allows adding more info around Throwable incident.This subclass ofRetriesExhaustedException
is thrown when we have more information about which rows were causing which exceptions on what servers.A Callable<T> that will be retried.This class is designed to fit into the RetryingCaller class which forms the central piece of intelligence for the client side retries for most calls.The context object used in theRpcRetryingCaller
to enableRetryingCallerInterceptor
to intercept calls.Factory implementation to provide theConnectionImplementation
with the implementation of theRetryingCallerInterceptor
that we would use to intercept theRpcRetryingCaller
during the course of their calls.Tracks the amount of time remaining for an operation.A reversed client scanner which support backward scanningA reversed ScannerCallable which supports backward scanning.Has a row.RowAccess<T>Provide a way to access the inner buffer.Performs multiple mutations atomically on a single row.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).Rpc based connection registry.A RetryingCallable for RPC connection operations.Factory to create anRpcRetryingCaller
Runs an rpc'ingRetryingCallable
.Caller that goes to replica if the primary region does no answer within a configurable timeout.Used to perform Scan operations.Scanner operations such as create, next, etc.This class has the logic for handling scanners for regions with and without replicas.Used to separate the row constructing logic.ReceivesResult
for an asynchronous scan.The base interface for scan result consumer.Client proxy for SecureBulkLoadProtocolA ClusterConnection that will short-circuit RPC making direct invocations against the localhost if the invocation target is 'this' server; save on network and protobuf invocations.When we directly invokeRSRpcServices.get(org.apache.hbase.thirdparty.com.google.protobuf.RpcController, org.apache.hadoop.hbase.shaded.protobuf.generated.ClientProtos.GetRequest)
on the same RegionServer throughServerConnectionUtils.ShortCircuitingClusterConnection
in region CPs such asRegionObserver.postScannerOpen(org.apache.hadoop.hbase.coprocessor.ObserverContext<org.apache.hadoop.hbase.coprocessor.RegionCoprocessorEnvironment>, org.apache.hadoop.hbase.client.Scan, org.apache.hadoop.hbase.regionserver.RegionScanner)
to get other rows, theRegionScanner
created for the directlyRSRpcServices.get(org.apache.hbase.thirdparty.com.google.protobuf.RpcController, org.apache.hadoop.hbase.shaded.protobuf.generated.ClientProtos.GetRequest)
may not be closed until the outmost rpc call is completed if there is an outmostRpcCall
, and even worse , theServerCall.rpcCallback
may be override which would cause serious problem,so forServerConnectionUtils.ShortCircuitingClusterConnection.getClient(org.apache.hadoop.hbase.ServerName)
, if returnServerConnectionUtils.ShortCircuitingClusterConnection.localHostClient
,we would add a wrapper class to wrap it , which usingRpcServer.unsetCurrentCall()
and {RpcServer#setCurrentCall} to surround the scan and get method call,so theRegionScanner
created for the directlyRSRpcServices.get(org.apache.hbase.thirdparty.com.google.protobuf.RpcController, org.apache.hadoop.hbase.shaded.protobuf.generated.ClientProtos.GetRequest)
could be closed immediately,see HBASE-26812 for more.ServerConnectionUtils.ShortCircuitingClusterConnection.ClientServiceBlockingInterfaceWrapper.Operation<REQUEST,RESPONSE> Tracks the statistics for multiple regionsSelect server type i.e destination for RPC request associated with ring buffer.ServiceCaller<S,R> Delegate to a protobuf rpc call.A short-circuit connection that can bypass the RPC layer (serialization, deserialization, networking, etc..) when talking to a local masterHolds back the requests if they reach any thresholds.limit the heap size for each request.limit the number of rows for each request.Provide a way to control the flow of rows iteration.limit the heapsize of total submitted data.limit the max number of tasks in an AsyncProcess.Class for single action responseSlowLog params object that contains detailed info as params and region name : to be used for filter purposeThe POJO equivalent of HBaseProtos.SnapshotDescriptionPOJO representing the snapshot typeParent interface for an object to get updates about per-region statistics.Base class which provides clients with an RPC connection to call coprocessor endpointService
s.Used to communicate with a single HBase table.Deprecated.Since 2.4.0, will be removed in 4.0.0.Deprecated.Since 2.4.0, will be removed in 4.0.0.For creatingTable
instance.Base class for all table builders.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...Convenience class for composing an instance ofTableDescriptor
.TODO: make this private after removing the HTableDescriptorA Scanner which performs a scan over snapshot files.Represents table state.Deprecated.As of release 2.0.0, this will be removed in HBase 3.0.0.Class to help with parsing the version info.Deprecated.As of 2.6.0, replaced byRpcConnectionRegistry
, which is the default connection mechanism as of 3.0.0.