Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-couchbase-nar/1.9.0/org.apache.nifi.couchbase.CouchbaseMapCacheClient/additionalDetails.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-couchbase-nar/1.9.0/org.apache.nifi.couchbase.CouchbaseMapCacheClient/additionalDetails.html?rev=1854109&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-couchbase-nar/1.9.0/org.apache.nifi.couchbase.CouchbaseMapCacheClient/additionalDetails.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-couchbase-nar/1.9.0/org.apache.nifi.couchbase.CouchbaseMapCacheClient/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>CouchbaseMapCacheClient</title>
+    <link rel="stylesheet" href="../../../../../css/component-usage.css" 
type="text/css" />
+</head>
+
+<body>
+<h2>CouchbaseMapCacheClient</h2>
+
+<h3>Requirements</h3>
+
+<h4>Couchbase Server 4.0 or higher is required for some operation using 
N1QL</h4>
+
+Following cache operations require N1QL query, thus you need to deploy 
Couchbase Server 4.0 or higher for those operations. However, as of this 
writing (May 2017) there are only few processors using these operations. Most 
cache APIs are implemented using document id lookup and should work with older 
version of Couchbase Server.
+
+<ul>
+    <li>removeByPattern(String regex): This cache API removes entries by 
regex. Execute query like:
+        <pre>delete from `cache-bucket-name` where REGEX_CONTAINS(meta().id, 
"^key.*")</pre>
+    </li>
+</ul>
+
+In order to make N1QL work correctly you need to create a <a 
href="https://developer.couchbase.com/documentation/server/current/n1ql/n1ql-language-reference/createprimaryindex.html";>Primary
 index</a> or an index covering N1QL queries performed by 
CouchbaseMapCacheClient. Please refer Couchbase Server documentations for how 
to create those.
+
+</body>
+</html>

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-couchbase-nar/1.9.0/org.apache.nifi.couchbase.CouchbaseMapCacheClient/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-couchbase-nar/1.9.0/org.apache.nifi.couchbase.CouchbaseMapCacheClient/index.html?rev=1854109&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-couchbase-nar/1.9.0/org.apache.nifi.couchbase.CouchbaseMapCacheClient/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-couchbase-nar/1.9.0/org.apache.nifi.couchbase.CouchbaseMapCacheClient/index.html
 Fri Feb 22 01:03:44 2019
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>CouchbaseMapCacheClient</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;">CouchbaseMapCacheClient</h1><h2>Description: </h2><p>Provides the 
ability to communicate with a Couchbase Server cluster as a 
DistributedMapCacheServer. This can be used in order to share a Map between 
nodes in a NiFi cluster. Couchbase Server cluster can provide a high available 
and persistent cache storage.</p><p><a href="additionalDetails.html">Additional 
Details...</a></p><h3>Tags: </h3><p>distributed, cache, map, cluster, 
couchbase</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 co
 nsidered 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>Couchbase Cluster Controller Service</strong></td><td 
id="default-value"></td><td id="allowable-values"><strong>Controller Service 
API: 
</strong><br/>CouchbaseClusterControllerService<br/><strong>Implementation: 
</strong><a 
href="../org.apache.nifi.couchbase.CouchbaseClusterService/index.html">CouchbaseClusterService</a></td><td
 id="description">A Couchbase Cluster Controller Service which manages 
connections to a Couchbase cluster.</td></tr><tr><td id="name"><strong>Bucket 
Name</strong></td><td id="default-value">default</td><td 
id="allowable-values"></td><td id="description">The name of bucket to 
access.<br/><strong>Supports Expression Language: true (wil
 l be evaluated using variable registry 
only)</strong></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-couchbase-nar/1.9.0/org.apache.nifi.couchbase.CouchbaseRecordLookupService/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-couchbase-nar/1.9.0/org.apache.nifi.couchbase.CouchbaseRecordLookupService/index.html?rev=1854109&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-couchbase-nar/1.9.0/org.apache.nifi.couchbase.CouchbaseRecordLookupService/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-couchbase-nar/1.9.0/org.apache.nifi.couchbase.CouchbaseRecordLookupService/index.html
 Fri Feb 22 01:03:44 2019
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>CouchbaseRecordLookupService</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;">CouchbaseRecordLookupService</h1><h2>Description: </h2><p>Lookup a 
record from Couchbase Server associated with the specified key. The coordinates 
that are passed to the lookup must contain the key 'key'.</p><h3>Tags: 
</h3><p>lookup, enrich, couchbase</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 
Languag
 e</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>Couchbase Cluster Controller Service</strong></td><td 
id="default-value"></td><td id="allowable-values"><strong>Controller Service 
API: 
</strong><br/>CouchbaseClusterControllerService<br/><strong>Implementation: 
</strong><a 
href="../org.apache.nifi.couchbase.CouchbaseClusterService/index.html">CouchbaseClusterService</a></td><td
 id="description">A Couchbase Cluster Controller Service which manages 
connections to a Couchbase cluster.</td></tr><tr><td id="name"><strong>Bucket 
Name</strong></td><td id="default-value">default</td><td 
id="allowable-values"></td><td id="description">The name of bucket to 
access.<br/><strong>Supports Expression Language: true (will be evaluated using 
variable registry only)</strong></td></tr><tr><td id="name"><strong>Document 
Type</strong></td><td id="default-value">Json</td><td 
id="allowable-values"><ul><li>Js
 on</li><li>Binary</li></ul></td><td id="description">The type of 
contents.</td></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-scripting-nar/1.9.0/or
 
g.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">The Record Reader to use for parsing fetched document from 
Couchbase Server.</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-couchbase-nar/1.9.0/org.apache.nifi.processors.couchbase.GetCouchbaseKey/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-couchbase-nar/1.9.0/org.apache.nifi.processors.couchbase.GetCouchbaseKey/index.html?rev=1854109&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-couchbase-nar/1.9.0/org.apache.nifi.processors.couchbase.GetCouchbaseKey/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-couchbase-nar/1.9.0/org.apache.nifi.processors.couchbase.GetCouchbaseKey/index.html
 Fri Feb 22 01:03:44 2019
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>GetCouchbaseKey</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;">GetCouchbaseKey</h1><h2>Description: </h2><p>Get a document from 
Couchbase Server via Key/Value access. The ID of the document to fetch may be 
supplied by setting the &lt;Document Id&gt; property. NOTE: if the Document Id 
property is not set, the contents of the FlowFile will be read to determine the 
Document Id, which means that the contents of the entire FlowFile will be 
buffered in memory.</p><h3>Tags: </h3><p>nosql, couchbase, database, 
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 co
 nsidered 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>Couchbase Cluster Controller Service</strong></td><td 
id="default-value"></td><td id="allowable-values"><strong>Controller Service 
API: 
</strong><br/>CouchbaseClusterControllerService<br/><strong>Implementation: 
</strong><a 
href="../org.apache.nifi.couchbase.CouchbaseClusterService/index.html">CouchbaseClusterService</a></td><td
 id="description">A Couchbase Cluster Controller Service which manages 
connections to a Couchbase cluster.</td></tr><tr><td id="name"><strong>Bucket 
Name</strong></td><td id="default-value">default</td><td 
id="allowable-values"></td><td id="description">The name of bucket to 
access.<br/><strong>Supports Expression Language: true (wil
 l be evaluated using variable registry only)</strong></td></tr><tr><td 
