DeleteHBaseRow

Description:

Delete HBase records individually or in batches. The input can be a single row ID in the flowfile content, one ID per line, row IDs separated by a configurable separator character (default is a comma).

Tags:

delete, hbase

Properties:

In the list below, the names of required properties appear in bold. Any other properties (not in bold) are considered optional. The table also indicates any default values, and whether a property supports the NiFi Expression Language.

NameDefault ValueAllowable ValuesDescription
HBase Client ServiceController Service API:
HBaseClientService
Implementation: HBase_1_1_2_ClientService
Specifies the Controller Service to use for accessing HBase.
Table NameThe name of the HBase Table.
Supports Expression Language: true (will be evaluated using flow file attributes and variable registry)
Row IdentifierSpecifies the Row ID to use when deleting data into HBase
Supports Expression Language: true (will be evaluated using flow file attributes and variable registry)
Row ID Locationcontent
  • FlowFile content Get the row key(s) from the flowfile content.
  • FlowFile attributes Get the row key from an expression language statement.
The location of the row ID to use for building the delete. Can be from the content or an expression language statement.
Flowfile Fetch Count5The number of flowfiles to fetch per run.
Batch Size50The number of deletes to send per batch.
Delete Row Key Separator,The separator character(s) that separate multiple row keys when multiple row keys are provided in the flowfile content
Supports Expression Language: true (will be evaluated using flow file attributes and variable registry)
Visibility LabelIf visibility labels are enabled, a row cannot be deleted without supplying its visibility label(s) in the delete request. Note: this visibility label will be applied to all cells within the row that is specified. If some cells have different visibility labels, they will not be deleted. When that happens, the failure to delete will be considered a success because HBase does not report it as a failure.
Supports Expression Language: true (will be evaluated using flow file attributes and variable registry)
Character SetUTF-8The character set used to encode the row key for HBase.

Relationships:

NameDescription
successA FlowFile is routed to this relationship after it has been successfully stored in HBase
failureA FlowFile is routed to this relationship if it cannot be sent to HBase

Reads Attributes:

None specified.

Writes Attributes:

NameDescription
restart.indexIf a delete batch fails, 'restart.index' attribute is added to the FlowFile and sent to 'failure' relationship, so that this processor can retry from there when the same FlowFile is routed again.
rowkey.startThe first rowkey in the flowfile. Only written when using the flowfile's content for the row IDs.
rowkey.endThe last rowkey in the flowfile. Only written when using the flowfile's content for the row IDs.

State management:

This component does not store state.

Restricted:

This component is not restricted.

Input requirement:

This component requires an incoming relationship.

System Resource Considerations:

None specified.