Static Apache HBase agent

Target HBase

Prerequisites

To have Gluesync working on your HBase instance you will need to have:

  • valid user credentials with permission to read and write to the target database

Setup via Web UI

  • Hostname / IP Address: DNS SVR record of your HBase cluster or IP Address of one of the nodes (automatic discovery of all other nodes is then applied);

  • Port: Optional, defaults to 60000;

  • Username: Username with read & write access role to the database;

  • Password: Password belonging to the given username.

Custom properties

  • columnInfoSeparator: (optional, defaults to :) It’s the user-defined separator used between family and column definitions;

  • maxRecoveryRetry: (optional, defaults to 3) It’s the number of max retries Gluesync will attempt before hanging up the connection with the Zookeeper services on the HBase side;

  • skipObjectsDeletion: (optional, defaults to false) If set to false tells Gluesync to skip any action that involves data deletion committed at the source level: Gluesync will propagate only events that involve Insert(s) and Update(s).

Setup via Rest APIs

Documentation available soon.

Data types infer

Apache HBase stores data in binary format, this means that for the engine knowing the precise data type and its length (especially when it comes to dates, floating point numbers, …​) is a guess. To boost performances and avoid any unwanted behavior while converting from binary to the destination data type we require the user to fill up this config piece to tell the engine how to handle the incoming data for a specific field.

Available supported data types:

Data type

STRING

INT

FLOAT

DOUBLE

LONG

BOOLEAN

LOCAL_DATE

LOCAL_DATE_TIME

LOCAL_TIME

OFFSET_DATE_TIME

Got Kerberos or other authentication services not covered here?

We’re working on improving the documentation and will be soon available all the possible combinations of authentication providers commonly used within HBase.