id="name"><strong>Document Type</strong></td><td 
id="default-value">Json</td><td 
id="allowable-values"><ul><li>Json</li><li>Binary</li></ul></td><td 
id="description">The type of contents.</td></tr><tr><td id="name">Document 
Id</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">A static, fixed Couchbase document id, or an expression to 
construct the Couchbase document id.<br/><strong>Supports Expression Language: 
true (will be evaluated using flow file attributes and variable 
registry)</strong></td></tr><tr><td id="name">Put Value to Attribute</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">If 
set, the retrieved value will be put into an attribute of the FlowFile instead 
of a the content of the FlowFile. The attribute key to put to is determined by 
evaluating value of this property.<br/><strong>Supports Expression Language: 
true (will be evaluate
 d using flow file attributes and variable 
registry)</strong></td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>retry</td><td>All
 FlowFiles failed to fetch from Couchbase Server but can be retried are routed 
to this relationship.</td></tr><tr><td>success</td><td>Values retrieved from 
Couchbase Server are written as outgoing FlowFiles content or put into an 
attribute of the incoming FlowFile and routed to this 
relationship.</td></tr><tr><td>failure</td><td>All FlowFiles failed to fetch 
from Couchbase Server and not retry-able are routed to this 
relationship.</td></tr><tr><td>original</td><td>The original input FlowFile is 
routed to this relationship when the value is retrieved from Couchbase Server 
and routed to 'success'.</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>couchbase.cluster</td><td>Cluste
 r where the document was retrieved 
from.</td></tr><tr><td>couchbase.bucket</td><td>Bucket where the document was 
retrieved from.</td></tr><tr><td>couchbase.doc.id</td><td>Id of the 
document.</td></tr><tr><td>couchbase.doc.cas</td><td>CAS of the 
document.</td></tr><tr><td>couchbase.doc.expiry</td><td>Expiration of the 
document.</td></tr><tr><td>couchbase.exception</td><td>If Couchbase related 
error occurs the CouchbaseException class name will be captured 
here.</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><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-couchbase-nar/1.9.0/org.apache.nifi.processors.couchbase.PutCouchbaseKey/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-couchbase-nar/1.9.0/org.apache.nifi.processors.couchbase.PutCouchbaseKey/index.html?rev=1854109&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-couchbase-nar/1.9.0/org.apache.nifi.processors.couchbase.PutCouchbaseKey/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-couchbase-nar/1.9.0/org.apache.nifi.processors.couchbase.PutCouchbaseKey/index.html
 Fri Feb 22 01:03:44 2019
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>PutCouchbaseKey</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;">PutCouchbaseKey</h1><h2>Description: </h2><p>Put a document to Couchbase 
Server via Key/Value access.</p><h3>Tags: </h3><p>nosql, couchbase, database, 
put</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>Descripti
 on</th></tr><tr><td id="name"><strong>Couchbase Cluster Controller 
Service</strong></td><td id="default-value"></td><td 
id="allowable-values"><strong>Controller Service API: 
</strong><br/>CouchbaseClusterControllerService<br/><strong>Implementation: 
</strong><a 
href="../org.apache.nifi.couchbase.CouchbaseClusterService/index.html">CouchbaseClusterService</a></td><td
 id="description">A Couchbase Cluster Controller Service which manages 
connections to a Couchbase cluster.</td></tr><tr><td id="name"><strong>Bucket 
Name</strong></td><td id="default-value">default</td><td 
id="allowable-values"></td><td id="description">The name of bucket to 
access.<br/><strong>Supports Expression Language: true (will be evaluated using 
variable registry only)</strong></td></tr><tr><td id="name"><strong>Document 
Type</strong></td><td id="default-value">Json</td><td 
id="allowable-values"><ul><li>Json</li><li>Binary</li></ul></td><td 
id="description">The type of contents.</td></tr><tr><td id="name">Document
  Id</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">A static, fixed Couchbase document id, or an expression to 
construct the Couchbase document id.<br/><strong>Supports Expression Language: 
true (will be evaluated using flow file attributes and variable 
registry)</strong></td></tr><tr><td id="name"><strong>Persist 
To</strong></td><td id="default-value">NONE</td><td 
id="allowable-values"><ul><li>MASTER</li><li>NONE</li><li>ONE</li><li>TWO</li><li>THREE</li><li>FOUR</li></ul></td><td
 id="description">Durability constraint about disk 
persistence.</td></tr><tr><td id="name"><strong>Replicate To</strong></td><td 
id="default-value">NONE</td><td 
id="allowable-values"><ul><li>NONE</li><li>ONE</li><li>TWO</li><li>THREE</li></ul></td><td
 id="description">Durability constraint about 
replication.</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>retry</td><td>All
 FlowFiles failed to be written
  to Couchbase Server but can be retried are routed to this 
relationship.</td></tr><tr><td>success</td><td>All FlowFiles that are written 
to Couchbase Server are routed to this 
relationship.</td></tr><tr><td>failure</td><td>All FlowFiles failed to be 
written to Couchbase Server and not retry-able are routed to this 
relationship.</td></tr></table><h3>Reads Attributes: </h3><table 
id="reads-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>uuid</td><td>Used
 as a document id if 'Document Id' is not specified</td></tr></table><h3>Writes 
Attributes: </h3><table 
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>couchbase.cluster</td><td>Cluster
 where the document was 
stored.</td></tr><tr><td>couchbase.bucket</td><td>Bucket where the document was 
stored.</td></tr><tr><td>couchbase.doc.id</td><td>Id of the 
document.</td></tr><tr><td>couchbase.doc.cas</td><td>CAS of the 
document.</td></tr><tr><td>couchbase.doc.expiry</td><td>Expiration of the 
document.</td><
 /tr><tr><td>couchbase.exception</td><td>If Couchbase related error occurs the 
CouchbaseException class name will be captured here.</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><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-cybersecurity-nar/1.9.0/org.apache.nifi.processors.cybersecurity.CompareFuzzyHash/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-cybersecurity-nar/1.9.0/org.apache.nifi.processors.cybersecurity.CompareFuzzyHash/index.html?rev=1854109&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-cybersecurity-nar/1.9.0/org.apache.nifi.processors.cybersecurity.CompareFuzzyHash/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-cybersecurity-nar/1.9.0/org.apache.nifi.processors.cybersecurity.CompareFuzzyHash/index.html
 Fri Feb 22 01:03:44 2019
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>CompareFuzzyHash</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;">CompareFuzzyHash</h1><h2>Description: </h2><p>Compares an attribute 
containing a Fuzzy Hash against a file containing a list of fuzzy hashes, 
appending an attribute to the FlowFile in case of a successful 
match.</p><h3>Tags: </h3><p>hashing, fuzzy-hashing, 
cyber-security</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>Hash List source file</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Path to the file containing hashes to be validated 
against</td></tr><tr><td id="name"><strong>Hashing Algorithm</strong></td><td 
id="default-value"></td><td id="allowable-values"><ul><li>ssdeep <img 
src="../../../../../html/images/iconInfo.png" alt="Uses ssdeep / SpamSum 
'context triggered piecewise hash'." title="Uses ssdeep / SpamSum 'context 
triggered piecewise hash'."></img></li><li>tlsh <img 
src="../../../../../html/images/iconInfo.png" alt="Uses TLSH (Trend 'Locality 
Sensitive Hash'). Note: FlowFile Content must be at least 512 characters long" 
title="Uses TLSH (Trend 'Locality Sensitive Hash'). Note: FlowFile Content must 
be at least 512 characters long"></img></li></ul></td><td id="description">The 
hashing algorithm utilised</td></tr><tr><td id="name"><strong>Hash Attribute 
Name</strong></td><td id="default-value">fuzzyhash.value</td
 ><td id="allowable-values"></td><td id="description">The name of the FlowFile 
 >Attribute that should hold the Fuzzy Hash Value</td></tr><tr><td 
 >id="name"><strong>Match threshold</strong></td><td 
 >id="default-value"></td><td id="allowable-values"></td><td 
 >id="description">The similarity score must exceed or be equal to in order 
 >formatch to be considered true. Refer to Additional Information for 
 >differences between TLSH and SSDEEP scores and how they relate to this 
 >property.</td></tr><tr><td id="name"><strong>Matching mode</strong></td><td 
 >id="default-value">single</td><td id="allowable-values"><ul><li>single <img 
 >src="../../../../../html/images/iconInfo.png" alt="Send FlowFile to matched 
 >after the first match above threshold" title="Send FlowFile to matched after 
 >the first match above threshold"></img></li><li>multi-match <img 
 >src="../../../../../html/images/iconInfo.png" alt="Iterate full list of 
 >hashes before deciding to send FlowFile to matched or unmatched" 
 >title="Iterate full list
  of hashes before deciding to send FlowFile to matched or 
