|Specifies the Controller Service to use for accessing HBase.|
|Distributed Cache Service||Controller Service API: |
|Specifies the Controller Service that should be used to maintain state about what has been pulled from HBase so that if a new node begins pulling data, it won't duplicate all of the work that has been done.|
|Table Name||The name of the HBase Table to put data into|
|Columns||A comma-separated list of "<colFamily>:<colQualifier>" pairs to return when scanning. To return all columns for a given family, leave off the qualifier such as "<colFamily1>,<colFamily2>".|
|Filter Expression||An HBase filter expression that will be applied to the scan. This property can not be used when also using the Columns property.|
|Initial Time Range||None||The time range to use on the first scan of a table. None will pull the entire table on the first scan, Current Time will pull entries from that point forward.|
|Character Set||UTF-8||Specifies which character set is used to encode the data in HBase|
|success||All FlowFiles are routed to this relationship|
Reads Attributes: None specified.
|hbase.table||The name of the HBase table that the data was pulled from|
|mime.type||Set to application/json to indicate that output is JSON|
|CLUSTER||After performing a fetching from HBase, stores a timestamp of the last-modified cell that was found. In addition, it stores the ID of the row(s) and the value of each cell that has that timestamp as its modification date. This is stored across the cluster and allows the next fetch to avoid duplicating data, even if this Processor is run on Primary Node only and the Primary Node changes.|
Restricted: This component is not restricted.
Input requirement: This component does not allow an incoming relationship.