Adds rows to HBase based on the contents of incoming JSON documents. Each FlowFile must contain a single UTF-8 encoded JSON document, and any FlowFiles where the root element is not a single document will be routed to failure. Each JSON field name and value will become a column qualifier and value of the HBase row. Any fields with a null value will be skipped, and fields with a complex value will be handled according to the Complex Field Strategy. The row id can be specified either directly on the processor through the Row Identifier property, or can be extracted from the JSON document by specifying the Row Identifier Field Name property. This processor will hold the contents of all FlowFiles for the given batch in memory at one time.
| Display Name | API Name | Default Value | Allowable Values | Description |
|---|
| HBase Client Service | HBase Client Service | | Controller Service API:
HBaseClientService
Implementations: HBase_1_1_2_ClientService
HBase_2_ClientService | Specifies the Controller Service to use for accessing HBase. |
| Table Name | Table Name | | | The name of the HBase Table to put data into
Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) |
| Row Identifier | Row Identifier | | | Specifies the Row ID to use when inserting data into HBase
Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) |
| Row Identifier Field Name | Row Identifier Field Name | | | Specifies the name of a JSON element whose value should be used as the row id for the given JSON document.
Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) |
| Row Identifier Encoding Strategy | Row Identifier Encoding Strategy | String | - String
 - Binary
| Specifies the data type of Row ID used when inserting data into HBase. The default behavior is to convert the row id to a UTF-8 byte array. Choosing Binary will convert a binary formatted string to the correct byte[] representation. The Binary option should be used if you are using Binary row keys in HBase |
| Column Family | Column Family | | | The Column Family to use when inserting data into HBase
Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) |
| Timestamp | timestamp | | | The timestamp for the cells being created in HBase. This field can be left blank and HBase will use the current time.
Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) |
| Batch Size | Batch Size | 25 | | The maximum number of FlowFiles to process in a single execution. The FlowFiles will be grouped by table, and a single Put per table will be performed. |
| Complex Field Strategy | Complex Field Strategy | Text | | Indicates how to handle complex fields, i.e. fields that do not have a single text value. |
| Field Encoding Strategy | Field Encoding Strategy | String | - String
- Bytes
| Indicates how to store the value of each field in HBase. The default behavior is to convert each value from the JSON to a String, and store the UTF-8 bytes. Choosing Bytes will interpret the type of each field from the JSON, and convert the value to the byte representation of that type, meaning an integer will be stored as the byte representation of that integer. |
Dynamic Properties allow the user to specify both the name and value of a property.