unmatched"></img></li></ul></td><td id="description">Defines if the Processor 
should try to match as many entries as possible (multi-match) or if it should 
stop after the first match (single)</td></tr></table><h3>Relationships: 
</h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>failure</td><td>Any
 FlowFile that cannot be matched, e.g. (lacks the attribute) will be sent to 
this Relationship.</td></tr><tr><td>not-found</td><td>Any FlowFile that cannot 
be matched to an existing hash will be sent to this 
Relationship.</td></tr><tr><td>found</td><td>Any FlowFile that is successfully 
matched to an existing hash will be sent 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>XXXX.N.match</td><td>The
 match that resembles the attribute specified by the &lt;Hash Attribut
 e Name&gt; property. Note that: 'XXX' gets replaced with the &lt;Hash 
Attribute Name&gt;</td></tr><tr><td>XXXX.N.similarity</td><td>The similarity 
score between this flowfileand its match of the same number N. Note that: 'XXX' 
gets replaced with the &lt;Hash Attribute Name&gt;</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.<h3>See Also:</h3><p><a 
href="../org.apache.nifi.processors.cybersecurity.FuzzyHashContent/index.html">FuzzyHashContent</a></p></body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-cybersecurity-nar/1.9.0/org.apache.nifi.processors.cybersecurity.FuzzyHashContent/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-cybersecurity-nar/1.9.0/org.apache.nifi.processors.cybersecurity.FuzzyHashContent/index.html?rev=1854109&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-cybersecurity-nar/1.9.0/org.apache.nifi.processors.cybersecurity.FuzzyHashContent/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-cybersecurity-nar/1.9.0/org.apache.nifi.processors.cybersecurity.FuzzyHashContent/index.html
 Fri Feb 22 01:03:44 2019
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>FuzzyHashContent</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;">FuzzyHashContent</h1><h2>Description: </h2><p>Calculates a 
fuzzy/locality-sensitive hash value for the Content of a FlowFile and puts that 
hash value on the FlowFile as an attribute whose name is determined by the 
&lt;Hash Attribute Name&gt; property.Note: this processor only offers 
non-cryptographic hash algorithms. And it should be not be seen as a 
replacement to the HashContent processor.Note: The underlying library loads the 
entirety of the streamed content into and performs result evaluations in 
memory. Accordingly, it is important to consider the anticipated profile of 
content being evalu
 ated by this processor and the hardware supporting it especially when working 
against large files.</p><h3>Tags: </h3><p>hashing, fuzzy-hashing, 
cyber-security</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>Hash Attribute Name</strong></td><td 
id="default-value">fuzzyhash.value</td><td id="allowable-values"></td><td 
id="description">The name of the FlowFile Attribute that should hold the Fuzzy 
Hash Value</td></tr><tr><td id="name"><strong>Hashing 
Algorithm</strong></td><td id="default-value"></td><td 
id="allowable-values"><ul><li>ssdeep <img 
src="../../../../../html/images/iconInfo.png" alt="Uses ssdeep / SpamSum 
'context triggered piecewise hash'." title="Uses ssdeep / SpamSum 
 'context triggered piecewise hash'."></img></li><li>tlsh <img 
src="../../../../../html/images/iconInfo.png" alt="Uses TLSH (Trend 'Locality 
Sensitive Hash'). Note: FlowFile Content must be at least 512 characters long" 
title="Uses TLSH (Trend 'Locality Sensitive Hash'). Note: FlowFile Content must 
be at least 512 characters long"></img></li></ul></td><td id="description">The 
hashing algorithm utilised</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>Any
 FlowFile that is successfully hashed will be sent to this 
Relationship.</td></tr><tr><td>failure</td><td>Any FlowFile that is 
successfully hashed will be sent 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>&lt;Hash
 Attribute Name&gt;</td><td>This Processor adds an attribute whose value is the 
result of Hashing t
 he existing FlowFile content. The name of this attribute is specified by the 
&lt;Hash Attribute Name&gt; property</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.<h3>See 
Also:</h3><p><a 
href="../org.apache.nifi.processors.cybersecurity.CompareFuzzyHash/index.html">CompareFuzzyHash</a>,
 <a 
href="../../../nifi-standard-nar/1.9.0/org.apache.nifi.processors.standard.HashContent/index.html">HashContent</a></p></body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-datadog-nar/1.9.0/org.apache.nifi.reporting.datadog.DataDogReportingTask/additionalDetails.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-datadog-nar/1.9.0/org.apache.nifi.reporting.datadog.DataDogReportingTask/additionalDetails.html?rev=1854109&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-datadog-nar/1.9.0/org.apache.nifi.reporting.datadog.DataDogReportingTask/additionalDetails.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-datadog-nar/1.9.0/org.apache.nifi.reporting.datadog.DataDogReportingTask/additionalDetails.html
 Fri Feb 22 01:03:44 2019
@@ -0,0 +1,53 @@
+<!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>DataDogReportingTask</title>
+        <link rel="stylesheet" href="../../../../../css/component-usage.css" 
type="text/css" />
+    </head>
+
+    <body>
+        <h2>DataDogReportingTask</h2>
+
+        <p>This ReportingTask sends the following metrics to DataDog:</p>
+        <ul>
+            <li>FlowFilesReceivedLast5Minutes</li>
+            <li>BytesReceivedLast5Minutes</li>
+            <li>FlowFilesSentLast5Minutes</li>
+            <li>BytesSentLast5Minutes</li>
+            <li>FlowFilesQueued</li>
+            <li>BytesQueued</li>
+            <li>BytesReadLast5Minutes</li>
+            <li>BytesWrittenLast5Minutes</li>
+            <li>ActiveThreads</li>
+            <li>TotalTaskDurationSeconds</li>
+            <li>jvm.uptime</li>
+            <li>jvm.heap_used</li>
+            <li>jvm.heap_usage</li>
+            <li>jvm.non_heap_usage</li>
+            <li>jvm.thread_states.runnable</li>
+            <li>jvm.thread_states.blocked</li>
+            <li>jvm.thread_states.timed_waiting</li>
+            <li>jvm.thread_states.terminated</li>
+            <li>jvm.thread_count</li>
+            <li>jvm.daemon_thread_count</li>
+            <li>jvm.file_descriptor_usage</li>
+            <li>jvm.gc.runs</li>
+            <li>jvm.gc.time</li>
+        </ul>
+    </body>
+</html>

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-datadog-nar/1.9.0/org.apache.nifi.reporting.datadog.DataDogReportingTask/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-datadog-nar/1.9.0/org.apache.nifi.reporting.datadog.DataDogReportingTask/index.html?rev=1854109&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-datadog-nar/1.9.0/org.apache.nifi.reporting.datadog.DataDogReportingTask/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-datadog-nar/1.9.0/org.apache.nifi.reporting.datadog.DataDogReportingTask/index.html
 Fri Feb 22 01:03:44 2019
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>DataDogReportingTask</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;">DataDogReportingTask</h1><h2>Description: </h2><p>Publishes metrics from 
NiFi to datadog. For accurate and informative reporting, components should have 
unique names.</p><p><a href="additionalDetails.html">Additional 
Details...</a></p><h3>Tags: </h3><p>reporting, datadog, 
metrics</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">Ni
 Fi 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>Metrics 
