PutHBaseJSON 2.3.0.4.10.0.0-147

Bundle
org.apache.nifi | nifi-hbase-nar
Description
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.
Tags
hadoop, hbase, json, put
Input Requirement
REQUIRED
Supports Sensitive Dynamic Properties
false
  • Additional Details for PutHBaseJSON 2.3.0.4.10.0.0-147

    PutHBaseJSON

    Visibility Labels

    This processor provides the ability to attach visibility labels to HBase Puts that it generates, if visibility labels are enabled on the HBase cluster. There are two ways to enable this:

    • Attributes on the flowfile.
    • Dynamic properties added to the processor.

    When the dynamic properties are defined on the processor, they will be the default value, but can be overridden by attributes set on the flowfile. The naming convention for both (property name and attribute name) is:

    • visibility.COLUMN_FAMILY - every column qualifier under the column family will get this.
    • visibility.COLUMN_FAMILY.COLUMN_VISIBILITY - the qualified column qualifier will be assigned this value.
Properties
Dynamic Properties
Relationships
Name Description
success A FlowFile is routed to this relationship after it has been successfully stored in HBase
failure A FlowFile is routed to this relationship if it cannot be sent to HBase