Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase-nar/1.9.0/org.apache.nifi.hbase.GetHBase/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase-nar/1.9.0/org.apache.nifi.hbase.GetHBase/index.html?rev=1854109&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase-nar/1.9.0/org.apache.nifi.hbase.GetHBase/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase-nar/1.9.0/org.apache.nifi.hbase.GetHBase/index.html
 Fri Feb 22 01:03:44 2019
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>GetHBase</title><link rel="stylesheet" 
href="../../../../../css/component-usage.css" 
type="text/css"></link></head><script type="text/javascript">window.onload = 
function(){if(self==top) { document.getElementById('nameHeader').style.display 
= "inherit"; } }</script><body><h1 id="nameHeader" style="display: 
none;">GetHBase</h1><h2>Description: </h2><p>This Processor polls HBase for any 
records in the specified table. The processor keeps track of the timestamp of 
the cells that it receives, so that as new records are pushed to HBase, they 
will automatically be pulled. Each record is output in JSON format, as {"row": 
"&lt;row key&gt;", "cells": { "&lt;column 1 family&gt;:&lt;column 1 
qualifier&gt;": "&lt;cell 1 value&gt;", "&lt;column 2 family&gt;:&lt;column 2 
qualifier&gt;": "&lt;cell 2 value&gt;", ... }}. For each record received, a 
Provenance RECEIVE event is emitted with the format hbase://&lt;table name&gt;/&
 lt;row key&gt;, where &lt;row key&gt; is the UTF-8 encoded value of the row's 
key.</p><h3>Tags: </h3><p>hbase, get, ingest</p><h3>Properties: </h3><p>In the 
list below, the names of required properties appear in <strong>bold</strong>. 
Any other properties (not in bold) are considered optional. The table also 
indicates any default values, and whether a property supports the <a 
href="../../../../../html/expression-language-guide.html">NiFi Expression 
Language</a>.</p><table id="properties"><tr><th>Name</th><th>Default 
Value</th><th>Allowable Values</th><th>Description</th></tr><tr><td 
id="name"><strong>HBase Client Service</strong></td><td 
id="default-value"></td><td id="allowable-values"><strong>Controller Service 
API: </strong><br/>HBaseClientService<br/><strong>Implementations: </strong><a 
href="../../../nifi-hbase_2-client-service-nar/1.9.0/org.apache.nifi.hbase.HBase_2_ClientService/index.html">HBase_2_ClientService</a><br/><a
 href="../../../nifi-hbase_1_1_2-client-service-nar/1.
 
9.0/org.apache.nifi.hbase.HBase_1_1_2_ClientService/index.html">HBase_1_1_2_ClientService</a></td><td
 id="description">Specifies the Controller Service to use for accessing 
HBase.</td></tr><tr><td id="name">Distributed Cache Service</td><td 
id="default-value"></td><td id="allowable-values"><strong>Controller Service 
API: </strong><br/>DistributedMapCacheClient<br/><strong>Implementations: 
</strong><a 
href="../../../nifi-distributed-cache-services-nar/1.9.0/org.apache.nifi.distributed.cache.client.DistributedMapCacheClientService/index.html">DistributedMapCacheClientService</a><br/><a
 
href="../../../nifi-redis-nar/1.9.0/org.apache.nifi.redis.service.RedisDistributedMapCacheClientService/index.html">RedisDistributedMapCacheClientService</a><br/><a
 
href="../../../nifi-couchbase-nar/1.9.0/org.apache.nifi.couchbase.CouchbaseMapCacheClient/index.html">CouchbaseMapCacheClient</a><br/><a
 
href="../../../nifi-hbase_2-client-service-nar/1.9.0/org.apache.nifi.hbase.HBase_2_ClientMapCacheService
 /index.html">HBase_2_ClientMapCacheService</a><br/><a 
href="../../../nifi-hbase_1_1_2-client-service-nar/1.9.0/org.apache.nifi.hbase.HBase_1_1_2_ClientMapCacheService/index.html">HBase_1_1_2_ClientMapCacheService</a></td><td
 id="description">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.</td></tr><tr><td id="name"><strong>Table Name</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
name of the HBase Table to put data into</td></tr><tr><td 
id="name">Columns</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">A comma-separated list of 
"&lt;colFamily&gt;:&lt;colQualifier&gt;" pairs to return when scanning. To 
return all columns for a given family, leave off the qualifier such as 
"&lt;colFamily1&gt;,&lt;colFamily2&gt;".</td></tr><tr><td id="name">Autho
 rizations</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">The list of authorizations to pass to the scanner. This will 
be ignored if cell visibility labels are not in use.<br/><strong>Supports 
Expression Language: true (will be evaluated using variable registry 
only)</strong></td></tr><tr><td id="name">Filter Expression</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">An 
HBase filter expression that will be applied to the scan. This property can not 
be used when also using the Columns property.</td></tr><tr><td 
id="name"><strong>Initial Time Range</strong></td><td 
id="default-value">None</td><td 
id="allowable-values"><ul><li>None</li><li>Current Time</li></ul></td><td 
id="description">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.</td></tr><tr><td id="name"><strong>Character 
Set</strong></td><td id="def
 ault-value">UTF-8</td><td id="allowable-values"></td><td 
id="description">Specifies which character set is used to encode the data in 
HBase</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>All
 FlowFiles are routed to this relationship</td></tr></table><h3>Reads 
Attributes: </h3>None specified.<h3>Writes Attributes: </h3><table 
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>hbase.table</td><td>The
 name of the HBase table that the data was pulled 
from</td></tr><tr><td>mime.type</td><td>Set to application/json to indicate 
that output is JSON</td></tr></table><h3>State management: </h3><table 
id="stateful"><tr><th>Scope</th><th>Description</th></tr><tr><td>CLUSTER</td><td>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 modific
 ation 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.</td></tr></table><h3>Restricted: </h3>This component 
is not restricted.<h3>Input requirement: </h3>This component does not allow an 
incoming relationship.<h3>System Resource Considerations:</h3>None 
specified.</body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase-nar/1.9.0/org.apache.nifi.hbase.PutHBaseCell/additionalDetails.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase-nar/1.9.0/org.apache.nifi.hbase.PutHBaseCell/additionalDetails.html?rev=1854109&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase-nar/1.9.0/org.apache.nifi.hbase.PutHBaseCell/additionalDetails.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase-nar/1.9.0/org.apache.nifi.hbase.PutHBaseCell/additionalDetails.html
 Fri Feb 22 01:03:44 2019
@@ -0,0 +1,41 @@
+<!DOCTYPE html>
+<html lang="en">
+<!--
+  Licensed to the Apache Software Foundation (ASF) under one or more
+  contributor license agreements.  See the NOTICE file distributed with
+  this work for additional information regarding copyright ownership.
+  The ASF licenses this file to You under the Apache License, Version 2.0
+  (the "License"); you may not use this file except in compliance with
+  the License.  You may obtain a copy of the License at
+      http://www.apache.org/licenses/LICENSE-2.0
+  Unless required by applicable law or agreed to in writing, software
+  distributed under the License is distributed on an "AS IS" BASIS,
+  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+  See the License for the specific language governing permissions and
+  limitations under the License.
+-->
+<head>
+    <meta charset="utf-8" />
+    <title>PutHBaseCell</title>
+    <link rel="stylesheet" href="../../../../../css/component-usage.css" 
type="text/css" />
+</head>
+
+<body>
+<!-- Processor Documentation 
================================================== -->
+<h2>Visibility Labels</h2>
+<p>
+    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:
+</p>
+<ul>
+    <li>Attributes on the flowfile.</li>
+    <li>Dynamic properties added to the processor.</li>
+</ul>
+<p>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:</p>
+<ul>
+    <li>visibility.COLUMN_FAMILY - every column qualifier under the column 
family will get this.</li>
+    <li>visibility.COLUMN_FAMILY.COLUMN_VISIBILITY - the qualified column 
qualifier will be assigned this value.</li>
+</ul>
+</body>
+</html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase-nar/1.9.0/org.apache.nifi.hbase.PutHBaseCell/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase-nar/1.9.0/org.apache.nifi.hbase.PutHBaseCell/index.html?rev=1854109&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase-nar/1.9.0/org.apache.nifi.hbase.PutHBaseCell/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase-nar/1.9.0/org.apache.nifi.hbase.PutHBaseCell/index.html
 Fri Feb 22 01:03:44 2019
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>PutHBaseCell</title><link rel="stylesheet" 
href="../../../../../css/component-usage.css" 
type="text/css"></link></head><script type="text/javascript">window.onload = 
function(){if(self==top) { document.getElementById('nameHeader').style.display 
= "inherit"; } }</script><body><h1 id="nameHeader" style="display: 
none;">PutHBaseCell</h1><h2>Description: </h2><p>Adds the Contents of a 
FlowFile to HBase as the value of a single cell</p><p><a 
href="additionalDetails.html">Additional Details...</a></p><h3>Tags: 
</h3><p>hadoop, hbase</p><h3>Properties: </h3><p>In the list below, the names 
of required properties appear in <strong>bold</strong>. Any other properties 
(not in bold) are considered optional. The table also indicates any default 
values, and whether a property supports the <a 
href="../../../../../html/expression-language-guide.html">NiFi Expression 
Language</a>.</p><table id="properties"><tr><th>Name</th><th>D
 efault Value</th><th>Allowable Values</th><th>Description</th></tr><tr><td 
id="name"><strong>HBase Client Service</strong></td><td 
id="default-value"></td><td id="allowable-values"><strong>Controller Service 
API: </strong><br/>HBaseClientService<br/><strong>Implementations: </strong><a 
href="../../../nifi-hbase_2-client-service-nar/1.9.0/org.apache.nifi.hbase.HBase_2_ClientService/index.html">HBase_2_ClientService</a><br/><a
 
href="../../../nifi-hbase_1_1_2-client-service-nar/1.9.0/org.apache.nifi.hbase.HBase_1_1_2_ClientService/index.html">HBase_1_1_2_ClientService</a></td><td
 id="description">Specifies the Controller Service to use for accessing 
HBase.</td></tr><tr><td id="name"><strong>Table Name</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
name of the HBase Table to put data into<br/><strong>Supports Expression 
Language: true (will be evaluated using flow file attributes and variable 
registry)</strong></td></tr><tr><td id="name"
 >Row Identifier</td><td id="default-value"></td><td 
 >id="allowable-values"></td><td id="description">Specifies the Row ID to use 
 >when inserting data into HBase<br/><strong>Supports Expression Language: true 
 >(will be evaluated using flow file attributes and variable 
 >registry)</strong></td></tr><tr><td id="name">Row Identifier Encoding 
 >Strategy</td><td id="default-value">String</td><td 
 >id="allowable-values"><ul><li>String <img 
 >src="../../../../../html/images/iconInfo.png" alt="Stores the value of row id 
 >as a UTF-8 String." title="Stores the value of row id as a UTF-8 
 >String."></img></li><li>Binary <img 
 >src="../../../../../html/images/iconInfo.png" alt="Stores the value of the 
 >rows id as a binary byte array. It expects that the row id is a binary 
 >formatted string." title="Stores the value of the rows id as a binary byte 
 >array. It expects that the row id is a binary formatted 
 >string."></img></li></ul></td><td id="description">Specifies the data type of 
 >Row ID used when inserting data int
 o 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</td></tr><tr><td id="name"><strong>Column Family</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
Column Family to use when inserting data into HBase<br/><strong>Supports 
Expression Language: true (will be evaluated using flow file attributes and 
variable registry)</strong></td></tr><tr><td id="name"><strong>Column 
Qualifier</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The Column Qualifier to use 
when inserting data into HBase<br/><strong>Supports Expression Language: true 
(will be evaluated using flow file attributes and variable 
registry)</strong></td></tr><tr><td id="name">Timestamp</td><td 
id="default-value"></td><td id="allowable-values"></td
 ><td id="description">The timestamp for the cells being created in HBase. This 
 >field can be left blank and HBase will use the current 
 >time.<br/><strong>Supports Expression Language: true (will be evaluated using 
 >flow file attributes and variable registry)</strong></td></tr><tr><td 
 >id="name"><strong>Batch Size</strong></td><td id="default-value">25</td><td 
 >id="allowable-values"></td><td id="description">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.</td></tr></table><h3>Dynamic Properties: </h3><p>Dynamic 
 >Properties allow the user to specify both the name and value of a 
 >property.<table 
 >id="dynamic-properties"><tr><th>Name</th><th>Value</th><th>Description</th></tr><tr><td
 > id="name">visibility.&lt;COLUMN FAMILY&gt;</td><td id="value">visibility 
 >label for &lt;COLUMN FAMILY&gt;</td><td>Visibility label for everything under 
 >that column family when a specific label for a particular col
 umn qualifier is not available.<br/><strong>Supports Expression Language: true 
(will be evaluated using flow file attributes and variable 
registry)</strong></td></tr><tr><td id="name">visibility.&lt;COLUMN 
FAMILY&gt;.&lt;COLUMN QUALIFIER&gt;</td><td id="value">visibility label for 
&lt;COLUMN FAMILY&gt;:&lt;COLUMN QUALIFIER&gt;.</td><td>Visibility label for 
the specified column qualifier qualified by a configured column 
family.<br/><strong>Supports Expression Language: true (will be evaluated using 
flow file attributes and variable 
registry)</strong></td></tr></table></p><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>A
 FlowFile is routed to this relationship after it has been successfully stored 
in HBase</td></tr><tr><td>failure</td><td>A FlowFile is routed to this 
relationship if it cannot be sent to HBase</td></tr></table><h3>Reads 
Attributes: </h3>None specified.<h3>Writes Attributes: </h3>None 
specified.<h3>Stat
 e management: </h3>This component does not store state.<h3>Restricted: 
</h3>This component is not restricted.<h3>Input requirement: </h3>This 
component requires an incoming relationship.<h3>System Resource 
Considerations:</h3><table 
id="system-resource-considerations"><tr><th>Resource</th><th>Description</th></tr><tr><td>MEMORY</td><td>An
 instance of this component can cause high usage of this system resource.  
Multiple instances or high concurrency settings may result a degradation of 
performance.</td></tr></table></body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase-nar/1.9.0/org.apache.nifi.hbase.PutHBaseJSON/additionalDetails.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase-nar/1.9.0/org.apache.nifi.hbase.PutHBaseJSON/additionalDetails.html?rev=1854109&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase-nar/1.9.0/org.apache.nifi.hbase.PutHBaseJSON/additionalDetails.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase-nar/1.9.0/org.apache.nifi.hbase.PutHBaseJSON/additionalDetails.html
 Fri Feb 22 01:03:44 2019
@@ -0,0 +1,41 @@
+<!DOCTYPE html>
+<html lang="en">
+<!--
+  Licensed to the Apache Software Foundation (ASF) under one or more
+  contributor license agreements.  See the NOTICE file distributed with
+  this work for additional information regarding copyright ownership.
+  The ASF licenses this file to You under the Apache License, Version 2.0
+  (the "License"); you may not use this file except in compliance with
+  the License.  You may obtain a copy of the License at
+      http://www.apache.org/licenses/LICENSE-2.0
+  Unless required by applicable law or agreed to in writing, software
+  distributed under the License is distributed on an "AS IS" BASIS,
+  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+  See the License for the specific language governing permissions and
+  limitations under the License.
+-->
+<head>
+    <meta charset="utf-8" />
+    <title>PutHBaseJSON</title>
+    <link rel="stylesheet" href="../../../../../css/component-usage.css" 
type="text/css" />
+</head>
+
+<body>
+<!-- Processor Documentation 
================================================== -->
+<h2>Visibility Labels</h2>
+<p>
+    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:
+</p>
+<ul>
+    <li>Attributes on the flowfile.</li>
+    <li>Dynamic properties added to the processor.</li>
+</ul>
+<p>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:</p>
+<ul>
+    <li>visibility.COLUMN_FAMILY - every column qualifier under the column 
family will get this.</li>
+    <li>visibility.COLUMN_FAMILY.COLUMN_VISIBILITY - the qualified column 
qualifier will be assigned this value.</li>
+</ul>
+</body>
+</html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase-nar/1.9.0/org.apache.nifi.hbase.PutHBaseJSON/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase-nar/1.9.0/org.apache.nifi.hbase.PutHBaseJSON/index.html?rev=1854109&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase-nar/1.9.0/org.apache.nifi.hbase.PutHBaseJSON/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase-nar/1.9.0/org.apache.nifi.hbase.PutHBaseJSON/index.html
 Fri Feb 22 01:03:44 2019
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>PutHBaseJSON</title><link rel="stylesheet" 
href="../../../../../css/component-usage.css" 
type="text/css"></link></head><script type="text/javascript">window.onload = 
function(){if(self==top) { document.getElementById('nameHeader').style.display 
= "inherit"; } }</script><body><h1 id="nameHeader" style="display: 
none;">PutHBaseJSON</h1><h2>Description: </h2><p>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 ext
 racted 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.</p><p><a href="additionalDetails.html">Additional 
Details...</a></p><h3>Tags: </h3><p>hadoop, hbase, put, json</p><h3>Properties: 
</h3><p>In the list below, the names of required properties appear in 
<strong>bold</strong>. Any other properties (not in bold) are considered 
optional. The table also indicates any default values, and whether a property 
supports the <a href="../../../../../html/expression-language-guide.html">NiFi 
Expression Language</a>.</p><table id="properties"><tr><th>Name</th><th>Default 
Value</th><th>Allowable Values</th><th>Description</th></tr><tr><td 
id="name"><strong>HBase Client Service</strong></td><td 
id="default-value"></td><td id="allowable-values"><strong>Controller Service 
API: </strong><br/>HBaseClientService<br/><strong>Implementations: </strong><a 
href="../../../nifi-hbase
 
_2-client-service-nar/1.9.0/org.apache.nifi.hbase.HBase_2_ClientService/index.html">HBase_2_ClientService</a><br/><a
 
href="../../../nifi-hbase_1_1_2-client-service-nar/1.9.0/org.apache.nifi.hbase.HBase_1_1_2_ClientService/index.html">HBase_1_1_2_ClientService</a></td><td
 id="description">Specifies the Controller Service to use for accessing 
HBase.</td></tr><tr><td id="name"><strong>Table Name</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
name of the HBase Table to put data into<br/><strong>Supports Expression 
Language: true (will be evaluated using flow file attributes and variable 
registry)</strong></td></tr><tr><td id="name">Row Identifier</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Specifies the Row ID to use when inserting data into 
HBase<br/><strong>Supports Expression Language: true (will be evaluated using 
flow file attributes and variable registry)</strong></td></tr><tr><td 
id="name">R
 ow Identifier Field Name</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Specifies the name of a JSON 
element whose value should be used as the row id for the given JSON 
document.<br/><strong>Supports Expression Language: true (will be evaluated 
using flow file attributes and variable registry)</strong></td></tr><tr><td 
id="name">Row Identifier Encoding Strategy</td><td 
id="default-value">String</td><td id="allowable-values"><ul><li>String <img 
src="../../../../../html/images/iconInfo.png" alt="Stores the value of row id 
as a UTF-8 String." title="Stores the value of row id as a UTF-8 
String."></img></li><li>Binary <img 
src="../../../../../html/images/iconInfo.png" alt="Stores the value of the rows 
id as a binary byte array. It expects that the row id is a binary formatted 
string." title="Stores the value of the rows id as a binary byte array. It 
expects that the row id is a binary formatted string."></img></li></ul></td><td 
id="description">Speci
 fies 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</td></tr><tr><td id="name"><strong>Column Family</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
Column Family to use when inserting data into HBase<br/><strong>Supports 
Expression Language: true (will be evaluated using flow file attributes and 
variable registry)</strong></td></tr><tr><td id="name">Timestamp</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
timestamp for the cells being created in HBase. This field can be left blank 
and HBase will use the current time.<br/><strong>Supports Expression Language: 
true (will be evaluated using flow file attributes and variable 
registry)</strong></td></t
 r><tr><td id="name"><strong>Batch Size</strong></td><td 
id="default-value">25</td><td id="allowable-values"></td><td 
id="description">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.</td></tr><tr><td id="name"><strong>Complex Field 
Strategy</strong></td><td id="default-value">Text</td><td 
id="allowable-values"><ul><li>Fail <img 
src="../../../../../html/images/iconInfo.png" alt="Route entire FlowFile to 
failure if any elements contain complex values." title="Route entire FlowFile 
to failure if any elements contain complex values."></img></li><li>Warn <img 
src="../../../../../html/images/iconInfo.png" alt="Provide a warning and do not 
include field in row sent to HBase." title="Provide a warning and do not 
include field in row sent to HBase."></img></li><li>Ignore <img 
src="../../../../../html/images/iconInfo.png" alt="Silently ignore and do not 
include in row sent to HBase." title="
 Silently ignore and do not include in row sent to HBase."></img></li><li>Text 
<img src="../../../../../html/images/iconInfo.png" alt="Use the string 
representation of the complex field as the value of the given column." 
title="Use the string representation of the complex field as the value of the 
given column."></img></li></ul></td><td id="description">Indicates how to 
handle complex fields, i.e. fields that do not have a single text 
value.</td></tr><tr><td id="name"><strong>Field Encoding 
Strategy</strong></td><td id="default-value">String</td><td 
id="allowable-values"><ul><li>String <img 
src="../../../../../html/images/iconInfo.png" alt="Stores the value of each 
field as a UTF-8 String." title="Stores the value of each field as a UTF-8 
String."></img></li><li>Bytes <img 
src="../../../../../html/images/iconInfo.png" alt="Stores the value of each 
field as the byte representation of the type derived from the JSON." 
title="Stores the value of each field as the byte representation of t
 he type derived from the JSON."></img></li></ul></td><td 
id="description">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.</td></tr></table><h3>Dynamic Properties: </h3><p>Dynamic Properties 
allow the user to specify both the name and value of a property.<table 
id="dynamic-properties"><tr><th>Name</th><th>Value</th><th>Description</th></tr><tr><td
 id="name">visibility.&lt;COLUMN FAMILY&gt;</td><td id="value">visibility label 
for &lt;COLUMN FAMILY&gt;</td><td>Visibility label for everything under that 
column family when a specific label for a particular column qualifier is not 
available.<br/><strong>Supports Expression Language: true (will be evaluated 
using flow file attr
 ibutes and variable registry)</strong></td></tr><tr><td 
id="name">visibility.&lt;COLUMN FAMILY&gt;.&lt;COLUMN QUALIFIER&gt;</td><td 
id="value">visibility label for &lt;COLUMN FAMILY&gt;:&lt;COLUMN 
QUALIFIER&gt;.</td><td>Visibility label for the specified column qualifier 
qualified by a configured column family.<br/><strong>Supports Expression 
Language: true (will be evaluated using flow file attributes and variable 
registry)</strong></td></tr></table></p><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>A
 FlowFile is routed to this relationship after it has been successfully stored 
in HBase</td></tr><tr><td>failure</td><td>A FlowFile is routed to this 
relationship if it cannot be sent to HBase</td></tr></table><h3>Reads 
Attributes: </h3>None specified.<h3>Writes Attributes: </h3>None 
specified.<h3>State management: </h3>This component does not store 
state.<h3>Restricted: </h3>This component is not restricted.<h3>Input
  requirement: </h3>This component requires an incoming relationship.<h3>System 
Resource Considerations:</h3>None specified.</body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase-nar/1.9.0/org.apache.nifi.hbase.PutHBaseRecord/additionalDetails.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase-nar/1.9.0/org.apache.nifi.hbase.PutHBaseRecord/additionalDetails.html?rev=1854109&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase-nar/1.9.0/org.apache.nifi.hbase.PutHBaseRecord/additionalDetails.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase-nar/1.9.0/org.apache.nifi.hbase.PutHBaseRecord/additionalDetails.html
 Fri Feb 22 01:03:44 2019
@@ -0,0 +1,113 @@
+<!DOCTYPE html>
+<html lang="en">
+<!--
+  Licensed to the Apache Software Foundation (ASF) under one or more
+  contributor license agreements.  See the NOTICE file distributed with
+  this work for additional information regarding copyright ownership.
+  The ASF licenses this file to You under the Apache License, Version 2.0
+  (the "License"); you may not use this file except in compliance with
+  the License.  You may obtain a copy of the License at
+      http://www.apache.org/licenses/LICENSE-2.0
+  Unless required by applicable law or agreed to in writing, software
+  distributed under the License is distributed on an "AS IS" BASIS,
+  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+  See the License for the specific language governing permissions and
+  limitations under the License.
+-->
+<head>
+    <meta charset="utf-8" />
+    <title>PutHBaseRecord</title>
+    <link rel="stylesheet" href="../../../../../css/component-usage.css" 
type="text/css" />
+</head>
+
+<body>
+<!-- Processor Documentation 
================================================== -->
+<h2>Visibility Labels:</h2>
+<p>
+    PutHBaseRecord provides the ability to define a branch of the record as a 
map which contains an association between
+    column qualifiers and the visibility label that they should have assigned 
to them.
+</p>
+<h3>Example Schema</h3>
+<pre>
+{
+    "type": "record",
+    "name": "SampleRecord",
+    "fields": [
+        { "name": "name", "type": "string" },
+        { "name": "address", "type": "string" },
+        { "name": "dob", "type": "string" },
+        { "name": "attendingPhysician", "type": "string" },
+        { "name": "accountNumber", "type": "string" },
+        { "name": "visibility_labels", "type": { "type" : "map", "values": 
"string" } }
+    ]
+}
+</pre>
+<h3>Example Record</h3>
+<pre>
+{
+    "name": "John Smith",
+    "address": "12345 Main Street",
+    "dob": "1970-01-01",
+    "attendingPhysician": "Dr. Jane Doe",
+    "accountNumber": "1234-567-890-ABC",
+    "visibility_labels": {
+        "name": "OPEN",
+        "address": "PII",
+        "dob": "PII",
+        "attendingPhysician": "PII&amp;PHI",
+        "accountNumber": "PII&amp;BILLING"
+    }
+}
+</pre>
+<h3>Results in HBase</h3>
+<p>Example is for row with ID <em>patient-1</em> and column family 
<em>patient</em></p>
+<table>
+    <thead>
+        <tr>
+            <th>Row</th>
+            <th>Value</th>
+            <th>Visibility</th>
+        </tr>
+    </thead>
+    <tbody>
+        <tr>
+            <td>patient-1:patient:name</td>
+            <td>John Smith</td>
+            <td>OPEN</td>
+        </tr>
+        <tr>
+            <td>patient-1:patient:address</td>
+            <td>12345 Main Street</td>
+            <td>PII</td>
+        </tr>
+        <tr>
+            <td>patient-1:patient:</td>
+            <td>1970-01-01</td>
+            <td>PII</td>
+        </tr>
+        <tr>
+            <td>patient-1:patient:attendingPhysician</td>
+            <td>Dr. Jane Doe</td>
+            <td>PII&amp;PHI</td>
+        </tr>
+        <tr>
+            <td>patient-1:patient:accountNumber</td>
+            <td>1234-567-890-ABC</td>
+            <td>PII&amp;BILLING</td>
+        </tr>
+    </tbody>
+</table>
+<p>In addition to the branch for visibility labels, the same methods used for 
PutHBaseCell and PutHBaseJSON can be used.
+They are:</p>
+<ul>
+    <li>Attributes on the flowfile.</li>
+    <li>Dynamic properties added to the processor.</li>
+</ul>
+<p>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:</p>
+<ul>
+    <li>visibility.COLUMN_FAMILY - every column qualifier under the column 
family will get this.</li>
+    <li>visibility.COLUMN_FAMILY.COLUMN_VISIBILITY - the qualified column 
qualifier will be assigned this value.</li>
+</ul>
+</body>
+</html>

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase-nar/1.9.0/org.apache.nifi.hbase.PutHBaseRecord/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase-nar/1.9.0/org.apache.nifi.hbase.PutHBaseRecord/index.html?rev=1854109&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase-nar/1.9.0/org.apache.nifi.hbase.PutHBaseRecord/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase-nar/1.9.0/org.apache.nifi.hbase.PutHBaseRecord/index.html
 Fri Feb 22 01:03:44 2019
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>PutHBaseRecord</title><link rel="stylesheet" 
href="../../../../../css/component-usage.css" 
type="text/css"></link></head><script type="text/javascript">window.onload = 
function(){if(self==top) { document.getElementById('nameHeader').style.display 
= "inherit"; } }</script><body><h1 id="nameHeader" style="display: 
none;">PutHBaseRecord</h1><h2>Description: </h2><p>Adds rows to HBase based on 
the contents of a flowfile using a configured record reader.</p><p><a 
href="additionalDetails.html">Additional Details...</a></p><h3>Tags: 
</h3><p>hadoop, hbase, put, record</p><h3>Properties: </h3><p>In the list 
below, the names of required properties appear in <strong>bold</strong>. Any 
other properties (not in bold) are considered optional. The table also 
indicates any default values, and whether a property supports the <a 
href="../../../../../html/expression-language-guide.html">NiFi Expression 
Language</a>.</p><table id=
 "properties"><tr><th>Name</th><th>Default Value</th><th>Allowable 
Values</th><th>Description</th></tr><tr><td id="name"><strong>Record 
Reader</strong></td><td id="default-value"></td><td 
id="allowable-values"><strong>Controller Service API: 
</strong><br/>RecordReaderFactory<br/><strong>Implementations: </strong><a 
href="../../../nifi-record-serialization-services-nar/1.9.0/org.apache.nifi.json.JsonTreeReader/index.html">JsonTreeReader</a><br/><a
 
href="../../../nifi-record-serialization-services-nar/1.9.0/org.apache.nifi.xml.XMLReader/index.html">XMLReader</a><br/><a
 
href="../../../nifi-record-serialization-services-nar/1.9.0/org.apache.nifi.json.JsonPathReader/index.html">JsonPathReader</a><br/><a
 
href="../../../nifi-record-serialization-services-nar/1.9.0/org.apache.nifi.syslog.Syslog5424Reader/index.html">Syslog5424Reader</a><br/><a
 
href="../../../nifi-record-serialization-services-nar/1.9.0/org.apache.nifi.grok.GrokReader/index.html">GrokReader</a><br/><a
 href="../../../nifi-scri
 
pting-nar/1.9.0/org.apache.nifi.record.script.ScriptedReader/index.html">ScriptedReader</a><br/><a
 
href="../../../nifi-record-serialization-services-nar/1.9.0/org.apache.nifi.avro.AvroReader/index.html">AvroReader</a><br/><a
 
href="../../../nifi-record-serialization-services-nar/1.9.0/org.apache.nifi.csv.CSVReader/index.html">CSVReader</a><br/><a
 
href="../../../nifi-record-serialization-services-nar/1.9.0/org.apache.nifi.syslog.SyslogReader/index.html">SyslogReader</a></td><td
 id="description">Specifies the Controller Service to use for parsing incoming 
data and determining the data's schema</td></tr><tr><td id="name"><strong>HBase 
Client Service</strong></td><td id="default-value"></td><td 
id="allowable-values"><strong>Controller Service API: 
</strong><br/>HBaseClientService<br/><strong>Implementations: </strong><a 
href="../../../nifi-hbase_2-client-service-nar/1.9.0/org.apache.nifi.hbase.HBase_2_ClientService/index.html">HBase_2_ClientService</a><br/><a
 href="../../../nifi-hbase_1_
 
1_2-client-service-nar/1.9.0/org.apache.nifi.hbase.HBase_1_1_2_ClientService/index.html">HBase_1_1_2_ClientService</a></td><td
 id="description">Specifies the Controller Service to use for accessing 
HBase.</td></tr><tr><td id="name"><strong>Table Name</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
name of the HBase Table to put data into<br/><strong>Supports Expression 
Language: true (will be evaluated using flow file attributes and variable 
registry)</strong></td></tr><tr><td id="name"><strong>Row Identifier Field 
Name</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Specifies the name of a record 
field whose value should be used as the row id for the given 
record.<br/><strong>Supports Expression Language: true (will be evaluated using 
flow file attributes and variable registry)</strong></td></tr><tr><td 
id="name">Row Identifier Encoding Strategy</td><td 
id="default-value">String</td><td id
 ="allowable-values"><ul><li>String <img 
src="../../../../../html/images/iconInfo.png" alt="Stores the value of row id 
as a UTF-8 String." title="Stores the value of row id as a UTF-8 
String."></img></li><li>Binary <img 
src="../../../../../html/images/iconInfo.png" alt="Stores the value of the rows 
id as a binary byte array. It expects that the row id is a binary formatted 
string." title="Stores the value of the rows id as a binary byte array. It 
expects that the row id is a binary formatted string."></img></li></ul></td><td 
id="description">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</td></tr><tr><td id="name"><strong>Null Field 
Strategy</strong></td><td id="default-value">skip-field</td><td 
id="allowable-values"><ul><li>Em
 pty Bytes <img src="../../../../../html/images/iconInfo.png" alt="Use empty 
bytes. This can be used to overwrite existing fields or to put an empty 
placeholder value if you want every field to be present even if it has a null 
value." title="Use empty bytes. This can be used to overwrite existing fields 
or to put an empty placeholder value if you want every field to be present even 
if it has a null value."></img></li><li>Skip Field <img 
src="../../../../../html/images/iconInfo.png" alt="Skip the field (don't 
process it at all)." title="Skip the field (don't process it at 
all)."></img></li></ul></td><td id="description">Handle null field values as 
either an empty string or skip them altogether.</td></tr><tr><td 
id="name"><strong>Column Family</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The Column Family to use when 
inserting data into HBase<br/><strong>Supports Expression Language: true (will 
be evaluated using flow file attributes and 
 variable registry)</strong></td></tr><tr><td id="name">Default Visibility 
String</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">When using visibility labels, any value set in this field will 
be applied to all cells that are written unless an attribute with the 
convention "visibility.COLUMN_FAMILY.COLUMN_QUALIFIER" is present on the 
flowfile. If this field is left blank, it will be assumed that no visibility is 
to be set unless visibility-related attributes are set. NOTE: this 
configuration will have no effect on your data if you have not enabled 
visibility labels in the HBase cluster.<br/><strong>Supports Expression 
Language: true (will be evaluated using flow file attributes and variable 
registry)</strong></td></tr><tr><td id="name">Visibility String Record Path 
Root</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">A record path that points to part of the record which contains 
a path to a mapping of visibility 
 strings to record paths</td></tr><tr><td id="name">Timestamp Field 
Name</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">Specifies the name of a record field whose value should be 
used as the timestamp for the cells in HBase. The value of this field must be a 
number, string, or date that can be converted to a long. If this field is left 
blank, HBase will use the current time.<br/><strong>Supports Expression 
Language: true (will be evaluated using flow file attributes and variable 
registry)</strong></td></tr><tr><td id="name"><strong>Batch 
Size</strong></td><td id="default-value">1000</td><td 
id="allowable-values"></td><td id="description">The maximum number of records 
to be sent to HBase at any one time from the record set.</td></tr><tr><td 
id="name"><strong>Complex Field Strategy</strong></td><td 
id="default-value">Text</td><td id="allowable-values"><ul><li>Fail <img 
src="../../../../../html/images/iconInfo.png" alt="Route entire FlowFile to 
failu
 re if any elements contain complex values." title="Route entire FlowFile to 
failure if any elements contain complex values."></img></li><li>Warn <img 
src="../../../../../html/images/iconInfo.png" alt="Provide a warning and do not 
include field in row sent to HBase." title="Provide a warning and do not 
include field in row sent to HBase."></img></li><li>Ignore <img 
src="../../../../../html/images/iconInfo.png" alt="Silently ignore and do not 
include in row sent to HBase." title="Silently ignore and do not include in row 
sent to HBase."></img></li><li>Text <img 
src="../../../../../html/images/iconInfo.png" alt="Use the string 
representation of the complex field as the value of the given column." 
title="Use the string representation of the complex field as the value of the 
given column."></img></li></ul></td><td id="description">Indicates how to 
handle complex fields, i.e. fields that do not have a single text 
value.</td></tr><tr><td id="name"><strong>Field Encoding Strategy</strong></
 td><td id="default-value">String</td><td id="allowable-values"><ul><li>String 
<img src="../../../../../html/images/iconInfo.png" alt="Stores the value of 
each field as a UTF-8 String." title="Stores the value of each field as a UTF-8 
String."></img></li><li>Bytes <img 
src="../../../../../html/images/iconInfo.png" alt="Stores the value of each 
field as the byte representation of the type derived from the record." 
title="Stores the value of each field as the byte representation of the type 
derived from the record."></img></li></ul></td><td id="description">Indicates 
how to store the value of each field in HBase. The default behavior is to 
convert each value from the record to a String, and store the UTF-8 bytes. 
Choosing Bytes will interpret the type of each field from the record, and 
convert the value to the byte representation of that type, meaning an integer 
will be stored as the byte representation of that 
integer.</td></tr></table><h3>Dynamic Properties: </h3><p>Dynamic Propertie
 s allow the user to specify both the name and value of a property.<table 
id="dynamic-properties"><tr><th>Name</th><th>Value</th><th>Description</th></tr><tr><td
 id="name">visibility.&lt;COLUMN FAMILY&gt;</td><td id="value">visibility label 
for &lt;COLUMN FAMILY&gt;</td><td>Visibility label for everything under that 
column family when a specific label for a particular column qualifier is not 
available.<br/><strong>Supports Expression Language: true (will be evaluated 
using flow file attributes and variable registry)</strong></td></tr><tr><td 
id="name">visibility.&lt;COLUMN FAMILY&gt;.&lt;COLUMN QUALIFIER&gt;</td><td 
id="value">visibility label for &lt;COLUMN FAMILY&gt;:&lt;COLUMN 
QUALIFIER&gt;.</td><td>Visibility label for the specified column qualifier 
qualified by a configured column family.<br/><strong>Supports Expression 
Language: true (will be evaluated using flow file attributes and variable 
registry)</strong></td></tr></table></p><h3>Relationships: </h3><table 
id="relationship
 s"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>A 
FlowFile is routed to this relationship after it has been successfully stored 
in HBase</td></tr><tr><td>failure</td><td>A FlowFile is routed to this 
relationship if it cannot be sent to HBase</td></tr></table><h3>Reads 
Attributes: </h3><table 
id="reads-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>restart.index</td><td>Reads
 restart.index when it needs to replay part of a record set that did not get 
into HBase.</td></tr></table><h3>Writes Attributes: </h3><table 
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>restart.index</td><td>Writes
 restart.index when a batch fails to be insert into 
HBase</td></tr></table><h3>State management: </h3>This component does not store 
state.<h3>Restricted: </h3>This component is not restricted.<h3>Input 
requirement: </h3>This component requires an incoming relationship.<h3>System 
Resource Considerations:</h3>None specified.</body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase-nar/1.9.0/org.apache.nifi.hbase.ScanHBase/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase-nar/1.9.0/org.apache.nifi.hbase.ScanHBase/index.html?rev=1854109&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase-nar/1.9.0/org.apache.nifi.hbase.ScanHBase/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase-nar/1.9.0/org.apache.nifi.hbase.ScanHBase/index.html
 Fri Feb 22 01:03:44 2019
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ScanHBase</title><link rel="stylesheet" 
href="../../../../../css/component-usage.css" 
type="text/css"></link></head><script type="text/javascript">window.onload = 
function(){if(self==top) { document.getElementById('nameHeader').style.display 
= "inherit"; } }</script><body><h1 id="nameHeader" style="display: 
none;">ScanHBase</h1><h2>Description: </h2><p>Scans and fetches rows from an 
HBase table. This processor may be used to fetch rows from hbase table by 
specifying a range of rowkey values (start and/or end ),by time range, by 
filter expression, or any combination of them. Order of records can be 
controlled by a property ReversedNumber of rows retrieved by the processor can 
be limited.</p><h3>Tags: </h3><p>hbase, scan, fetch, get</p><h3>Properties: 
</h3><p>In the list below, the names of required properties appear in 
<strong>bold</strong>. Any other properties (not in bold) are considered 
optional. The table a
 lso indicates any default values, and whether a property supports the <a 
href="../../../../../html/expression-language-guide.html">NiFi Expression 
Language</a>.</p><table id="properties"><tr><th>Name</th><th>Default 
Value</th><th>Allowable Values</th><th>Description</th></tr><tr><td 
id="name"><strong>HBase Client Service</strong></td><td 
id="default-value"></td><td id="allowable-values"><strong>Controller Service 
API: </strong><br/>HBaseClientService<br/><strong>Implementations: </strong><a 
href="../../../nifi-hbase_2-client-service-nar/1.9.0/org.apache.nifi.hbase.HBase_2_ClientService/index.html">HBase_2_ClientService</a><br/><a
 
href="../../../nifi-hbase_1_1_2-client-service-nar/1.9.0/org.apache.nifi.hbase.HBase_1_1_2_ClientService/index.html">HBase_1_1_2_ClientService</a></td><td
 id="description">Specifies the Controller Service to use for accessing 
HBase.</td></tr><tr><td id="name"><strong>Table Name</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="
 description">The name of the HBase Table to fetch from.<br/><strong>Supports 
Expression Language: true (will be evaluated using flow file attributes and 
variable registry)</strong></td></tr><tr><td id="name">Authorizations</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
list of authorizations to pass to the scanner. This will be ignored if cell 
visibility labels are not in use.<br/><strong>Supports Expression Language: 
true (will be evaluated using flow file attributes and variable 
registry)</strong></td></tr><tr><td id="name">Start rowkey</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
rowkey to start scan from.<br/><strong>Supports Expression Language: true (will 
be evaluated using flow file attributes and variable 
registry)</strong></td></tr><tr><td id="name">End rowkey</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
row key to end scan by.<br/><strong>Supports 
 Expression Language: true (will be evaluated using flow file attributes and 
variable registry)</strong></td></tr><tr><td id="name">Time range min</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Time range min value. Both min and max values for time range 
should be either blank or provided.<br/><strong>Supports Expression Language: 
true (will be evaluated using flow file attributes and variable 
registry)</strong></td></tr><tr><td id="name">Time range max</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Time range max value. Both min and max values for time range 
should be either blank or provided.<br/><strong>Supports Expression Language: 
true (will be evaluated using flow file attributes and variable 
registry)</strong></td></tr><tr><td id="name">Limit rows</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Limit number of rows retrieved by scan.<br/><strong>Supports 
Expression Lan
 guage: true (will be evaluated using flow file attributes and variable 
registry)</strong></td></tr><tr><td id="name">Reversed order</td><td 
id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Set whether this scan is a reversed one. This is false by 
default which means forward(normal) scan.</td></tr><tr><td id="name">Max rows 
per flow file</td><td id="default-value">0</td><td 
id="allowable-values"></td><td id="description">Limits number of rows in single 
flow file content. Set to 0 to avoid multiple flow files.<br/><strong>Supports 
Expression Language: true (will be evaluated using flow file attributes and 
variable registry)</strong></td></tr><tr><td id="name">Filter 
expression</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">An HBase filter expression that will be applied to the scan. 
This property can not be used when also using the Columns property. Example: 
"ValueFilter( =, 'binar
 yprefix:commit' )"<br/><strong>Supports Expression Language: true (will be 
evaluated using flow file attributes and variable 
registry)</strong></td></tr><tr><td id="name">Columns</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">An 
optional comma-separated list of "&lt;colFamily&gt;:&lt;colQualifier&gt;" pairs 
to fetch. To return all columns for a given family, leave off the qualifier 
such as "&lt;colFamily1&gt;,&lt;colFamily2&gt;".<br/><strong>Supports 
Expression Language: true (will be evaluated using flow file attributes and 
variable registry)</strong></td></tr><tr><td id="name"><strong>JSON 
Format</strong></td><td id="default-value">full-row</td><td 
id="allowable-values"><ul><li>full-row <img 
src="../../../../../html/images/iconInfo.png" alt="Creates a JSON document with 
the format: {&quot;row&quot;:&lt;row-id&gt;, 
&quot;cells&quot;:[{&quot;fam&quot;:&lt;col-fam&gt;, 
&quot;qual&quot;:&lt;col-val&gt;, &quot;val&quot;:&lt;value&gt;, &quot;ts&quot;
 :&lt;timestamp&gt;}]}." title="Creates a JSON document with the format: 
{&quot;row&quot;:&lt;row-id&gt;, 
&quot;cells&quot;:[{&quot;fam&quot;:&lt;col-fam&gt;, 
&quot;qual&quot;:&lt;col-val&gt;, &quot;val&quot;:&lt;value&gt;, 
&quot;ts&quot;:&lt;timestamp&gt;}]}."></img></li><li>col-qual-and-val <img 
src="../../../../../html/images/iconInfo.png" alt="Creates a JSON document with 
the format: {&quot;&lt;col-qual&gt;&quot;:&quot;&lt;value&gt;&quot;, 
&quot;&lt;col-qual&gt;&quot;:&quot;&lt;value&gt;&quot;." title="Creates a JSON 
document with the format: 
{&quot;&lt;col-qual&gt;&quot;:&quot;&lt;value&gt;&quot;, 
&quot;&lt;col-qual&gt;&quot;:&quot;&lt;value&gt;&quot;."></img></li></ul></td><td
 id="description">Specifies how to represent the HBase row as a JSON 
document.</td></tr><tr><td id="name"><strong>Encode Character 
Set</strong></td><td id="default-value">UTF-8</td><td 
id="allowable-values"></td><td id="description">The character set used to 
encode the JSON representation of the row.</td><
 /tr><tr><td id="name"><strong>Decode Character Set</strong></td><td 
id="default-value">UTF-8</td><td id="allowable-values"></td><td 
id="description">The character set used to decode data from 
HBase.</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>All
 successful fetches are routed to this 
relationship.</td></tr><tr><td>failure</td><td>All failed fetches are routed to 
this relationship.</td></tr><tr><td>original</td><td>The original input file 
will be routed to this destination, even if no rows are retrieved based on 
provided conditions.</td></tr></table><h3>Reads Attributes: </h3>None 
specified.<h3>Writes Attributes: </h3><table 
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>hbase.table</td><td>The
 name of the HBase table that the row was fetched 
from</td></tr><tr><td>mime.type</td><td>Set to application/json when using a 
Destination of flowfile-content, not set or modified 
 otherwise</td></tr><tr><td>hbase.rows.count</td><td>Number of rows in the 
content of given flow 
file</td></tr><tr><td>scanhbase.results.found</td><td>Indicates whether at 
least one row has been found in given hbase table with provided conditions. 
Could be null (not present) if transfered to FAILURE</td></tr></table><h3>State 
management: </h3>This component does not store state.<h3>Restricted: </h3>This 
component is not restricted.<h3>Input requirement: </h3>This component requires 
an incoming relationship.<h3>System Resource Considerations:</h3>None 
specified.</body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase_1_1_2-client-service-nar/1.9.0/org.apache.nifi.hbase.HBase_1_1_2_ClientMapCacheService/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase_1_1_2-client-service-nar/1.9.0/org.apache.nifi.hbase.HBase_1_1_2_ClientMapCacheService/index.html?rev=1854109&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase_1_1_2-client-service-nar/1.9.0/org.apache.nifi.hbase.HBase_1_1_2_ClientMapCacheService/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase_1_1_2-client-service-nar/1.9.0/org.apache.nifi.hbase.HBase_1_1_2_ClientMapCacheService/index.html
 Fri Feb 22 01:03:44 2019
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>HBase_1_1_2_ClientMapCacheService</title><link 
rel="stylesheet" href="../../../../../css/component-usage.css" 
type="text/css"></link></head><script type="text/javascript">window.onload = 
function(){if(self==top) { document.getElementById('nameHeader').style.display 
= "inherit"; } }</script><body><h1 id="nameHeader" style="display: 
none;">HBase_1_1_2_ClientMapCacheService</h1><h2>Description: </h2><p>Provides 
the ability to use an HBase table as a cache, in place of a 
DistributedMapCache. Uses a HBase_1_1_2_ClientService controller to communicate 
with HBase.</p><h3>Tags: </h3><p>distributed, cache, state, map, cluster, 
hbase</p><h3>Properties: </h3><p>In the list below, the names of required 
properties appear in <strong>bold</strong>. Any other properties (not in bold) 
are considered optional. The table also indicates any default values, and 
whether a property supports the <a href="../../../../../html/expression
 -language-guide.html">NiFi Expression Language</a>.</p><table 
id="properties"><tr><th>Name</th><th>Default Value</th><th>Allowable 
Values</th><th>Description</th></tr><tr><td id="name"><strong>HBase Cache Table 
Name</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Name of the table on HBase to 
use for the cache.<br/><strong>Supports Expression Language: true (will be 
evaluated using variable registry only)</strong></td></tr><tr><td 
id="name">Authorizations</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The list of authorization 
tokens to be used with cell visibility if it is enabled. These will be used to 
override the default authorization list for the user accessing 
HBase.</td></tr><tr><td id="name"><strong>HBase Client Service</strong></td><td 
id="default-value"></td><td id="allowable-values"><strong>Controller Service 
API: </strong><br/>HBaseClientService<br/><strong>Implementations: </strong><a 
href
 
="../../../nifi-hbase_2-client-service-nar/1.9.0/org.apache.nifi.hbase.HBase_2_ClientService/index.html">HBase_2_ClientService</a><br/><a
 
href="../org.apache.nifi.hbase.HBase_1_1_2_ClientService/index.html">HBase_1_1_2_ClientService</a></td><td
 id="description">Specifies the HBase Client Controller Service to use for 
accessing HBase.</td></tr><tr><td id="name"><strong>HBase Column 
Family</strong></td><td id="default-value">f</td><td 
id="allowable-values"></td><td id="description">Name of the column family on 
HBase to use for the cache.<br/><strong>Supports Expression Language: true 
(will be evaluated using variable registry only)</strong></td></tr><tr><td 
id="name"><strong>HBase Column Qualifier</strong></td><td 
id="default-value">q</td><td id="allowable-values"></td><td 
id="description">Name of the column qualifier on HBase to use for the 
cache<br/><strong>Supports Expression Language: true (will be evaluated using 
variable registry only)</strong></td></tr></table><h3>State managem
 ent: </h3>This component does not store state.<h3>Restricted: </h3>This 
component is not restricted.<h3>System Resource Considerations:</h3>None 
specified.<h3>See Also:</h3><p><a 
href="../org.apache.nifi.hbase.HBase_1_1_2_ClientService/index.html">HBase_1_1_2_ClientService</a></p></body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase_1_1_2-client-service-nar/1.9.0/org.apache.nifi.hbase.HBase_1_1_2_ClientService/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase_1_1_2-client-service-nar/1.9.0/org.apache.nifi.hbase.HBase_1_1_2_ClientService/index.html?rev=1854109&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase_1_1_2-client-service-nar/1.9.0/org.apache.nifi.hbase.HBase_1_1_2_ClientService/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase_1_1_2-client-service-nar/1.9.0/org.apache.nifi.hbase.HBase_1_1_2_ClientService/index.html
 Fri Feb 22 01:03:44 2019
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>HBase_1_1_2_ClientService</title><link 
rel="stylesheet" href="../../../../../css/component-usage.css" 
type="text/css"></link></head><script type="text/javascript">window.onload = 
function(){if(self==top) { document.getElementById('nameHeader').style.display 
= "inherit"; } }</script><body><h1 id="nameHeader" style="display: 
none;">HBase_1_1_2_ClientService</h1><h2>Description: </h2><p>Implementation of 
HBaseClientService using the HBase 1.1.x client. Although this service was 
originally built with the 1.1.2 client and has 1_1_2 in it's name, the client 
library has since been upgraded to 1.1.13 to leverage bug fixes. This service 
can be configured by providing a comma-separated list of configuration files, 
or by specifying values for the other properties. If configuration files are 
provided, they will be loaded first, and the values of the additional 
properties will override the values from the configuration file
 s. In addition, any user defined properties on the processor will also be 
passed to the HBase configuration.</p><h3>Tags: </h3><p>hbase, 
client</p><h3>Properties: </h3><p>In the list below, the names of required 
properties appear in <strong>bold</strong>. Any other properties (not in bold) 
are considered optional. The table also indicates any default values, and 
whether a property supports the <a 
href="../../../../../html/expression-language-guide.html">NiFi Expression 
Language</a>.</p><table id="properties"><tr><th>Name</th><th>Default 
Value</th><th>Allowable Values</th><th>Description</th></tr><tr><td 
id="name">Hadoop Configuration Files</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Comma-separated list of Hadoop 
Configuration files, such as hbase-site.xml and core-site.xml for kerberos, 
including full paths to the files.<br/><strong>Supports Expression Language: 
true (will be evaluated using variable registry only)</strong></td></tr><tr><td 
i
 d="name">Kerberos Credentials Service</td><td id="default-value"></td><td 
id="allowable-values"><strong>Controller Service API: 
</strong><br/>KerberosCredentialsService<br/><strong>Implementation: 
</strong><a 
href="../../../nifi-kerberos-credentials-service-nar/1.9.0/org.apache.nifi.kerberos.KeytabCredentialsService/index.html">KeytabCredentialsService</a></td><td
 id="description">Specifies the Kerberos Credentials Controller Service that 
should be used for authenticating with Kerberos</td></tr><tr><td 
id="name">Kerberos Principal</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Kerberos principal to 
authenticate as. Requires nifi.kerberos.krb5.file to be set in your 
nifi.properties<br/><strong>Supports Expression Language: true (will be 
evaluated using variable registry only)</strong></td></tr><tr><td 
id="name">Kerberos Keytab</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Kerberos keytab associated with 
the pr
 incipal. Requires nifi.kerberos.krb5.file to be set in your 
nifi.properties<br/><strong>Supports Expression Language: true (will be 
evaluated using variable registry only)</strong></td></tr><tr><td 
id="name">ZooKeeper Quorum</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Comma-separated list of 
ZooKeeper hosts for HBase. Required if Hadoop Configuration Files are not 
provided.<br/><strong>Supports Expression Language: true (will be evaluated 
using variable registry only)</strong></td></tr><tr><td id="name">ZooKeeper 
Client Port</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">The port on which ZooKeeper is accepting client connections. 
Required if Hadoop Configuration Files are not provided.<br/><strong>Supports 
Expression Language: true (will be evaluated using variable registry 
only)</strong></td></tr><tr><td id="name">ZooKeeper ZNode Parent</td><td 
id="default-value"></td><td id="allowable-values"></td><td id
 ="description">The ZooKeeper ZNode Parent value for HBase (example: /hbase). 
Required if Hadoop Configuration Files are not provided.<br/><strong>Supports 
Expression Language: true (will be evaluated using variable registry 
only)</strong></td></tr><tr><td id="name">HBase Client Retries</td><td 
id="default-value">1</td><td id="allowable-values"></td><td 
id="description">The number of times the HBase client will retry connecting. 
Required if Hadoop Configuration Files are not provided.<br/><strong>Supports 
Expression Language: true (will be evaluated using variable registry 
only)</strong></td></tr><tr><td id="name">Phoenix Client JAR Location</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
full path to the Phoenix client JAR. Required if Phoenix is installed on top of 
HBase.<br/><strong>Supports Expression Language: true (will be evaluated using 
variable registry only)</strong></td></tr></table><h3>Dynamic Properties: 
</h3><p>Dynamic Properties 
 allow the user to specify both the name and value of a property.<table 
id="dynamic-properties"><tr><th>Name</th><th>Value</th><th>Description</th></tr><tr><td
 id="name">The name of an HBase configuration property.</td><td id="value">The 
value of the given HBase configuration property.</td><td>These properties will 
be set on the HBase configuration after loading any provided configuration 
files.<br/><strong>Supports Expression Language: 
false</strong></td></tr></table></p><h3>State management: </h3>This component 
does not store state.<h3>Restricted: </h3>This component is not 
restricted.<h3>System Resource Considerations:</h3>None specified.</body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase_1_1_2-client-service-nar/1.9.0/org.apache.nifi.hbase.HBase_1_1_2_RecordLookupService/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase_1_1_2-client-service-nar/1.9.0/org.apache.nifi.hbase.HBase_1_1_2_RecordLookupService/index.html?rev=1854109&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase_1_1_2-client-service-nar/1.9.0/org.apache.nifi.hbase.HBase_1_1_2_RecordLookupService/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase_1_1_2-client-service-nar/1.9.0/org.apache.nifi.hbase.HBase_1_1_2_RecordLookupService/index.html
 Fri Feb 22 01:03:44 2019
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>HBase_1_1_2_RecordLookupService</title><link 
rel="stylesheet" href="../../../../../css/component-usage.css" 
type="text/css"></link></head><script type="text/javascript">window.onload = 
function(){if(self==top) { document.getElementById('nameHeader').style.display 
= "inherit"; } }</script><body><h1 id="nameHeader" style="display: 
none;">HBase_1_1_2_RecordLookupService</h1><h2>Description: </h2><p>A lookup 
service that retrieves one or more columns from HBase and returns them as a 
record. The lookup coordinates must contain 'rowKey' which will be the HBase 
row id.</p><h3>Tags: </h3><p>hbase, record, lookup, service</p><h3>Properties: 
</h3><p>In the list below, the names of required properties appear in 
<strong>bold</strong>. Any other properties (not in bold) are considered 
optional. The table also indicates any default values.</p><table 
id="properties"><tr><th>Name</th><th>Default Value</th><th>Allowable Values<
 /th><th>Description</th></tr><tr><td id="name"><strong>HBase Client 
Service</strong></td><td id="default-value"></td><td 
id="allowable-values"><strong>Controller Service API: 
</strong><br/>HBaseClientService<br/><strong>Implementations: </strong><a 
href="../../../nifi-hbase_2-client-service-nar/1.9.0/org.apache.nifi.hbase.HBase_2_ClientService/index.html">HBase_2_ClientService</a><br/><a
 
href="../org.apache.nifi.hbase.HBase_1_1_2_ClientService/index.html">HBase_1_1_2_ClientService</a></td><td
 id="description">Specifies the HBase Client Controller Service to use for 
accessing HBase.</td></tr><tr><td id="name"><strong>Table Name</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
name of the table where look ups will be run.</td></tr><tr><td 
id="name">Authorizations</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The list of authorization 
tokens to be used with cell visibility if it is enabled. These will
  be used to override the default authorization list for the user accessing 
HBase.</td></tr><tr><td id="name">Columns</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">A comma-separated list of 
\"&lt;colFamily&gt;:&lt;colQualifier&gt;\" pairs to return when scanning. To 
return all columns for a given family, leave off the qualifier such as 
\"&lt;colFamily1&gt;,&lt;colFamily2&gt;\".</td></tr><tr><td 
id="name"><strong>Character Set</strong></td><td 
id="default-value">UTF-8</td><td id="allowable-values"></td><td 
id="description">Specifies the character set used to decode bytes retrieved 
from HBase.</td></tr></table><h3>State management: </h3>This component does not 
store state.<h3>Restricted: </h3>This component is not restricted.<h3>System 
Resource Considerations:</h3>None specified.</body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase_2-client-service-nar/1.9.0/org.apache.nifi.hbase.HBase_2_ClientMapCacheService/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase_2-client-service-nar/1.9.0/org.apache.nifi.hbase.HBase_2_ClientMapCacheService/index.html?rev=1854109&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase_2-client-service-nar/1.9.0/org.apache.nifi.hbase.HBase_2_ClientMapCacheService/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase_2-client-service-nar/1.9.0/org.apache.nifi.hbase.HBase_2_ClientMapCacheService/index.html
 Fri Feb 22 01:03:44 2019
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>HBase_2_ClientMapCacheService</title><link 
rel="stylesheet" href="../../../../../css/component-usage.css" 
type="text/css"></link></head><script type="text/javascript">window.onload = 
function(){if(self==top) { document.getElementById('nameHeader').style.display 
= "inherit"; } }</script><body><h1 id="nameHeader" style="display: 
none;">HBase_2_ClientMapCacheService</h1><h2>Description: </h2><p>Provides the 
ability to use an HBase table as a cache, in place of a DistributedMapCache. 
Uses a HBase_2_ClientService controller to communicate with HBase.</p><h3>Tags: 
</h3><p>distributed, cache, state, map, cluster, hbase</p><h3>Properties: 
</h3><p>In the list below, the names of required properties appear in 
<strong>bold</strong>. Any other properties (not in bold) are considered 
optional. The table also indicates any default values, and whether a property 
supports the <a href="../../../../../html/expression-language-gu
 ide.html">NiFi Expression Language</a>.</p><table 
id="properties"><tr><th>Name</th><th>Default Value</th><th>Allowable 
Values</th><th>Description</th></tr><tr><td id="name"><strong>HBase Cache Table 
Name</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Name of the table on HBase to 
use for the cache.<br/><strong>Supports Expression Language: true (will be 
evaluated using variable registry only)</strong></td></tr><tr><td 
id="name">Authorizations</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The list of authorization 
tokens to be used with cell visibility if it is enabled. These will be used to 
override the default authorization list for the user accessing 
HBase.</td></tr><tr><td id="name"><strong>HBase Client Service</strong></td><td 
id="default-value"></td><td id="allowable-values"><strong>Controller Service 
API: </strong><br/>HBaseClientService<br/><strong>Implementations: </strong><a 
href="../org.apa
 
che.nifi.hbase.HBase_2_ClientService/index.html">HBase_2_ClientService</a><br/><a
 
href="../../../nifi-hbase_1_1_2-client-service-nar/1.9.0/org.apache.nifi.hbase.HBase_1_1_2_ClientService/index.html">HBase_1_1_2_ClientService</a></td><td
 id="description">Specifies the HBase Client Controller Service to use for 
accessing HBase.</td></tr><tr><td id="name"><strong>HBase Column 
Family</strong></td><td id="default-value">f</td><td 
id="allowable-values"></td><td id="description">Name of the column family on 
HBase to use for the cache.<br/><strong>Supports Expression Language: true 
(will be evaluated using variable registry only)</strong></td></tr><tr><td 
id="name"><strong>HBase Column Qualifier</strong></td><td 
id="default-value">q</td><td id="allowable-values"></td><td 
id="description">Name of the column qualifier on HBase to use for the 
cache<br/><strong>Supports Expression Language: true (will be evaluated using 
variable registry only)</strong></td></tr></table><h3>State management: </h
 3>This component does not store state.<h3>Restricted: </h3>This component is 
not restricted.<h3>System Resource Considerations:</h3>None specified.<h3>See 
Also:</h3><p><a 
href="../org.apache.nifi.hbase.HBase_2_ClientService/index.html">HBase_2_ClientService</a></p></body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase_2-client-service-nar/1.9.0/org.apache.nifi.hbase.HBase_2_ClientService/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase_2-client-service-nar/1.9.0/org.apache.nifi.hbase.HBase_2_ClientService/index.html?rev=1854109&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase_2-client-service-nar/1.9.0/org.apache.nifi.hbase.HBase_2_ClientService/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase_2-client-service-nar/1.9.0/org.apache.nifi.hbase.HBase_2_ClientService/index.html
 Fri Feb 22 01:03:44 2019
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>HBase_2_ClientService</title><link 
rel="stylesheet" href="../../../../../css/component-usage.css" 
type="text/css"></link></head><script type="text/javascript">window.onload = 
function(){if(self==top) { document.getElementById('nameHeader').style.display 
= "inherit"; } }</script><body><h1 id="nameHeader" style="display: 
none;">HBase_2_ClientService</h1><h2>Description: </h2><p>Implementation of 
HBaseClientService using the HBase 1.1.x client. Although this service was 
originally built with the 1.1.2 client and has 1_1_2 in it's name, the client 
library has since been upgraded to 1.1.13 to leverage bug fixes. This service 
can be configured by providing a comma-separated list of configuration files, 
or by specifying values for the other properties. If configuration files are 
provided, they will be loaded first, and the values of the additional 
properties will override the values from the configuration files. In ad
 dition, any user defined properties on the processor will also be passed to 
the HBase configuration.</p><h3>Tags: </h3><p>hbase, client</p><h3>Properties: 
</h3><p>In the list below, the names of required properties appear in 
<strong>bold</strong>. Any other properties (not in bold) are considered 
optional. The table also indicates any default values, and whether a property 
supports the <a href="../../../../../html/expression-language-guide.html">NiFi 
Expression Language</a>.</p><table id="properties"><tr><th>Name</th><th>Default 
Value</th><th>Allowable Values</th><th>Description</th></tr><tr><td 
id="name">Hadoop Configuration Files</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Comma-separated list of Hadoop 
Configuration files, such as hbase-site.xml and core-site.xml for kerberos, 
including full paths to the files.<br/><strong>Supports Expression Language: 
true (will be evaluated using variable registry only)</strong></td></tr><tr><td 
id="name"
 >Kerberos Credentials Service</td><td id="default-value"></td><td 
 >id="allowable-values"><strong>Controller Service API: 
 ></strong><br/>KerberosCredentialsService<br/><strong>Implementation: 
 ></strong><a 
 >href="../../../nifi-kerberos-credentials-service-nar/1.9.0/org.apache.nifi.kerberos.KeytabCredentialsService/index.html">KeytabCredentialsService</a></td><td
 > id="description">Specifies the Kerberos Credentials Controller Service that 
 >should be used for authenticating with Kerberos</td></tr><tr><td 
 >id="name">Kerberos Principal</td><td id="default-value"></td><td 
 >id="allowable-values"></td><td id="description">Kerberos principal to 
 >authenticate as. Requires nifi.kerberos.krb5.file to be set in your 
 >nifi.properties<br/><strong>Supports Expression Language: true (will be 
 >evaluated using variable registry only)</strong></td></tr><tr><td 
 >id="name">Kerberos Keytab</td><td id="default-value"></td><td 
 >id="allowable-values"></td><td id="description">Kerberos keytab associated 
 >with the principal.
  Requires nifi.kerberos.krb5.file to be set in your 
nifi.properties<br/><strong>Supports Expression Language: true (will be 
evaluated using variable registry only)</strong></td></tr><tr><td 
id="name">ZooKeeper Quorum</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Comma-separated list of 
ZooKeeper hosts for HBase. Required if Hadoop Configuration Files are not 
provided.<br/><strong>Supports Expression Language: true (will be evaluated 
using variable registry only)</strong></td></tr><tr><td id="name">ZooKeeper 
Client Port</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">The port on which ZooKeeper is accepting client connections. 
Required if Hadoop Configuration Files are not provided.<br/><strong>Supports 
Expression Language: true (will be evaluated using variable registry 
only)</strong></td></tr><tr><td id="name">ZooKeeper ZNode Parent</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="descri
 ption">The ZooKeeper ZNode Parent value for HBase (example: /hbase). Required 
if Hadoop Configuration Files are not provided.<br/><strong>Supports Expression 
Language: true (will be evaluated using variable registry 
only)</strong></td></tr><tr><td id="name">HBase Client Retries</td><td 
id="default-value">1</td><td id="allowable-values"></td><td 
id="description">The number of times the HBase client will retry connecting. 
Required if Hadoop Configuration Files are not provided.<br/><strong>Supports 
Expression Language: true (will be evaluated using variable registry 
only)</strong></td></tr><tr><td id="name">Phoenix Client JAR Location</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
full path to the Phoenix client JAR. Required if Phoenix is installed on top of 
HBase.<br/><strong>Supports Expression Language: true (will be evaluated using 
variable registry only)</strong></td></tr></table><h3>Dynamic Properties: 
</h3><p>Dynamic Properties allow th
 e user to specify both the name and value of a property.<table 
id="dynamic-properties"><tr><th>Name</th><th>Value</th><th>Description</th></tr><tr><td
 id="name">The name of an HBase configuration property.</td><td id="value">The 
value of the given HBase configuration property.</td><td>These properties will 
be set on the HBase configuration after loading any provided configuration 
files.<br/><strong>Supports Expression Language: 
false</strong></td></tr></table></p><h3>State management: </h3>This component 
does not store state.<h3>Restricted: </h3>This component is not 
restricted.<h3>System Resource Considerations:</h3>None specified.</body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase_2-client-service-nar/1.9.0/org.apache.nifi.hbase.HBase_2_RecordLookupService/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase_2-client-service-nar/1.9.0/org.apache.nifi.hbase.HBase_2_RecordLookupService/index.html?rev=1854109&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase_2-client-service-nar/1.9.0/org.apache.nifi.hbase.HBase_2_RecordLookupService/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase_2-client-service-nar/1.9.0/org.apache.nifi.hbase.HBase_2_RecordLookupService/index.html
 Fri Feb 22 01:03:44 2019
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>HBase_2_RecordLookupService</title><link 
rel="stylesheet" href="../../../../../css/component-usage.css" 
type="text/css"></link></head><script type="text/javascript">window.onload = 
function(){if(self==top) { document.getElementById('nameHeader').style.display 
= "inherit"; } }</script><body><h1 id="nameHeader" style="display: 
none;">HBase_2_RecordLookupService</h1><h2>Description: </h2><p>A lookup 
service that retrieves one or more columns from HBase and returns them as a 
record. The lookup coordinates must contain 'rowKey' which will be the HBase 
row id.</p><h3>Tags: </h3><p>hbase, record, lookup, service</p><h3>Properties: 
</h3><p>In the list below, the names of required properties appear in 
<strong>bold</strong>. Any other properties (not in bold) are considered 
optional. The table also indicates any default values.</p><table 
id="properties"><tr><th>Name</th><th>Default Value</th><th>Allowable 
Values</th><th>
 Description</th></tr><tr><td id="name"><strong>HBase Client 
Service</strong></td><td id="default-value"></td><td 
id="allowable-values"><strong>Controller Service API: 
</strong><br/>HBaseClientService<br/><strong>Implementations: </strong><a 
href="../org.apache.nifi.hbase.HBase_2_ClientService/index.html">HBase_2_ClientService</a><br/><a
 
href="../../../nifi-hbase_1_1_2-client-service-nar/1.9.0/org.apache.nifi.hbase.HBase_1_1_2_ClientService/index.html">HBase_1_1_2_ClientService</a></td><td
 id="description">Specifies the HBase Client Controller Service to use for 
accessing HBase.</td></tr><tr><td id="name"><strong>Table Name</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
name of the table where look ups will be run.</td></tr><tr><td 
id="name">Authorizations</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The list of authorization 
tokens to be used with cell visibility if it is enabled. These will be 
 used to override the default authorization list for the user accessing 
HBase.</td></tr><tr><td id="name">Columns</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">A comma-separated list of 
\"&lt;colFamily&gt;:&lt;colQualifier&gt;\" pairs to return when scanning. To 
return all columns for a given family, leave off the qualifier such as 
\"&lt;colFamily1&gt;,&lt;colFamily2&gt;\".</td></tr><tr><td 
id="name"><strong>Character Set</strong></td><td 
id="default-value">UTF-8</td><td id="allowable-values"></td><td 
id="description">Specifies the character set used to decode bytes retrieved 
from HBase.</td></tr></table><h3>State management: </h3>This component does not 
store state.<h3>Restricted: </h3>This component is not restricted.<h3>System 
Resource Considerations:</h3>None specified.</body></html>
\ No newline at end of file


Reply via email to