prefix</strong></td><td id="default-value">nifi</td><td 
id="allowable-values"></td><td id="description">Prefix to be added before every 
metric<br/><strong>Supports Expression Language: true (will be evaluated using 
variable registry only)</strong></td></tr><tr><td 
id="name"><strong>Environment</strong></td><td id="default-value">dev</td><td 
id="allowable-values"></td><td id="description">Environment, dataflow is 
running in. This property will be included as metrics tag.<br/><strong>Supports 
Expression Language: true (will be evaluated using variable registry 
only)</strong></td></tr><tr><td id="name">API key</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Datadog API key. If specified value is 'agent', local Datadog 
agent will be used.</td></tr><tr><td id="name"><strong>Data
 dog transport</strong></td><td id="default-value">Datadog HTTP</td><td 
id="allowable-values"><ul><li>Datadog Agent <img 
src="../../../../../html/images/iconInfo.png" alt="Metrics will be sent via 
locally installed Datadog agent. Datadog agent needs to be installed manually 
before using this option" title="Metrics will be sent via locally installed 
Datadog agent. Datadog agent needs to be installed manually before using this 
option"></img></li><li>Datadog HTTP <img 
src="../../../../../html/images/iconInfo.png" alt="Metrics will be sent via 
HTTP transport with no need of Agent installed. Datadog API key needs to be 
set" title="Metrics will be sent via HTTP transport with no need of Agent 
installed. Datadog API key needs to be set"></img></li></ul></td><td 
id="description">Transport through which metrics will be sent to 
Datadog</td></tr></table><h3>State management: </h3>This component does not 
store state.<h3>Restricted: </h3>This component is not restricted.<h3>System 
Resource Consid
 erations:</h3>None specified.</body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-dbcp-service-nar/1.9.0/org.apache.nifi.dbcp.DBCPConnectionPool/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-dbcp-service-nar/1.9.0/org.apache.nifi.dbcp.DBCPConnectionPool/index.html?rev=1854109&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-dbcp-service-nar/1.9.0/org.apache.nifi.dbcp.DBCPConnectionPool/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-dbcp-service-nar/1.9.0/org.apache.nifi.dbcp.DBCPConnectionPool/index.html
 Fri Feb 22 01:03:44 2019
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>DBCPConnectionPool</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;">DBCPConnectionPool</h1><h2>Description: </h2><p>Provides Database 
Connection Pooling Service. Connections can be asked from pool and returned 
after usage.</p><h3>Tags: </h3><p>dbcp, jdbc, database, connection, pooling, 
store</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, whether a 
property supports the <a 
href="../../../../../html/expression-language-guide.html">NiFi Expression 
Language</a>, and whether a property is consider
 ed "sensitive", meaning that its value will be encrypted. Before entering a 
value in a sensitive property, ensure that the <strong>nifi.properties</strong> 
file has an entry for the property 
<strong>nifi.sensitive.props.key</strong>.</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>Database 
Connection URL</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">A database connection URL used 
to connect to a database. May contain database system name, host, port, 
database name and some parameters. The exact syntax of a database connection 
URL is specified by your DBMS.<br/><strong>Supports Expression Language: true 
(will be evaluated using variable registry only)</strong></td></tr><tr><td 
id="name"><strong>Database Driver Class Name</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Database driver class name<br/><st
 rong>Supports Expression Language: true (will be evaluated using variable 
registry only)</strong></td></tr><tr><td id="name">Database Driver 
Location(s)</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">Comma-separated list of files/folders and/or URLs containing 
the driver JAR and its dependencies (if any). For example 
'/var/tmp/mariadb-java-client-1.1.7.jar'<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">Database User</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Database user name<br/><strong>Supports Expression Language: 
true (will be evaluated using variable registry only)</strong></td></tr><tr><td 
id="name">Password</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The password for the database 
user<br/><strong>Sensitive Property: true</strong><br/><strong>Supports 
Expression Language: true (will be evaluated using variable registry 
only)</strong></td></tr><tr><td id="name"><strong>Max Wait 
Time</strong></td><td id="default-value">500 millis</td><td 
id="allowable-values"></td><td id="description">The maximum amount of time that 
the pool will wait (when there are no available connections)  for a connection 
to be returned before failing, or -1 to wait indefinitely. </td></tr><tr><td 
id="name"><strong>Max Total Connections</strong></td><td 
id="default-value">8</td><td id
 ="allowable-values"></td><td id="description">The maximum number of active 
connections that can be allocated from this pool at the same time,  or negative 
for no limit.</td></tr><tr><td id="name">Validation query</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Validation query used to validate connections before returning 
them. When connection is invalid, it get's dropped and new valid connection 
will be returned. Note!! Using validation might have some performance 
penalty.<br/><strong>Supports Expression Language: true (will be evaluated 
using variable registry only)</strong></td></tr><tr><td id="name">Minimum Idle 
Connections</td><td id="default-value">0</td><td id="allowable-values"></td><td 
id="description">The minimum number of connections that can remain idle in the 
pool, without extra ones being created, or zero to create 
none.<br/><strong>Supports Expression Language: true (will be evaluated using 
variable registry only)</strong></td></tr>
 <tr><td id="name">Max Idle Connections</td><td id="default-value">8</td><td 
id="allowable-values"></td><td id="description">The maximum number of 
connections that can remain idle in the pool, without extra ones being 
released, or negative for no limit.<br/><strong>Supports Expression Language: 
true (will be evaluated using variable registry only)</strong></td></tr><tr><td 
id="name">Max Connection Lifetime</td><td id="default-value">-1</td><td 
id="allowable-values"></td><td id="description">The maximum lifetime in 
milliseconds of a connection. After this time is exceeded the connection will 
fail the next activation, passivation or validation test. A value of zero or 
less means the connection has an infinite lifetime.<br/><strong>Supports 
Expression Language: true (will be evaluated using variable registry 
only)</strong></td></tr><tr><td id="name">Time Between Eviction Runs</td><td 
id="default-value">-1</td><td id="allowable-values"></td><td 
id="description">The number of milliseconds
  to sleep between runs of the idle connection evictor thread. When 
non-positive, no idle connection evictor thread will be 
run.<br/><strong>Supports Expression Language: true (will be evaluated using 
variable registry only)</strong></td></tr><tr><td id="name">Minimum Evictable 
Idle Time</td><td id="default-value">30 mins</td><td 
id="allowable-values"></td><td id="description">The minimum amount of time a 
connection may sit idle in the pool before it is eligible for 
eviction.<br/><strong>Supports Expression Language: true (will be evaluated 
using variable registry only)</strong></td></tr><tr><td id="name">Soft Minimum 
Evictable Idle Time</td><td id="default-value">-1</td><td 
id="allowable-values"></td><td id="description">The minimum amount of time a 
connection may sit idle in the pool before it is eligible for eviction by the 
idle connection evictor, with the extra condition that at least a minimum 
number of idle connections remain in the pool. When the not-soft version of 
this opti
 on is set to a positive value, it is examined first by the idle connection 
