Performance Improvements
You can improve connector performance by using the KEY column as a filter in your queries or by using a load balancer to connect to HBase through REST gateways.
Wildcard Filtering
When you use the KEY column as a filter in queries, connector performance is improved and wildcards are supported in filtering. For example, you can use the filter foo*
to return key values including foo
, foobar
, and foo2
.
Load Balancer Support
When you use a load balancer to connect to HBase through REST gateways, the connector automatically redirects to the REST gateway reported by the load balancer. The connector detects if the current REST gateway fails, and attempts to reconnect to another REST gateway through the load balancer. You can specify the maximum number of connection retries that the connector attempts by setting the MaxRetryLimit
property in the connection string or in the DSN.
To use this feature, make sure that the load balancer returns the correct HTTP redirect request for GET and non-GET HTTP requests. For GET requests, the load balancer should request a relocation with HTTP code 302. For non-GET requests (such as PUT, POST, and DELETE), the load balancer should request a relocation with HTTP code 307.
- HTTP Path
- MaxRetryLimit
- Configuring the Driver on page 1
- Features