HBase REST API (on Cloudera) - SoojungHong/HBase GitHub Wiki

https://www.cloudera.com/documentation/enterprise/5-9-x/topics/admin_hbase_rest_api.html

The HBase REST server exposes endpoints that provide CRUD (create, read, update, delete) operations for each HBase process, as well as tables, regions, and namespaces. For a given endpoint, the HTTP verb controls the type of operation (create, read, update, or delete).

The examples in these tables use the curl command, and follow these guidelines: The HTTP verb is specified using the -X parameter. For GET queries, the Accept header is set to text/xml, which indicates that the client (curl) expects to receive responses formatted in XML. You can set it to text/json to receive JSON responses instead. For PUT, POST, and DELETE queries, the Content-Type header should be set only if data is also being sent with the -d parameter. If set, it should match the format of the data being sent, to enable the REST server to deserialize the data correctly. For more details about the curl command, see the documentation for the curl version that ships with your operating system.

Cluster-Wide Endpoints Endpoint HTTP Verb Description Example /version/cluster GET Version of HBase running on this cluster curl -vi -X GET
-H "Accept: text/xml"
"http://example.com:20550/version/cluster" /status/cluster GET Cluster status curl -vi -X GET
-H "Accept: text/xml"
"http://example.com:20550/status/cluster" / GET List of all nonsystem tables curl -vi -X GET
-H "Accept: text/xml"
"http://example.com:20550/"