evictor: when idle connections are visited by the evictor, idle time is first 
compared against it (without considering the number of idle connections in the 
pool) and then against this soft option, including the minimum idle connections 
constraint.<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">JDBC property name</td><td id="value">JDBC property 
value</td><td>Specifies a property name and value to be set on the JDBC 
connection(s). If Expression Language is used, evaluation will be performed 
upon the controller service being enabled. Note that no flow file input 
(attributes, e.g.) is available for use in Expression Langu
 age constructs for these properties.<br/><strong>Supports Expression Language: 
true (will be evaluated using variable registry 
only)</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-dbcp-service-nar/1.9.0/org.apache.nifi.dbcp.DBCPConnectionPoolLookup/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-dbcp-service-nar/1.9.0/org.apache.nifi.dbcp.DBCPConnectionPoolLookup/index.html?rev=1854109&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-dbcp-service-nar/1.9.0/org.apache.nifi.dbcp.DBCPConnectionPoolLookup/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-dbcp-service-nar/1.9.0/org.apache.nifi.dbcp.DBCPConnectionPoolLookup/index.html
 Fri Feb 22 01:03:44 2019
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>DBCPConnectionPoolLookup</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;">DBCPConnectionPoolLookup</h1><h2>Description: </h2><p>Provides a 
DBCPService that can be used to dynamically select another DBCPService. This 
service requires an attribute named 'database.name' to be passed in when asking 
for a connection, and will throw an exception if the attribute is missing. The 
value of 'database.name' will be used to select the DBCPService that has been 
registered with that name. This will allow multiple DBCPServices to be defined 
and registered, and then selected dynamically at runtime by tagging flow files 
with the appropriate 'database.name' attribute.</p><h3>T
 ags: </h3><p>dbcp, jdbc, database, connection, pooling, 
store</p><h3>Properties: </h3><p>This component has no required or optional 
properties.</p><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 </td><td id="value">JDBC property 
value</td><td><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-distributed-cache-services-nar/1.9.0/org.apache.nifi.distributed.cache.client.DistributedMapCacheClientService/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-distributed-cache-services-nar/1.9.0/org.apache.nifi.distributed.cache.client.DistributedMapCacheClientService/index.html?rev=1854109&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-distributed-cache-services-nar/1.9.0/org.apache.nifi.distributed.cache.client.DistributedMapCacheClientService/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-distributed-cache-services-nar/1.9.0/org.apache.nifi.distributed.cache.client.DistributedMapCacheClientService/index.html
 Fri Feb 22 01:03:44 2019
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>DistributedMapCacheClientService</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;">DistributedMapCacheClientService</h1><h2>Description: </h2><p>Provides 
the ability to communicate with a DistributedMapCacheServer. This can be used 
in order to share a Map between nodes in a NiFi cluster</p><h3>Tags: 
</h3><p>distributed, cache, state, map, cluster</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>Descript
 ion</th></tr><tr><td id="name"><strong>Server Hostname</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
name of the server that is running the DistributedMapCacheServer 
service</td></tr><tr><td id="name"><strong>Server Port</strong></td><td 
id="default-value">4557</td><td id="allowable-values"></td><td 
id="description">The port on the remote server that is to be used when 
communicating with the DistributedMapCacheServer service</td></tr><tr><td 
id="name">SSL Context Service</td><td id="default-value"></td><td 
id="allowable-values"><strong>Controller Service API: 
</strong><br/>SSLContextService<br/><strong>Implementations: </strong><a 
href="../../../nifi-ssl-context-service-nar/1.9.0/org.apache.nifi.ssl.StandardRestrictedSSLContextService/index.html">StandardRestrictedSSLContextService</a><br/><a
 
href="../../../nifi-ssl-context-service-nar/1.9.0/org.apache.nifi.ssl.StandardSSLContextService/index.html">StandardSSLContextService</a></td>
 <td id="description">If specified, indicates the SSL Context Service that is 
used to communicate with the remote server. If not specified, communications 
will not be encrypted</td></tr><tr><td id="name"><strong>Communications 
Timeout</strong></td><td id="default-value">30 secs</td><td 
id="allowable-values"></td><td id="description">Specifies how long to wait when 
communicating with the remote server before determining that there is a 
communications failure if data cannot be sent or 
received</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.<h3>See Also:</h3><p><a 
href="../org.apache.nifi.distributed.cache.server.map.DistributedMapCacheServer/index.html">DistributedMapCacheServer</a>,
 <a 
href="../../../nifi-ssl-context-service-nar/1.9.0/org.apache.nifi.ssl.StandardSSLContextService/index.html">StandardSSLContextService</a></p></body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-distributed-cache-services-nar/1.9.0/org.apache.nifi.distributed.cache.client.DistributedSetCacheClientService/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-distributed-cache-services-nar/1.9.0/org.apache.nifi.distributed.cache.client.DistributedSetCacheClientService/index.html?rev=1854109&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-distributed-cache-services-nar/1.9.0/org.apache.nifi.distributed.cache.client.DistributedSetCacheClientService/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-distributed-cache-services-nar/1.9.0/org.apache.nifi.distributed.cache.client.DistributedSetCacheClientService/index.html
 Fri Feb 22 01:03:44 2019
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>DistributedSetCacheClientService</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;">DistributedSetCacheClientService</h1><h2>Description: </h2><p>Provides 
the ability to communicate with a DistributedSetCacheServer. This can be used 
in order to share a Set between nodes in a NiFi cluster</p><h3>Tags: 
</h3><p>distributed, cache, state, set, cluster</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>Descript
 ion</th></tr><tr><td id="name"><strong>Server Hostname</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
name of the server that is running the DistributedSetCacheServer 
service</td></tr><tr><td id="name"><strong>Server Port</strong></td><td 
id="default-value">4557</td><td id="allowable-values"></td><td 
id="description">The port on the remote server that is to be used when 
communicating with the DistributedSetCacheServer service</td></tr><tr><td 
id="name">SSL Context Service</td><td id="default-value"></td><td 
id="allowable-values"><strong>Controller Service API: 
</strong><br/>SSLContextService<br/><strong>Implementations: </strong><a 
href="../../../nifi-ssl-context-service-nar/1.9.0/org.apache.nifi.ssl.StandardRestrictedSSLContextService/index.html">StandardRestrictedSSLContextService</a><br/><a
 
href="../../../nifi-ssl-context-service-nar/1.9.0/org.apache.nifi.ssl.StandardSSLContextService/index.html">StandardSSLContextService</a></td>
 <td id="description">If specified, indicates the SSL Context Service that is 
used to communicate with the remote server. If not specified, communications 
will not be encrypted</td></tr><tr><td id="name"><strong>Communications 
Timeout</strong></td><td id="default-value">30 secs</td><td 
id="allowable-values"></td><td id="description">Specifices how long to wait 
when communicating with the remote server before determining that there is a 
communications failure if data cannot be sent or 
received</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.<h3>See Also:</h3><p><a 
href="../org.apache.nifi.distributed.cache.server.DistributedSetCacheServer/index.html">DistributedSetCacheServer</a>,
 <a 
href="../../../nifi-ssl-context-service-nar/1.9.0/org.apache.nifi.ssl.StandardSSLContextService/index.html">StandardSSLContextService</a></p></body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-distributed-cache-services-nar/1.9.0/org.apache.nifi.distributed.cache.server.DistributedSetCacheServer/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-distributed-cache-services-nar/1.9.0/org.apache.nifi.distributed.cache.server.DistributedSetCacheServer/index.html?rev=1854109&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-distributed-cache-services-nar/1.9.0/org.apache.nifi.distributed.cache.server.DistributedSetCacheServer/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-distributed-cache-services-nar/1.9.0/org.apache.nifi.distributed.cache.server.DistributedSetCacheServer/index.html
 Fri Feb 22 01:03:44 2019
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>DistributedSetCacheServer</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;">DistributedSetCacheServer</h1><h2>Description: </h2><p>Provides a set 
(collection of unique values) cache that can be accessed over a socket. 
Interaction with this service is typically accomplished via a 
DistributedSetCacheClient service.</p><h3>Tags: </h3><p>distributed, set, 
distinct, cache, server</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>Allo
 wable Values</th><th>Description</th></tr><tr><td 
id="name"><strong>Port</strong></td><td id="default-value">4557</td><td 
id="allowable-values"></td><td id="description">The port to listen on for 
incoming connections</td></tr><tr><td id="name"><strong>Maximum Cache 
Entries</strong></td><td id="default-value">10000</td><td 
id="allowable-values"></td><td id="description">The maximum number of cache 
entries that the cache can hold</td></tr><tr><td id="name"><strong>Eviction 
Strategy</strong></td><td id="default-value">Least Frequently Used</td><td 
id="allowable-values"><ul><li>Least Frequently Used</li><li>Least Recently 
Used</li><li>First In, First Out</li></ul></td><td id="description">Determines 
which strategy should be used to evict values from the cache to make room for 
new entries</td></tr><tr><td id="name">Persistence Directory</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">If 
specified, the cache will be persisted in the given directory; if 
 not specified, the cache will be in-memory only</td></tr><tr><td id="name">SSL 
Context Service</td><td id="default-value"></td><td 
id="allowable-values"><strong>Controller Service API: 
</strong><br/>RestrictedSSLContextService<br/><strong>Implementation: 
</strong><a 
href="../../../nifi-ssl-context-service-nar/1.9.0/org.apache.nifi.ssl.StandardRestrictedSSLContextService/index.html">StandardRestrictedSSLContextService</a></td><td
 id="description">If specified, this service will be used to create an SSL 
Context that will be used to secure communications; if not specified, 
communications will not be secure</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-distributed-cache-services-nar/1.9.0/org.apache.nifi.distributed.cache.server.map.DistributedMapCacheServer/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-distributed-cache-services-nar/1.9.0/org.apache.nifi.distributed.cache.server.map.DistributedMapCacheServer/index.html?rev=1854109&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-distributed-cache-services-nar/1.9.0/org.apache.nifi.distributed.cache.server.map.DistributedMapCacheServer/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-distributed-cache-services-nar/1.9.0/org.apache.nifi.distributed.cache.server.map.DistributedMapCacheServer/index.html
 Fri Feb 22 01:03:44 2019
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>DistributedMapCacheServer</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;">DistributedMapCacheServer</h1><h2>Description: </h2><p>Provides a map 
(key/value) cache that can be accessed over a socket. Interaction with this 
service is typically accomplished via a DistributedMapCacheClient 
service.</p><h3>Tags: </h3><p>distributed, cluster, map, cache, server, 
key/value</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 Va
 lues</th><th>Description</th></tr><tr><td 
id="name"><strong>Port</strong></td><td id="default-value">4557</td><td 
id="allowable-values"></td><td id="description">The port to listen on for 
incoming connections</td></tr><tr><td id="name"><strong>Maximum Cache 
Entries</strong></td><td id="default-value">10000</td><td 
id="allowable-values"></td><td id="description">The maximum number of cache 
entries that the cache can hold</td></tr><tr><td id="name"><strong>Eviction 
Strategy</strong></td><td id="default-value">Least Frequently Used</td><td 
id="allowable-values"><ul><li>Least Frequently Used</li><li>Least Recently 
Used</li><li>First In, First Out</li></ul></td><td id="description">Determines 
which strategy should be used to evict values from the cache to make room for 
new entries</td></tr><tr><td id="name">Persistence Directory</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">If 
specified, the cache will be persisted in the given directory; if not spec
 ified, the cache will be in-memory only</td></tr><tr><td id="name">SSL Context 
Service</td><td id="default-value"></td><td 
id="allowable-values"><strong>Controller Service API: 
</strong><br/>RestrictedSSLContextService<br/><strong>Implementation: 
</strong><a 
href="../../../nifi-ssl-context-service-nar/1.9.0/org.apache.nifi.ssl.StandardRestrictedSSLContextService/index.html">StandardRestrictedSSLContextService</a></td><td
 id="description">If specified, this service will be used to create an SSL 
Context that will be used to secure communications; if not specified, 
communications will not be secure</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.<h3>See 
Also:</h3><p><a 
href="../org.apache.nifi.distributed.cache.client.DistributedMapCacheClientService/index.html">DistributedMapCacheClientService</a>,
 <a href="../../../nifi-ssl-context-service-nar/1
 
.9.0/org.apache.nifi.ssl.StandardSSLContextService/index.html">StandardSSLContextService</a></p></body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-druid-nar/1.9.0/org.apache.nifi.controller.druid.DruidTranquilityController/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-druid-nar/1.9.0/org.apache.nifi.controller.druid.DruidTranquilityController/index.html?rev=1854109&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-druid-nar/1.9.0/org.apache.nifi.controller.druid.DruidTranquilityController/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-druid-nar/1.9.0/org.apache.nifi.controller.druid.DruidTranquilityController/index.html
 Fri Feb 22 01:03:44 2019
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>DruidTranquilityController</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;">DruidTranquilityController</h1><h2>Description: </h2><p>Asynchronously 
sends flowfiles to Druid Indexing Task using Tranquility API. If aggregation 
and roll-up of data is required, an Aggregator JSON descriptor needs to be 
provided.Details on how describe aggregation using JSON can be found at: 
http://druid.io/docs/latest/querying/aggregations.html</p><h3>Tags: 
</h3><p>Druid, Timeseries, OLAP, 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>Druid Data Source</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">A 
data source is the Druid equivalent of a database table.<br/><strong>Supports 
Expression Language: true (will be evaluated using variable registry 
only)</strong></td></tr><tr><td id="name"><strong>Zookeeper Connection 
String</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">A comma-separated list of 
host:port pairs, each corresponding to a ZooKeeper server. Ex: 
localhost:2181<br/><strong>Supports Expression Language: true (will be 
evaluated using variable registry only)</strong></td></tr><tr><td 
id="name"><strong>Zookeeper Retry Base Sle
 ep Time</strong></td><td id="default-value">1000</td><td 
id="allowable-values"></td><td id="description">When a connection to Zookeeper 
needs to be retried, this property specifies the amount of time (in 
milliseconds) to wait at first before retrying.<br/><strong>Supports Expression 
Language: true (will be evaluated using variable registry 
only)</strong></td></tr><tr><td id="name"><strong>Zookeeper Retry Max 
Retries</strong></td><td id="default-value">20</td><td 
id="allowable-values"></td><td id="description">When a connection to Zookeeper 
needs to be retried, this property specifies how many times to attempt 
reconnection.<br/><strong>Supports Expression Language: true (will be evaluated 
using variable registry only)</strong></td></tr><tr><td 
id="name"><strong>Zookeeper Retry Sleep Time</strong></td><td 
id="default-value">30000</td><td id="allowable-values"></td><td 
id="description">When a connection to Zookeeper needs to be retried, this 
property specifies the amount of time to sle
 ep (in milliseconds) between retries.<br/><strong>Supports Expression 
Language: true (will be evaluated using variable registry 
only)</strong></td></tr><tr><td id="name"><strong>Index Service 
Path</strong></td><td id="default-value">druid/overlord</td><td 
id="allowable-values"></td><td id="description">Druid Index Service path as 
defined via the Druid Overlord druid.service property.<br/><strong>Supports 
Expression Language: true (will be evaluated using variable registry 
only)</strong></td></tr><tr><td id="name"><strong>Discovery 
Path</strong></td><td id="default-value">/druid/discovery</td><td 
id="allowable-values"></td><td id="description">Druid Discovery Path as 
configured in Druid Common druid.discovery.curator.path 
property<br/><strong>Supports Expression Language: true (will be evaluated 
using variable registry only)</strong></td></tr><tr><td 
id="name"><strong>Cluster Partitions</strong></td><td 
id="default-value">1</td><td id="allowable-values"></td><td 
id="description">The 
 number of partitions in the Druid cluster.<br/><strong>Supports Expression 
Language: true (will be evaluated using variable registry 
only)</strong></td></tr><tr><td id="name"><strong>Cluster 
Replication</strong></td><td id="default-value">1</td><td 
id="allowable-values"></td><td id="description">The replication factor for the 
Druid cluster.<br/><strong>Supports Expression Language: true (will be 
evaluated using variable registry only)</strong></td></tr><tr><td 
id="name"><strong>Dimension Fields</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">A comma separated list of field 
names that will be stored as dimensions on ingest.<br/><strong>Supports 
Expression Language: true (will be evaluated using variable registry 
only)</strong></td></tr><tr><td id="name"><strong>Aggregator 
JSON</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Tranquility-compliant JSON 
string that defines what aggregators to apply
  on ingest.Example: [{ "type" : "count",       "name" : "count",},{    "name" 
: "value_sum",   "type" : "doubleSum",   "fieldName" : "value"},{        
"fieldName" : "value",  "name" : "value_min",   "type" : "doubleMin"},{ "type" 
: "doubleMax",   "name" : "value_max",   "fieldName" : 
"value"}]<br/><strong>Supports Expression Language: true (will be evaluated 
using variable registry only)</strong></td></tr><tr><td 
id="name"><strong>Segment Granularity</strong></td><td 
id="default-value">TEN_MINUTE</td><td 
id="allowable-values"><ul><li>NONE</li><li>SECOND</li><li>MINUTE</li><li>TEN_MINUTE</li><li>HOUR</li><li>DAY</li><li>MONTH</li><li>YEAR</li></ul></td><td
 id="description">Time unit by which to group and aggregate/rollup events. The 
value must be at least as large as the value of Query 
Granularity.</td></tr><tr><td id="name"><strong>Query 
Granularity</strong></td><td id="default-value">MINUTE</td><td 
id="allowable-values"><ul><li>NONE</li><li>SECOND</li><li>MINUTE</li><li>FIFTEEN_MINUTE</li><li>THIRTY_MINUTE</
 li><li>HOUR</li><li>DAY</li><li>MONTH</li><li>YEAR</li></ul></td><td 
id="description">Time unit by which to group and aggregate/rollup events. The 
value must be less than or equal to the value of Segment 
Granularity.</td></tr><tr><td id="name"><strong>Late Event Grace 
Period</strong></td><td id="default-value">PT10M</td><td 
id="allowable-values"><ul><li>1 minute <img 
src="../../../../../html/images/iconInfo.png" alt="1 minute" title="1 
minute"></img></li><li>10 minutes <img 
src="../../../../../html/images/iconInfo.png" alt="10 minutes" title="10 
minutes"></img></li><li>60 minutes <img 
src="../../../../../html/images/iconInfo.png" alt="1 hour" title="1 
hour"></img></li></ul></td><td id="description">Grace period to allow late 
arriving events for real time ingest.</td></tr><tr><td 
id="name"><strong>Timestamp field</strong></td><td 
id="default-value">timestamp</td><td id="allowable-values"></td><td 
id="description">The name of the field that will be used as the timestamp. 
Should be in 
 ISO8601 format.<br/><strong>Supports Expression Language: true (will be 
evaluated using variable registry only)</strong></td></tr><tr><td 
id="name"><strong>Batch Size</strong></td><td id="default-value">2000</td><td 
id="allowable-values"></td><td id="description">Maximum number of messages to 
send at once.<br/><strong>Supports Expression Language: true (will be evaluated 
using variable registry only)</strong></td></tr><tr><td id="name"><strong>Max 
Pending Batches</strong></td><td id="default-value">5</td><td 
id="allowable-values"></td><td id="description">Maximum number of batches that 
may be in flight before service blocks and waits for one to 
finish.<br/><strong>Supports Expression Language: true (will be evaluated using 
variable registry only)</strong></td></tr><tr><td id="name"><strong>Linger 
(milliseconds)</strong></td><td id="default-value">1000</td><td 
id="allowable-values"></td><td id="description">Wait this long for batches to 
collect more messages (up to Batch Size) before
  sending them. Set to zero to disable waiting. Set to -1 to always wait for 
complete batches before sending. <br/><strong>Supports Expression Language: 
true (will be evaluated using variable registry 
only)</strong></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-druid-nar/1.9.0/org.apache.nifi.processors.druid.PutDruidRecord/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-druid-nar/1.9.0/org.apache.nifi.processors.druid.PutDruidRecord/index.html?rev=1854109&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-druid-nar/1.9.0/org.apache.nifi.processors.druid.PutDruidRecord/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-druid-nar/1.9.0/org.apache.nifi.processors.druid.PutDruidRecord/index.html
 Fri Feb 22 01:03:44 2019
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>PutDruidRecord</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;">PutDruidRecord</h1><h2>Description: </h2><p>Sends records to Druid for 
Indexing. Leverages Druid Tranquility Controller service.</p><h3>Tags: 
</h3><p>druid, timeseries, olap, ingest, 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.</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-scripting-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.avr
 o.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>Record Writer</strong></td><td id="default-value"></td><td 
id="allowable-values"><strong>Controller Service API: 
</strong><br/>RecordSetWriterFactory<br/><strong>Implementations: </strong><a 
href="../../../nifi-record-serialization-services-nar/1.9.0/org.apache.nifi.xml.XMLRecordSetWriter/index.html">XMLRecordSetWriter</a><br/><a
 
href="../../../nifi-record-serialization-services-nar/1.9.0/org.apache.nifi.json.JsonRecordSetWriter/index.html">JsonRecordSetWriter</a><br/><a
 href="../../../nifi-record-serialization-services-nar/1.9.0/org.a
 pache.nifi.csv.CSVRecordSetWriter/index.html">CSVRecordSetWriter</a><br/><a 
href="../../../nifi-scripting-nar/1.9.0/org.apache.nifi.record.script.ScriptedRecordSetWriter/index.html">ScriptedRecordSetWriter</a><br/><a
 
href="../../../nifi-record-serialization-services-nar/1.9.0/org.apache.nifi.avro.AvroRecordSetWriter/index.html">AvroRecordSetWriter</a><br/><a
 
href="../../../nifi-record-serialization-services-nar/1.9.0/org.apache.nifi.text.FreeFormTextRecordSetWriter/index.html">FreeFormTextRecordSetWriter</a></td><td
 id="description">The Record Writer to use in order to serialize the data to 
outgoing relationships.</td></tr><tr><td id="name"><strong>Tranquility 
Service</strong></td><td id="default-value"></td><td 
id="allowable-values"><strong>Controller Service API: 
</strong><br/>DruidTranquilityService<br/><strong>Implementation: </strong><a 
href="../org.apache.nifi.controller.druid.DruidTranquilityController/index.html">DruidTranquilityController</a></td><td
 id="description">Tranqu
 ility Service to use for sending events to 
Druid.</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>FlowFiles
 are routed to this relationship when they are successfully processed by 
Druid</td></tr><tr><td>dropped</td><td>FlowFiles are routed to this 
relationship when they are outside of the configured time window, timestamp 
format is invalid, ect...</td></tr><tr><td>failure</td><td>FlowFiles are routed 
to this relationship when they cannot be parsed or otherwise processed by 
Druid</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>record.count</td><td>The
 number of messages that were sent to Druid for this FlowFile. FlowFiles on the 
success relationship will have a value of this attribute that indicates the 
number of records successfully processed by Druid, and the FlowFile content 
will 
 be only the successful records. This behavior applies to the failure and 
dropped relationships as well.</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-elasticsearch-5-nar/1.9.0/org.apache.nifi.processors.elasticsearch.DeleteElasticsearch5/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-elasticsearch-5-nar/1.9.0/org.apache.nifi.processors.elasticsearch.DeleteElasticsearch5/index.html?rev=1854109&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-elasticsearch-5-nar/1.9.0/org.apache.nifi.processors.elasticsearch.DeleteElasticsearch5/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-elasticsearch-5-nar/1.9.0/org.apache.nifi.processors.elasticsearch.DeleteElasticsearch5/index.html
 Fri Feb 22 01:03:44 2019
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>DeleteElasticsearch5</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;">DeleteElasticsearch5</h1><h2>Description: </h2><p>Delete a document from 
Elasticsearch 5.0 by document id. If the cluster has been configured for 
authorization and/or secure transport (SSL/TLS), and the X-Pack plugin is 
available, secure connections can be made.</p><h3>Tags: </h3><p>elasticsearch, 
elasticsearch 5, delete, remove</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, whether a property supports the <a href="../../..
 /../../html/expression-language-guide.html">NiFi Expression Language</a>, and 
whether a property is considered "sensitive", meaning that its value will be 
encrypted. Before entering a value in a sensitive property, ensure that the 
<strong>nifi.properties</strong> file has an entry for the property 
<strong>nifi.sensitive.props.key</strong>.</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>Cluster 
Name</strong></td><td id="default-value">elasticsearch</td><td 
id="allowable-values"></td><td id="description">Name of the ES cluster (for 
example, elasticsearch_brew). Defaults to 'elasticsearch'<br/><strong>Supports 
Expression Language: true (will be evaluated using variable registry 
only)</strong></td></tr><tr><td id="name"><strong>ElasticSearch 
Hosts</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">ElasticSearch Hosts, which 
should be comma separated and
  colon for hostname/port host1:port,host2:port,....  For example 
testcluster:9300. This processor uses the Transport Client to connect to hosts. 
The default transport client port is 9300.<br/><strong>Supports Expression 
Language: true (will be evaluated using variable registry 
only)</strong></td></tr><tr><td id="name">SSL Context Service</td><td 
id="default-value"></td><td id="allowable-values"><strong>Controller Service 
API: </strong><br/>SSLContextService<br/><strong>Implementations: </strong><a 
href="../../../nifi-ssl-context-service-nar/1.9.0/org.apache.nifi.ssl.StandardRestrictedSSLContextService/index.html">StandardRestrictedSSLContextService</a><br/><a
 
href="../../../nifi-ssl-context-service-nar/1.9.0/org.apache.nifi.ssl.StandardSSLContextService/index.html">StandardSSLContextService</a></td><td
 id="description">The SSL Context Service used to provide client certificate 
information for TLS/SSL connections. This service only applies if the 
Elasticsearch endpoint(s) have been s
 ecured with TLS/SSL.</td></tr><tr><td id="name">X-Pack Transport 
Location</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">Specifies the path to the JAR(s) for the Elasticsearch X-Pack 
Transport feature. If the Elasticsearch cluster has been secured with the 
X-Pack plugin, then the X-Pack Transport JARs must also be available to this 
processor. Note: Do NOT place the X-Pack JARs into NiFi's lib/ directory, doing 
so will prevent the X-Pack Transport JARs from being 
loaded.<br/><strong>Supports Expression Language: true (will be evaluated using 
variable registry only)</strong></td></tr><tr><td id="name">Username</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Username to access the Elasticsearch 
cluster<br/><strong>Supports Expression Language: true (will be evaluated using 
variable registry only)</strong></td></tr><tr><td id="name">Password</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="des
 cription">Password to access the Elasticsearch cluster<br/><strong>Sensitive 
Property: true</strong></td></tr><tr><td id="name"><strong>ElasticSearch Ping 
Timeout</strong></td><td id="default-value">5s</td><td 
id="allowable-values"></td><td id="description">The ping timeout used to 
determine when a node is unreachable. For example, 5s (5 seconds). If non-local 
recommended is 30s<br/><strong>Supports Expression Language: true (will be 
evaluated using variable registry only)</strong></td></tr><tr><td 
id="name"><strong>Sampler Interval</strong></td><td 
id="default-value">5s</td><td id="allowable-values"></td><td 
id="description">How often to sample / ping the nodes listed and connected. For 
example, 5s (5 seconds). If non-local recommended is 30s.<br/><strong>Supports 
Expression Language: true (will be evaluated using variable registry 
only)</strong></td></tr><tr><td id="name"><strong>Document 
Identifier</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="de
 scription">The identifier for the document to be deleted<br/><strong>Supports 
Expression Language: true (will be evaluated using flow file attributes and 
variable registry)</strong></td></tr><tr><td 
id="name"><strong>Index</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The name of the index to delete 
the document from<br/><strong>Supports Expression Language: true (will be 
evaluated using flow file attributes and variable 
registry)</strong></td></tr><tr><td id="name"><strong>Type</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
type of this document to be deleted<br/><strong>Supports Expression Language: 
true (will be evaluated using flow file attributes and variable 
registry)</strong></td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>retry</td><td>A
 FlowFile is routed to this relationship if the document cannot be deleted b
 ecause or retryable exception like timeout or node not 
available</td></tr><tr><td>success</td><td>All FlowFile corresponding to the 
deleted document from Elasticsearch are routed to this 
relationship</td></tr><tr><td>failure</td><td>All FlowFile corresponding to 
delete document that failed from Elasticsearch are routed to this 
relationship</td></tr><tr><td>not found</td><td>A FlowFile is routed to this 
relationship if the specified document was not found in 
elasticsearch</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>es.error.message</td><td>The
 message attribute in case of error</td></tr><tr><td>filename</td><td>The 
filename attribute which is set to the document 
identifier</td></tr><tr><td>es.index</td><td>The Elasticsearch index containing 
the document</td></tr><tr><td>es.type</td><td>The Elasticsearch document 
type</td></tr><tr><td>es.rest.status</td><td>The fi
 lename attribute with rest status</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.<h3>See 
Also:</h3><p><a 
href="../org.apache.nifi.processors.elasticsearch.FetchElasticsearch5/index.html">FetchElasticsearch5</a>,
 <a 
href="../org.apache.nifi.processors.elasticsearch.PutElasticsearch5/index.html">PutElasticsearch5</a></p></body></html>
\ No newline at end of file


Reply via email to