Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.HashContent/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.HashContent/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.HashContent/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.HashContent/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>HashContent</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;">HashContent</h1><h2>Description: </h2><p>Calculates a 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</p><h3>Tags: </h3><p>hash, content, MD5, SHA-1, 
SHA-256</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">hash.value</td><td id="allowable-values"></td><td 
id="description">The name of the FlowFile Attribute into which the Hash Value 
should be written. If the value already exists, it will be 
overwritten</td></tr><tr><td id="name"><strong>Hash Algorithm</strong></td><td 
id="default-value">MD5</td><td 
id="allowable-values"><ul><li>SHA-1</li><li>SHA-384</li><li>SKEIN-512-256</li><li>SKEIN-1024-384</li><li>BLAKE2B-160</li><li>SHA</li><li>KECCAK-288</li><li>WHIRLPOOL</li><li>SKEIN-512-384</li><li>SHA-224</li><li>SM3</li><li>BLAKE2B-512</li><li>GOST3411-2012-512</li><li>KECCAK-256</li><li>SKEIN-512-128</li><li>BLAKE2B-384</li><li>SKEIN-256-160</li><li>OID.2.16.840.1.101.3.4.2.10</li><li>DSTU7564-256</li><li>SHA-256</li><li>BLAKE2S-224</li><li>SHA3-256</li><li>KECCAK-384</li><li>SKEIN-256-128</li><li>DSTU7564-384</li><li>KECCAK-224</li><li>SKEIN-512-512</li><li>SKEIN-1024-512</li><li>SKEIN-512-160</li><li>OID.
 
1.2.804.2.1.1.1.1.2.2.3</li><li>GOST3411</li><li>1.2.804.2.1.1.1.1.2.2.3</li><li>BLAKE2B-256</li><li>OID.1.2.804.2.1.1.1.1.2.2.2</li><li>SKEIN-1024-1024</li><li>OID.1.2.804.2.1.1.1.1.2.2.1</li><li>SHA3-384</li><li>OID.2.16.840.1.101.3.4.2.9</li><li>BLAKE2S-256</li><li>SHA-512/224</li><li>OID.2.16.840.1.101.3.4.2.8</li><li>OID.2.16.840.1.101.3.4.2.7</li><li>TIGER</li><li>RIPEMD256</li><li>SKEIN-256-256</li><li>SHA3-224</li><li>SHA3-512</li><li>RIPEMD320</li><li>2.16.840.1.101.3.4.2.9</li><li>RIPEMD160</li><li>GOST3411-2012-256</li><li>2.16.840.1.101.3.4.2.8</li><li>1.2.804.2.1.1.1.1.2.2.1</li><li>KECCAK-512</li><li>SKEIN-512-224</li><li>2.16.840.1.101.3.4.2.7</li><li>1.2.804.2.1.1.1.1.2.2.2</li><li>2.16.840.1.101.3.4.2.10</li><li>BLAKE2S-160</li><li>SHA-512/256</li><li>MD2</li><li>RIPEMD128</li><li>MD4</li><li>SHA-512</li><li>SKEIN-256-224</li><li>MD5</li><li>BLAKE2S-128</li><li>DSTU7564-512</li></ul></td><td
 id="description">Determines what hashing algorithm should be used to perfor
 m the hashing function</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>FlowFiles
 that are process successfully will be sent to this 
relationship</td></tr><tr><td>failure</td><td>Any FlowFile that cannot be 
processed successfully will be sent to this relationship without any attribute 
being added</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 the 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 
Resou
 rce Considerations:</h3>None specified.</body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.IdentifyMimeType/additionalDetails.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.IdentifyMimeType/additionalDetails.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.IdentifyMimeType/additionalDetails.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.IdentifyMimeType/additionalDetails.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1,64 @@
+<!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>IdentifyMimeType</title>
+
+        <link rel="stylesheet" href="../../../../../css/component-usage.css" 
type="text/css" />
+    </head>
+
+    <body>
+        <p>The following is a non-exhaustive list of MIME Types detected:
+        </p>
+        <ul>
+            <li>application/gzip</li>
+            <li>application/bzip2</li>
+            <li>application/flowfile-v3</li>
+            <li>application/flowfile-v1</li>
+            <li>application/xml</li>
+            <li>video/mp4</li>
+            <li>video/x-m4v</li>
+            <li>video/mp4a-latm</li>
+            <li>video/quicktime</li>
+            <li>video/mpeg</li>
+            <li>audio/wav</li>
+            <li>audio/mp3</li>
+            <li>image/bmp</li>
+            <li>image/png</li>
+            <li>image/jpg</li>
+            <li>image/gif</li>
+            <li>image/tif</li>
+            <li>application/vnd.ms-works</li>
+            <li>application/msexcel</li>
+            <li>application/mspowerpoint</li>
+            <li>application/msaccess</li>
+            <li>application/x-ms-wmv</li>
+            <li>application/pdf</li>
+            <li>application/x-rpm</li>
+            <li>application/tar</li>
+            <li>application/x-7z-compressed</li>
+            <li>application/java-archive</li>
+            <li>application/zip</li>
+            <li>application/x-lzh</li>
+        </ul>
+        <p>For a complete list, please refer to
+            <a 
href="https://git-wip-us.apache.org/repos/asf?p=tika.git;a=blob;f=tika-core/src/main/resources/org/apache/tika/mime/tika-mimetypes.xml;h=fffb9bbca8f49d2265479da798c0c01ceb2060e2;hb=d647a234783bbc3f83d3691a1e1d5788c438d55d";>
+                Apache Tika's source code</a>
+        </p>
+
+    </body>
+</html>

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.IdentifyMimeType/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.IdentifyMimeType/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.IdentifyMimeType/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.IdentifyMimeType/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>IdentifyMimeType</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;">IdentifyMimeType</h1><h2>Description: </h2><p>Attempts to identify the 
MIME Type used for a FlowFile. If the MIME Type can be identified, an attribute 
with the name 'mime.type' is added with the value being the MIME Type. If the 
MIME Type cannot be determined, the value will be set to 
'application/octet-stream'. In addition, the attribute mime.extension will be 
set if a common file extension for the MIME Type is known.</p><p><a 
href="additionalDetails.html">Additional Details...</a></p><h3>Tags: 
</h3><p>compression, gzip, bzip2, zip, MIME, mime.type, file, 
identify</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>Use Filename In 
Detection</strong></td><td id="default-value">true</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">If true will pass the filename to Tika to aid in 
detection.</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 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>mime.type</td><td>This
 Processor sets the FlowFile's mime.type attribute to the detected MIME Type. 
If unable to 
 detect the MIME Type, the attribute's value will be set to 
application/octet-stream</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-standard-nar/1.6.0/org.apache.nifi.processors.standard.InvokeHTTP/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.InvokeHTTP/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.InvokeHTTP/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.InvokeHTTP/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>InvokeHTTP</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;">InvokeHTTP</h1><h2>Description: </h2><p>An HTTP client processor which 
can interact with a configurable HTTP Endpoint. The destination URL and HTTP 
Method are configurable. FlowFile attributes are converted to HTTP headers and 
the FlowFile contents are included as the body of the request (if the HTTP 
Method is PUT, POST or PATCH).</p><h3>Tags: </h3><p>http, https, rest, 
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, 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>HTTP 
Method</strong></td><td id="default-value">GET</td><td 
id="allowable-values"></td><td id="description">HTTP request method (GET, POST, 
PUT, PATCH, DELETE, HEAD, OPTIONS). Arbitrary methods are also supported. 
Methods other than POST, PUT and PATCH will be sent without a message 
body.<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
id="name"><strong>Remote URL</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="des
 cription">Remote URL which will be connected to, including scheme, host, port, 
path.<br/><strong>Supports Expression Language: true</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.6.0/org.apache.nifi.ssl.StandardSSLContextService/index.html">StandardSSLContextService</a><br/><a
 
href="../../../nifi-ssl-context-service-nar/1.6.0/org.apache.nifi.ssl.StandardRestrictedSSLContextService/index.html">StandardRestrictedSSLContextService</a></td><td
 id="description">The SSL Context Service used to provide client certificate 
information for TLS/SSL (https) connections. It is also used to connect to 
HTTPS Proxy.</td></tr><tr><td id="name"><strong>Connection 
Timeout</strong></td><td id="default-value">5 secs</td><td 
id="allowable-values"></td><td id="description">Max wait time for 
 connection to remote service.</td></tr><tr><td id="name"><strong>Read 
Timeout</strong></td><td id="default-value">15 secs</td><td 
id="allowable-values"></td><td id="description">Max wait time for response from 
remote service.</td></tr><tr><td id="name"><strong>Include Date 
Header</strong></td><td id="default-value">True</td><td 
id="allowable-values"><ul><li>True</li><li>False</li></ul></td><td 
id="description">Include an RFC-2616 Date header in the 
request.</td></tr><tr><td id="name"><strong>Follow Redirects</strong></td><td 
id="default-value">True</td><td 
id="allowable-values"><ul><li>True</li><li>False</li></ul></td><td 
id="description">Follow HTTP redirects issued by remote 
server.</td></tr><tr><td id="name">Attributes to Send</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Regular expression that defines which attributes to send as 
HTTP headers in the request. If not defined, no attributes are sent as headers. 
Also any dynamic properties set w
 ill be sent as headers. The dynamic property key will be the header key and 
the dynamic property value will be interpreted as expression language will be 
the header value.</td></tr><tr><td id="name">Basic Authentication 
Username</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">The username to be used by the client to authenticate against 
the Remote URL.  Cannot include control characters (0-31), ':', or DEL 
(127).</td></tr><tr><td id="name">Basic Authentication Password</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
password to be used by the client to authenticate against the Remote 
URL.<br/><strong>Sensitive Property: true</strong></td></tr><tr><td 
id="name">Proxy Host</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The fully qualified hostname or 
IP address of the proxy server<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Proxy Port<
 /td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">The port of the proxy server<br/><strong>Supports Expression 
Language: true</strong></td></tr><tr><td id="name">Proxy Type</td><td 
id="default-value">http</td><td id="allowable-values"></td><td 
id="description">The type of the proxy we are connecting to. Must be either 
http or https<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Proxy Username</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Username to set when authenticating against 
proxy<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
id="name">Proxy Password</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Password to set when 
authenticating against proxy<br/><strong>Sensitive Property: 
true</strong><br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Put Response Body In Attribute</td><
 td id="default-value"></td><td id="allowable-values"></td><td 
id="description">If set, the response body received back will be put into an 
attribute of the original FlowFile instead of a separate FlowFile. The 
attribute key to put to is determined by evaluating value of this property. 
<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
id="name">Max Length To Put In Attribute</td><td id="default-value">256</td><td 
id="allowable-values"></td><td id="description">If routing the response body to 
an attribute of the original (by setting the "Put response body in attribute" 
property or by receiving an error status code), the number of characters put to 
the attribute value will be at most this amount. This is important because 
attributes are held in memory and large attributes will quickly cause out of 
memory issues. If the output goes longer than this value, it will be truncated 
to fit. Consider making this smaller if able.</td></tr><tr><td id="name">Use 
Digest Auth
 entication</td><td id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Whether to communicate with the website using Digest 
Authentication. 'Basic Authentication Username' and 'Basic Authentication 
Password' are used for authentication.</td></tr><tr><td id="name">Always Output 
Response</td><td id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Will force a response FlowFile to be generated and routed to 
the 'Response' relationship regardless of what the server status code received 
is or if the processor is configured to put the server response body in the 
request attribute. In the later configuration a request FlowFile with the 
response body in the attribute and a typical response FlowFile will be emitted 
to their respective relationships.</td></tr><tr><td id="name">Trusted 
Hostname</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="d
 escription">Bypass the normal truststore hostname verifier to allow the 
specified remote hostname as trusted. Enabling this property has MITM security 
implications, use wisely. Will still accept other connections based on the 
normal truststore hostname verifier. Only valid with SSL (HTTPS) 
connections.</td></tr><tr><td id="name">Add Response Headers to Request</td><td 
id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Enabling this property saves all the response headers to the 
original request. This may be when the response headers are needed but a 
response is not generated due to the status code received.</td></tr><tr><td 
id="name"><strong>Content-Type</strong></td><td 
id="default-value">${mime.type}</td><td id="allowable-values"></td><td 
id="description">The Content-Type to specify for when content is being 
transmitted through a PUT, POST or PATCH. In the case of an empty value after 
evaluating an expression langua
 ge expression, Content-Type defaults to 
application/octet-stream<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Send Message Body</td><td 
id="default-value">true</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">If true, sends the HTTP message body on POST/PUT/PATCH 
requests (default).  If false, suppresses the message body and content-type 
header for these requests.</td></tr><tr><td id="name"><strong>Use Chunked 
Encoding</strong></td><td id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">When POST'ing, PUT'ing or PATCH'ing content set this property 
to true in order to not pass the 'Content-length' header and instead send 
'Transfer-Encoding' with a value of 'chunked'. This will enable the data 
transfer mechanism which was introduced in HTTP 1.1 to pass data of unknown 
lengths in chunks.</td></tr><tr><td id="name">Penalize on "No Retry"</td><
 td id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Enabling this property will penalize FlowFiles that are routed 
to the "No Retry" relationship.</td></tr><tr><td id="name"><strong>Use HTTP 
ETag</strong></td><td id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Enable HTTP entity tag (ETag) support for HTTP 
requests.</td></tr><tr><td id="name"><strong>Maximum ETag Cache 
Size</strong></td><td id="default-value">10MB</td><td 
id="allowable-values"></td><td id="description">The maximum size that the ETag 
cache should be allowed to grow to. The default size is 
10MB.</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">Header Name</td><td id="value">Attribute Expression Lang
 uage</td><td>Send request header with a key matching the Dynamic Property Key 
and a value created by evaluating the Attribute Expression Language set in the 
value of the Dynamic Property.<br/><strong>Supports Expression Language: 
true</strong></td></tr></table></p><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>Original</td><td>The
 original FlowFile will be routed upon success (2xx status codes). It will have 
new attributes detailing the success of the 
request.</td></tr><tr><td>Failure</td><td>The original FlowFile will be routed 
on any type of connection failure, timeout or general exception. It will have 
new attributes detailing the request.</td></tr><tr><td>Retry</td><td>The 
original FlowFile will be routed on any status code that can be retried (5xx 
status codes). It will have new attributes detailing the 
request.</td></tr><tr><td>No Retry</td><td>The original FlowFile will be routed 
on any status code that should NOT be retrie
 d (1xx, 3xx, 4xx status codes).  It will have new attributes detailing the 
request.</td></tr><tr><td>Response</td><td>A Response FlowFile will be routed 
upon success (2xx status codes). If the 'Output Response Regardless' property 
is true then the response will be sent to this relationship regardless of the 
status code received.</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>invokehttp.status.code</td><td>The
 status code that is 
returned</td></tr><tr><td>invokehttp.status.message</td><td>The status message 
that is returned</td></tr><tr><td>invokehttp.response.body</td><td>In the 
instance where the status code received is not a success (2xx) then the 
response body will be put to the 'invokehttp.response.body' attribute of the 
request FlowFile.</td></tr><tr><td>invokehttp.request.url</td><td>The request 
URL</td></tr><tr><td>invokehttp.tx.id</td><td>The transaction ID
  that is returned after reading the 
response</td></tr><tr><td>invokehttp.remote.dn</td><td>The DN of the remote 
server</td></tr><tr><td>invokehttp.java.exception.class</td><td>The Java 
exception class raised when the processor 
fails</td></tr><tr><td>invokehttp.java.exception.message</td><td>The Java 
exception message raised when the processor 
fails</td></tr><tr><td>user-defined</td><td>If the 'Put Response Body In 
Attribute' property is set then whatever it is set to will become the attribute 
key and the value would be the body of the HTTP 
response.</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 allows 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-standard-nar/1.6.0/org.apache.nifi.processors.standard.JoltTransformJSON/additionalDetails.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.JoltTransformJSON/additionalDetails.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.JoltTransformJSON/additionalDetails.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.JoltTransformJSON/additionalDetails.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1,40 @@
+<!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>JoltTransformJSON</title>
+    <link rel="stylesheet" href="../../../../../css/component-usage.css" 
type="text/css"/>
+</head>
+
+<body>
+<!-- Processor Documentation 
================================================== -->
+<h2>Usage Information</h2>
+
+<p>
+    The Jolt utilities processing JSON are not not stream based therefore 
large JSON document
+    transformation may consume large amounts of memory. Currently UTF-8 
FlowFile content and Jolt specifications are supported.
+    A specification can be defined using Expression Language where attributes 
can be referred either on the left or right hand side within the specification 
syntax.
+
+    Custom Jolt Transformations (that implement the Transform interface) are 
supported.  Modules containing custom libraries which do not
+    existing on the current class path can be included via the custom module 
directory property.
+
+    <Strong>Note:</Strong> When configuring a processor if user selects of the 
Default transformation yet provides a
+    Chain specification the system does not alert that the specification is 
invalid and and will produce failed flow files.
+    This is a known issue identified within the Jolt library.
+</p>
+</body>
+</html>

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.JoltTransformJSON/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.JoltTransformJSON/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.JoltTransformJSON/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.JoltTransformJSON/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>JoltTransformJSON</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;">JoltTransformJSON</h1><h2>Description: </h2><p>Applies a list of Jolt 
specifications to the flowfile JSON payload. A new FlowFile is created with 
transformed content and is routed to the 'success' relationship. If the JSON 
transform fails, the original FlowFile is routed to the 'failure' 
relationship.</p><p><a href="additionalDetails.html">Additional 
Details...</a></p><h3>Tags: </h3><p>json, jolt, transform, shiftr, chainr, 
defaultr, removr, cardinality, sort</p><h3>Properties: </h3><p>In the list 
below, the names of required properties appear in <strong>bold</strong>. Any 
other properties (no
 t 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>Jolt Transformation DSL</strong></td><td 
id="default-value">jolt-transform-chain</td><td 
id="allowable-values"><ul><li>Cardinality <img 
src="../../../../../html/images/iconInfo.png" alt="Change the cardinality of 
input elements to create the output JSON." title="Change the cardinality of 
input elements to create the output JSON."></img></li><li>Chain <img 
src="../../../../../html/images/iconInfo.png" alt="Execute list of Jolt 
transformations." title="Execute list of Jolt 
transformations."></img></li><li>Default <img 
src="../../../../../html/images/iconInfo.png" alt=" Apply default values to the 
output JSON." title=" Apply default values to 
 the output JSON."></img></li><li>Modify - Default <img 
src="../../../../../html/images/iconInfo.png" alt="Writes when key is missing 
or value is null" title="Writes when key is missing or value is 
null"></img></li><li>Modify - Define <img 
src="../../../../../html/images/iconInfo.png" alt="Writes when key is missing" 
title="Writes when key is missing"></img></li><li>Modify - Overwrite <img 
src="../../../../../html/images/iconInfo.png" alt=" Always overwrite value" 
title=" Always overwrite value"></img></li><li>Remove <img 
src="../../../../../html/images/iconInfo.png" alt=" Remove values from input 
data to create the output JSON." title=" Remove values from input data to 
create the output JSON."></img></li><li>Shift <img 
src="../../../../../html/images/iconInfo.png" alt="Shift input JSON/data to 
create the output JSON." title="Shift input JSON/data to create the output 
JSON."></img></li><li>Sort <img src="../../../../../html/images/iconInfo.png" 
alt="Sort input json key values alphabe
 tically. Any specification set is ignored." title="Sort input json key values 
alphabetically. Any specification set is ignored."></img></li><li>Custom <img 
src="../../../../../html/images/iconInfo.png" alt="Custom Transformation. 
Requires Custom Transformation Class Name" title="Custom Transformation. 
Requires Custom Transformation Class Name"></img></li></ul></td><td 
id="description">Specifies the Jolt Transformation that should be used with the 
provided specification.</td></tr><tr><td id="name">Custom Transformation Class 
Name</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">Fully Qualified Class Name for Custom 
Transformation</td></tr><tr><td id="name">Custom Module Directory</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Comma-separated list of paths to files and/or directories 
which contain modules containing custom transformations (that are not included 
on NiFi's classpath).</td></tr><tr><td id="name">Jolt
  Specification</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Jolt Specification for 
transform of JSON data. This value is ignored if the Jolt Sort Transformation 
is selected.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Transform Cache 
Size</strong></td><td id="default-value">1</td><td 
id="allowable-values"></td><td id="description">Compiling a Jolt Transform can 
be fairly expensive. Ideally, this will be done only once. However, if the 
Expression Language is used in the transform, we may need a new Transform for 
each FlowFile. This value controls how many of those Transforms we cache in 
memory in order to avoid having to compile the Transform each 
time.</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>The
 FlowFile with transformed content will be routed to this 
relationship</td></tr><tr><td>failure</td><td>If a FlowF
 ile fails processing for any reason (for example, the FlowFile is not valid 
JSON), it will be 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>mime.type</td><td>Always
 set to application/json</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-standard-nar/1.6.0/org.apache.nifi.processors.standard.ListDatabaseTables/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.ListDatabaseTables/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.ListDatabaseTables/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.ListDatabaseTables/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ListDatabaseTables</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;">ListDatabaseTables</h1><h2>Description: </h2><p>Generates a set of flow 
files, each containing attributes corresponding to metadata about a table from 
a database connection. Once metadata about a table has been fetched, it will 
not be fetched again until the Refresh Interval (if set) has elapsed, or until 
state has been manually cleared.</p><h3>Tags: </h3><p>sql, list, jdbc, table, 
database</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 defa
 ult 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>Database Connection Pooling Service</strong></td><td 
id="default-value"></td><td id="allowable-values"><strong>Controller Service 
API: </strong><br/>DBCPService<br/><strong>Implementations: </strong><a 
href="../../../nifi-dbcp-service-nar/1.6.0/org.apache.nifi.dbcp.DBCPConnectionPool/index.html">DBCPConnectionPool</a><br/><a
 
href="../../../nifi-hive-nar/1.6.0/org.apache.nifi.dbcp.hive.HiveConnectionPool/index.html">HiveConnectionPool</a></td><td
 id="description">The Controller Service that is used to obtain connection to 
database</td></tr><tr><td id="name">Catalog</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The name of a catalog from 
which to list database tables. The name must match the catalog name as it is 
stored in the database. If the property is not set, the catalog name will not 
be used
  to narrow the search for tables. If the property is set to an empty string, 
tables without a catalog will be listed.</td></tr><tr><td id="name">Schema 
Pattern</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">A pattern for matching schemas in the database. Within a 
pattern, "%" means match any substring of 0 or more characters, and "_" means 
match any one character. The pattern must match the schema name as it is stored 
in the database. If the property is not set, the schema name will not be used 
to narrow the search for tables. If the property is set to an empty string, 
tables without a schema will be listed.</td></tr><tr><td id="name">Table Name 
Pattern</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">A pattern for matching tables in the database. Within a 
pattern, "%" means match any substring of 0 or more characters, and "_" means 
match any one character. The pattern must match the table name as it is stored i
 n the database. If the property is not set, all tables will be 
retrieved.</td></tr><tr><td id="name">Table Types</td><td 
id="default-value">TABLE</td><td id="allowable-values"></td><td 
id="description">A comma-separated list of table types to include. For example, 
some databases support TABLE and VIEW types. If the property is not set, tables 
of all types will be returned.</td></tr><tr><td id="name"><strong>Include 
Count</strong></td><td id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Whether to include the table's row count as a flow file 
attribute. This affects performance as a database query will be generated for 
each table in the retrieved list.</td></tr><tr><td id="name"><strong>Refresh 
Interval</strong></td><td id="default-value">0 sec</td><td 
id="allowable-values"></td><td id="description">The amount of time to elapse 
before resetting the processor state, thereby causing all current tables to be 
listed. Duri
 ng this interval, the processor may continue to run, but tables that have 
already been listed will not be re-listed. However new/added tables will be 
listed as the processor runs. A value of zero means the state will never be 
automatically reset, the user must Clear State 
manually.</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>All
 FlowFiles that are received are 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>db.table.name</td><td>Contains
 the name of a database table from the 
connection</td></tr><tr><td>db.table.catalog</td><td>Contains the name of the 
catalog to which the table belongs (may be 
null)</td></tr><tr><td>db.table.schema</td><td>Contains the name of the schema 
to which the table belongs (may be 
null)</td></tr><tr><td>db.table.fullname</td><td>Contain
 s the fully-qualifed table name (possibly including catalog, schema, 
etc.)</td></tr><tr><td>db.table.type</td><td>Contains the type of the database 
table from the connection. Typical types are "TABLE", "VIEW", "SYSTEM TABLE", 
"GLOBAL TEMPORARY", "LOCAL TEMPORARY", "ALIAS", 
"SYNONYM"</td></tr><tr><td>db.table.remarks</td><td>Contains the name of a 
database table from the 
connection</td></tr><tr><td>db.table.count</td><td>Contains the number of rows 
in the table</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 listing of tables, the timestamp of the query is stored. This 
allows the Processor to not re-list tables the next time that the Processor is 
run. Specifying the refresh interval in the processor properties will indicate 
that when the processor detects the interval has elapsed, the state will be 
reset and tables will be re-listed as a result. This processor is meant to be 
run on 
 the primary node only.</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-standard-nar/1.6.0/org.apache.nifi.processors.standard.ListFTP/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.ListFTP/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.ListFTP/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.ListFTP/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ListFTP</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;">ListFTP</h1><h2>Description: </h2><p>Performs a listing of the files 
residing on an FTP server. For each file that is found on the remote server, a 
new FlowFile will be created with the filename attribute set to the name of the 
file on the remote server. This can then be used in conjunction with FetchFTP 
in order to fetch those files.</p><h3>Tags: </h3><p>list, ftp, remote, ingest, 
source, input, files</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 def
 ault 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>Hostname</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The fully qualified hostname or 
IP address of the remote system<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Port</strong></td><td 
id="default-value">21</td><td id="allowable-values"></td><td 
id="description">The port to connect to on the remote host to fetch the data 
from<br/><strong>Supports Expressio
 n Language: true</strong></td></tr><tr><td 
id="name"><strong>Username</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Username<br/><strong>Supports 
Expression Language: true</strong></td></tr><tr><td id="name">Password</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Password for the user account<br/><strong>Sensitive Property: 
true</strong><br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Remote Path</td><td 
id="default-value">.</td><td id="allowable-values"></td><td 
id="description">The path on the remote system from which to pull or push 
files<br/><strong>Supports Expression Language: true</strong></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-redis-nar/1.6.0/org.apache.nif
 
i.redis.service.RedisDistributedMapCacheClientService/index.html">RedisDistributedMapCacheClientService</a><br/><a
 
href="../../../nifi-distributed-cache-services-nar/1.6.0/org.apache.nifi.distributed.cache.client.DistributedMapCacheClientService/index.html">DistributedMapCacheClientService</a><br/><a
 
href="../../../nifi-hbase_1_1_2-client-service-nar/1.6.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 the remote server so that if a 
new node begins pulling data, it won't duplicate all of the work that has been 
done. If not specified, the information will not be shared across the cluster. 
This property does not need to be set for standalone instances of NiFi but 
should be configured if NiFi is run within a cluster.</td></tr><tr><td 
id="name"><strong>Search Recursively</strong></td><td id="default-val
 ue">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">If true, will pull files from arbitrarily nested 
subdirectories; otherwise, will not traverse subdirectories</td></tr><tr><td 
id="name">File Filter Regex</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Provides a Java Regular 
Expression for filtering Filenames; if a filter is supplied, only files whose 
names match that Regular Expression will be fetched</td></tr><tr><td 
id="name">Path Filter Regex</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">When Search Recursively is 
true, then only subdirectories whose path matches the given Regular Expression 
will be scanned</td></tr><tr><td id="name"><strong>Ignore Dotted 
Files</strong></td><td id="default-value">true</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">If true, files whose names begin with a dot (".") will be 
ignore
 d</td></tr><tr><td id="name"><strong>Remote Poll Batch Size</strong></td><td 
id="default-value">5000</td><td id="allowable-values"></td><td 
id="description">The value specifies how many file paths to find in a given 
directory on the remote system when doing a file listing. This value in general 
should not need to be modified but when polling against a remote system with a 
tremendous number of files this value can be critical.  Setting this value too 
high can result very poor performance and setting it too low can cause the flow 
to be slower than normal.</td></tr><tr><td id="name"><strong>Connection 
Timeout</strong></td><td id="default-value">30 sec</td><td 
id="allowable-values"></td><td id="description">Amount of time to wait before 
timing out while creating a connection</td></tr><tr><td id="name"><strong>Data 
Timeout</strong></td><td id="default-value">30 sec</td><td 
id="allowable-values"></td><td id="description">When transferring a file 
between the local and remote system, this v
 alue specifies how long is allowed to elapse without any data being 
transferred between systems</td></tr><tr><td id="name">Connection Mode</td><td 
id="default-value">Passive</td><td 
id="allowable-values"><ul><li>Active</li><li>Passive</li></ul></td><td 
id="description">The FTP Connection Mode</td></tr><tr><td id="name">Transfer 
Mode</td><td id="default-value">Binary</td><td 
id="allowable-values"><ul><li>Binary</li><li>ASCII</li></ul></td><td 
id="description">The FTP Transfer Mode</td></tr><tr><td id="name">Proxy 
Type</td><td id="default-value">DIRECT</td><td 
id="allowable-values"><ul><li>DIRECT</li><li>HTTP</li><li>SOCKS</li></ul></td><td
 id="description">Proxy type used for file transfers</td></tr><tr><td 
id="name">Proxy Host</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The fully qualified hostname or 
IP address of the proxy server</td></tr><tr><td id="name">Proxy Port</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="desc
 ription">The port of the proxy server</td></tr><tr><td id="name">Http Proxy 
Username</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">Http Proxy Username</td></tr><tr><td id="name">Http Proxy 
Password</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">Http Proxy Password<br/><strong>Sensitive Property: 
true</strong></td></tr><tr><td id="name">Internal Buffer Size</td><td 
id="default-value">16KB</td><td id="allowable-values"></td><td 
id="description">Set the internal buffer size for buffered data 
streams</td></tr><tr><td id="name"><strong>Target System Timestamp 
Precision</strong></td><td id="default-value">auto-detect</td><td 
id="allowable-values"><ul><li>Auto Detect <img 
src="../../../../../html/images/iconInfo.png" alt="Automatically detect time 
unit deterministically based on candidate entries timestamp. Please note that 
this option may take longer to list entities unnecessarily, if none of entries 
has a precise 
 precision timestamp. E.g. even if a target system supports millis, if all 
entries only have timestamps without millis, such as '2017-06-16 09:06:34.000', 
then its precision is determined as 'seconds'." title="Automatically detect 
time unit deterministically based on candidate entries timestamp. Please note 
that this option may take longer to list entities unnecessarily, if none of 
entries has a precise precision timestamp. E.g. even if a target system 
supports millis, if all entries only have timestamps without millis, such as 
'2017-06-16 09:06:34.000', then its precision is determined as 
'seconds'."></img></li><li>Milliseconds <img 
src="../../../../../html/images/iconInfo.png" alt="This option provides the 
minimum latency for an entry from being available to being listed if target 
system supports millis, if not, use other options." title="This option provides 
the minimum latency for an entry from being available to being listed if target 
system supports millis, if not, use other op
 tions."></img></li><li>Seconds <img 
src="../../../../../html/images/iconInfo.png" alt="For a target system that 
does not have millis precision, but has in seconds." title="For a target system 
that does not have millis precision, but has in 
seconds."></img></li><li>Minutes <img 
src="../../../../../html/images/iconInfo.png" alt="For a target system that 
only supports precision in minutes." title="For a target system that only 
supports precision in minutes."></img></li></ul></td><td 
id="description">Specify timestamp precision at the target system. Since this 
processor uses timestamp of entities to decide which should be listed, it is 
crucial to use the right timestamp 
precision.</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>All
 FlowFiles that are received are 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>ftp.remote.host</td><td>The 
 >hostname of the FTP Server</td></tr><tr><td>ftp.remote.port</td><td>The port 
 >that was connected to on the FTP 
 >Server</td></tr><tr><td>ftp.listing.user</td><td>The username of the user 
 >that performed the FTP Listing</td></tr><tr><td>file.owner</td><td>The 
 >numeric owner id of the source file</td></tr><tr><td>file.group</td><td>The 
 >numeric group id of the source 
 >file</td></tr><tr><td>file.permissions</td><td>The read/write/execute 
 >permissions of the source file</td></tr><tr><td>file.size</td><td>The number 
 >of bytes in the source 
 >file</td></tr><tr><td>file.lastModifiedTime</td><td>The timestamp of when the 
 >file in the filesystem waslast modified as 
 >'yyyy-MM-dd'T'HH:mm:ssZ'</td></tr><tr><td>filename</td><td>The name of the 
 >file on the SFTP Server</td></tr><tr><td>path</td><td>The fully qualified 
 >name of the directory on the SFTP Server from which the file was 
 >pulled</td></tr></table><h3>State management: </h3><table i
 
d="stateful"><tr><th>Scope</th><th>Description</th></tr><tr><td>CLUSTER</td><td>After
 performing a listing of files, the timestamp of the newest file is stored. 
This allows the Processor to list only files that have been added or modified 
after this date the next time that the Processor is run. State is stored across 
the cluster so that this Processor can be run on Primary Node only and if a new 
Primary Node is selected, the new node will not duplicate the data that was 
listed by the previous Primary Node.</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.<h3>See Also:</h3><p><a 
href="../org.apache.nifi.processors.standard.FetchFTP/index.html">FetchFTP</a>, 
<a href="../org.apache.nifi.processors.standard.GetFTP/index.html">GetFTP</a>, 
<a 
href="../org.apache.nifi.processors.standard.PutFTP/index.html">PutFTP</a></p></body></htm
 l>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.ListFile/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.ListFile/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.ListFile/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.ListFile/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ListFile</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;">ListFile</h1><h2>Description: </h2><p>Retrieves a listing of files from 
the local filesystem. For each file that is listed, creates a FlowFile that 
represents the file so that it can be fetched in conjunction with FetchFile. 
This Processor is designed to run on Primary Node only in a cluster. If the 
primary node changes, the new Primary Node will pick up where the previous node 
left off without duplicating all of the data. Unlike GetFile, this Processor 
does not delete any data from the local filesystem.</p><h3>Tags: </h3><p>file, 
get, list, ingest, source, filesystem</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>Input Directory</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The input directory from which 
files to pull files<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Recurse 
Subdirectories</strong></td><td id="default-value">true</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Indicates whether to list files from subdirectories of the 
directory</td></tr><tr><td id="name"><strong>Input Directory Location</strong></
 td><td id="default-value">Local</td><td id="allowable-values"><ul><li>Local 
<img src="../../../../../html/images/iconInfo.png" alt="Input Directory is 
located on a local disk. State will be stored locally on each node in the 
cluster." title="Input Directory is located on a local disk. State will be 
stored locally on each node in the cluster."></img></li><li>Remote <img 
src="../../../../../html/images/iconInfo.png" alt="Input Directory is located 
on a remote system. State will be stored across the cluster so that the listing 
can be performed on Primary Node Only and another node can pick up where the 
last node left off, if the Primary Node changes" title="Input Directory is 
located on a remote system. State will be stored across the cluster so that the 
listing can be performed on Primary Node Only and another node can pick up 
where the last node left off, if the Primary Node 
changes"></img></li></ul></td><td id="description">Specifies where the Input 
Directory is located. This is use
 d to determine whether state should be stored locally or across the 
cluster.</td></tr><tr><td id="name"><strong>File Filter</strong></td><td 
id="default-value">[^\.].*</td><td id="allowable-values"></td><td 
id="description">Only files whose names match the given regular expression will 
be picked up</td></tr><tr><td id="name">Path Filter</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">When Recurse Subdirectories is true, then only subdirectories 
whose path matches the given regular expression will be 
scanned</td></tr><tr><td id="name"><strong>Minimum File Age</strong></td><td 
id="default-value">0 sec</td><td id="allowable-values"></td><td 
id="description">The minimum age that a file must be in order to be pulled; any 
file younger than this amount of time (according to last modification date) 
will be ignored</td></tr><tr><td id="name">Maximum File Age</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
maximum age
  that a file must be in order to be pulled; any file older than this amount of 
time (according to last modification date) will be ignored</td></tr><tr><td 
id="name"><strong>Minimum File Size</strong></td><td id="default-value">0 
B</td><td id="allowable-values"></td><td id="description">The minimum size that 
a file must be in order to be pulled</td></tr><tr><td id="name">Maximum File 
Size</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">The maximum size that a file can be in order to be 
pulled</td></tr><tr><td id="name"><strong>Ignore Hidden Files</strong></td><td 
id="default-value">true</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Indicates whether or not hidden files should be 
ignored</td></tr><tr><td id="name"><strong>Target System Timestamp 
Precision</strong></td><td id="default-value">auto-detect</td><td 
id="allowable-values"><ul><li>Auto Detect <img 
src="../../../../../html/images/iconInfo.png" al
 t="Automatically detect time unit deterministically based on candidate entries 
timestamp. Please note that this option may take longer to list entities 
unnecessarily, if none of entries has a precise precision timestamp. E.g. even 
if a target system supports millis, if all entries only have timestamps without 
millis, such as '2017-06-16 09:06:34.000', then its precision is determined as 
'seconds'." title="Automatically detect time unit deterministically based on 
candidate entries timestamp. Please note that this option may take longer to 
list entities unnecessarily, if none of entries has a precise precision 
timestamp. E.g. even if a target system supports millis, if all entries only 
have timestamps without millis, such as '2017-06-16 09:06:34.000', then its 
precision is determined as 'seconds'."></img></li><li>Milliseconds <img 
src="../../../../../html/images/iconInfo.png" alt="This option provides the 
minimum latency for an entry from being available to being listed if target syst
 em supports millis, if not, use other options." title="This option provides 
the minimum latency for an entry from being available to being listed if target 
system supports millis, if not, use other options."></img></li><li>Seconds <img 
src="../../../../../html/images/iconInfo.png" alt="For a target system that 
does not have millis precision, but has in seconds." title="For a target system 
that does not have millis precision, but has in 
seconds."></img></li><li>Minutes <img 
src="../../../../../html/images/iconInfo.png" alt="For a target system that 
only supports precision in minutes." title="For a target system that only 
supports precision in minutes."></img></li></ul></td><td 
id="description">Specify timestamp precision at the target system. Since this 
processor uses timestamp of entities to decide which should be listed, it is 
crucial to use the right timestamp 
precision.</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><t
 r><td>success</td><td>All FlowFiles that are received are 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>filename</td><td>The
 name of the file that was read from 
filesystem.</td></tr><tr><td>path</td><td>The path is set to the relative path 
of the file's directory on filesystem compared to the Input Directory property. 
 For example, if Input Directory is set to /tmp, then files picked up from /tmp 
will have the path attribute set to "/". If the Recurse Subdirectories property 
is set to true and a file is picked up from /tmp/abc/1/2/3, then the path 
attribute will be set to 
"abc/1/2/3/".</td></tr><tr><td>absolute.path</td><td>The absolute.path is set 
to the absolute path of the file's directory on filesystem. For example, if the 
Input Directory property is set to /tmp, then files picked up from /tmp will 
have the path attribute set to "/tmp/". If t
 he Recurse Subdirectories property is set to true and a file is picked up from 
/tmp/abc/1/2/3, then the path attribute will be set to 
"/tmp/abc/1/2/3/".</td></tr><tr><td>file.owner</td><td>The user that owns the 
file in filesystem</td></tr><tr><td>file.group</td><td>The group that owns the 
file in filesystem</td></tr><tr><td>file.size</td><td>The number of bytes in 
the file in filesystem</td></tr><tr><td>file.permissions</td><td>The 
permissions for the file in filesystem. This is formatted as 3 characters for 
the owner, 3 for the group, and 3 for other users. For example 
rw-rw-r--</td></tr><tr><td>file.lastModifiedTime</td><td>The timestamp of when 
the file in filesystem was last modified as 
'yyyy-MM-dd'T'HH:mm:ssZ'</td></tr><tr><td>file.lastAccessTime</td><td>The 
timestamp of when the file in filesystem was last accessed as 
'yyyy-MM-dd'T'HH:mm:ssZ'</td></tr><tr><td>file.creationTime</td><td>The 
timestamp of when the file in filesystem was created as 
'yyyy-MM-dd'T'HH:mm:ssZ'</td></t
 r></table><h3>State management: </h3><table 
id="stateful"><tr><th>Scope</th><th>Description</th></tr><tr><td>LOCAL, 
CLUSTER</td><td>After performing a listing of files, the timestamp of the 
newest file is stored. This allows the Processor to list only files that have 
been added or modified after this date the next time that the Processor is run. 
Whether the state is stored with a Local or Cluster scope depends on the value 
of the &lt;Input Directory Location&gt; 
property.</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.<h3>See Also:</h3><p><a 
href="../org.apache.nifi.processors.standard.GetFile/index.html">GetFile</a>, 
<a 
href="../org.apache.nifi.processors.standard.PutFile/index.html">PutFile</a>, 
<a 
href="../org.apache.nifi.processors.standard.FetchFile/index.html">FetchFile</a></p></body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.ListSFTP/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.ListSFTP/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.ListSFTP/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.ListSFTP/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ListSFTP</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;">ListSFTP</h1><h2>Description: </h2><p>Performs a listing of the files 
residing on an SFTP server. For each file that is found on the remote server, a 
new FlowFile will be created with the filename attribute set to the name of the 
file on the remote server. This can then be used in conjunction with FetchSFTP 
in order to fetch those files.</p><h3>Tags: </h3><p>list, sftp, remote, ingest, 
source, input, files</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 an
 y 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>Hostname</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The fully qualified hostname or 
IP address of the remote system<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Port</strong></td><td 
id="default-value">22</td><td id="allowable-values"></td><td 
id="description">The port to connect to on the remote host to fetch the data 
from<br/><strong>Supports Expr
 ession Language: true</strong></td></tr><tr><td 
id="name"><strong>Username</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Username<br/><strong>Supports 
Expression Language: true</strong></td></tr><tr><td id="name">Password</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Password for the user account<br/><strong>Sensitive Property: 
true</strong><br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Private Key Path</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
fully qualified path to the Private Key file<br/><strong>Supports Expression 
Language: true</strong></td></tr><tr><td id="name">Private Key 
Passphrase</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">Password for the private key<br/><strong>Sensitive Property: 
true</strong><br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><
 td id="name">Remote Path</td><td id="default-value">.</td><td 
id="allowable-values"></td><td id="description">The path on the remote system 
from which to pull or push files<br/><strong>Supports Expression Language: 
true</strong></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-redis-nar/1.6.0/org.apache.nifi.redis.service.RedisDistributedMapCacheClientService/index.html">RedisDistributedMapCacheClientService</a><br/><a
 
href="../../../nifi-distributed-cache-services-nar/1.6.0/org.apache.nifi.distributed.cache.client.DistributedMapCacheClientService/index.html">DistributedMapCacheClientService</a><br/><a
 
href="../../../nifi-hbase_1_1_2-client-service-nar/1.6.0/org.apache.nifi.hbase.HBase_1_1_2_ClientMapCacheService/index.html">HBase_1_1_2_ClientMapCacheService</a></td><td
 id="description">Spec
 ifies the Controller Service that should be used to maintain state about what 
has been pulled from the remote server so that if a new node begins pulling 
data, it won't duplicate all of the work that has been done. If not specified, 
the information will not be shared across the cluster. This property does not 
need to be set for standalone instances of NiFi but should be configured if 
NiFi is run within a cluster.</td></tr><tr><td id="name"><strong>Search 
Recursively</strong></td><td id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">If true, will pull files from arbitrarily nested 
subdirectories; otherwise, will not traverse subdirectories</td></tr><tr><td 
id="name">File Filter Regex</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Provides a Java Regular 
Expression for filtering Filenames; if a filter is supplied, only files whose 
names match that Regular Expression will be fetched<
 /td></tr><tr><td id="name">Path Filter Regex</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">When Search Recursively is true, then only subdirectories 
whose path matches the given Regular Expression will be 
scanned</td></tr><tr><td id="name"><strong>Ignore Dotted Files</strong></td><td 
id="default-value">true</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">If true, files whose names begin with a dot (".") will be 
ignored</td></tr><tr><td id="name"><strong>Strict Host Key 
Checking</strong></td><td id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Indicates whether or not strict enforcement of hosts keys 
should be applied</td></tr><tr><td id="name">Host Key File</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">If 
supplied, the given file will be used as the Host Key; otherwise, no use host 
key file will be
  used</td></tr><tr><td id="name"><strong>Connection Timeout</strong></td><td 
id="default-value">30 sec</td><td id="allowable-values"></td><td 
id="description">Amount of time to wait before timing out while creating a 
connection</td></tr><tr><td id="name"><strong>Data Timeout</strong></td><td 
id="default-value">30 sec</td><td id="allowable-values"></td><td 
id="description">When transferring a file between the local and remote system, 
this value specifies how long is allowed to elapse without any data being 
transferred between systems</td></tr><tr><td id="name"><strong>Send Keep Alive 
On Timeout</strong></td><td id="default-value">true</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Indicates whether or not to send a single Keep Alive message 
when SSH socket times out</td></tr><tr><td id="name"><strong>Target System 
Timestamp Precision</strong></td><td id="default-value">auto-detect</td><td 
id="allowable-values"><ul><li>Auto Detect <img src=
 "../../../../../html/images/iconInfo.png" alt="Automatically detect time unit 
deterministically based on candidate entries timestamp. Please note that this 
option may take longer to list entities unnecessarily, if none of entries has a 
precise precision timestamp. E.g. even if a target system supports millis, if 
all entries only have timestamps without millis, such as '2017-06-16 
09:06:34.000', then its precision is determined as 'seconds'." 
title="Automatically detect time unit deterministically based on candidate 
entries timestamp. Please note that this option may take longer to list 
entities unnecessarily, if none of entries has a precise precision timestamp. 
E.g. even if a target system supports millis, if all entries only have 
timestamps without millis, such as '2017-06-16 09:06:34.000', then its 
precision is determined as 'seconds'."></img></li><li>Milliseconds <img 
src="../../../../../html/images/iconInfo.png" alt="This option provides the 
minimum latency for an entry from be
 ing available to being listed if target system supports millis, if not, use 
other options." title="This option provides the minimum latency for an entry 
from being available to being listed if target system supports millis, if not, 
use other options."></img></li><li>Seconds <img 
src="../../../../../html/images/iconInfo.png" alt="For a target system that 
does not have millis precision, but has in seconds." title="For a target system 
that does not have millis precision, but has in 
seconds."></img></li><li>Minutes <img 
src="../../../../../html/images/iconInfo.png" alt="For a target system that 
only supports precision in minutes." title="For a target system that only 
supports precision in minutes."></img></li></ul></td><td 
id="description">Specify timestamp precision at the target system. Since this 
processor uses timestamp of entities to decide which should be listed, it is 
crucial to use the right timestamp 
precision.</td></tr></table><h3>Relationships: </h3><table id="relationships">
 <tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>All 
FlowFiles that are received are 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>sftp.remote.host</td><td>The
 hostname of the SFTP Server</td></tr><tr><td>sftp.remote.port</td><td>The port 
that was connected to on the SFTP 
Server</td></tr><tr><td>sftp.listing.user</td><td>The username of the user that 
performed the SFTP Listing</td></tr><tr><td>file.owner</td><td>The numeric 
owner id of the source file</td></tr><tr><td>file.group</td><td>The numeric 
group id of the source file</td></tr><tr><td>file.permissions</td><td>The 
read/write/execute permissions of the source 
file</td></tr><tr><td>file.size</td><td>The number of bytes in the source 
file</td></tr><tr><td>file.lastModifiedTime</td><td>The timestamp of when the 
file in the filesystem waslast modified as 'yyyy-MM-dd'T'HH:mm:ssZ
 '</td></tr><tr><td>filename</td><td>The name of the file on the SFTP 
Server</td></tr><tr><td>path</td><td>The fully qualified name of the directory 
on the SFTP Server from which the file was pulled</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 listing of files, the timestamp of the newest file is stored. 
This allows the Processor to list only files that have been added or modified 
after this date the next time that the Processor is run. State is stored across 
the cluster so that this Processor can be run on Primary Node only and if a new 
Primary Node is selected, the new node will not duplicate the data that was 
listed by the previous Primary Node.</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.<h3>See Also:</h3><p><a hr
 
ef="../org.apache.nifi.processors.standard.FetchSFTP/index.html">FetchSFTP</a>, 
<a 
href="../org.apache.nifi.processors.standard.GetSFTP/index.html">GetSFTP</a>, 
<a 
href="../org.apache.nifi.processors.standard.PutSFTP/index.html">PutSFTP</a></p></body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.ListenHTTP/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.ListenHTTP/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.ListenHTTP/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.ListenHTTP/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ListenHTTP</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;">ListenHTTP</h1><h2>Description: </h2><p>Starts an HTTP Server and 
listens on a given base path to transform incoming requests into FlowFiles. The 
default URI of the Service will be http://{hostname}:{port}/contentListener. 
Only HEAD and POST requests are supported. GET, PUT, and DELETE will result in 
an error and the HTTP response status code 405.</p><h3>Tags: </h3><p>ingest, 
http, https, rest, listen</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 d
 efault 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>Base Path</strong></td><td 
id="default-value">contentListener</td><td id="allowable-values"></td><td 
id="description">Base path for incoming connections<br/><strong>Supports 
Expression Language: true</strong></td></tr><tr><td id="name"><strong>Listening 
Port</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The Port to listen on for 
incoming connections<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Max Data to Receive per Second</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
maximum amount of data to receive per second; this allows the bandwidth to be 
throttled to a specified data rate;
  if not specified, the data rate is not throttled</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.6.0/org.apache.nifi.ssl.StandardRestrictedSSLContextService/index.html">StandardRestrictedSSLContextService</a></td><td
 id="description">The Controller Service to use in order to obtain an SSL 
Context</td></tr><tr><td id="name"><strong>Authorized DN 
Pattern</strong></td><td id="default-value">.*</td><td 
id="allowable-values"></td><td id="description">A Regular Expression to apply 
against the Distinguished Name of incoming connections. If the Pattern does not 
match the DN, the connection will be refused.</td></tr><tr><td 
id="name"><strong>Max Unconfirmed Flowfile Time</strong></td><td 
id="default-value">60 secs</td><td id="allowable-values"></td><td 
id="description">The maxi
 mum amount of time to wait for a FlowFile to be confirmed before it is removed 
from the cache</td></tr><tr><td id="name">HTTP Headers to receive as Attributes 
(Regex)</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">Specifies the Regular Expression that determines the names of 
HTTP Headers that should be passed along as FlowFile 
attributes</td></tr><tr><td id="name">Return Code</td><td 
id="default-value">200</td><td id="allowable-values"></td><td 
id="description">The HTTP return code returned after every HTTP 
call</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>Relationship
 for successfully received FlowFiles</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 componen
 t 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-standard-nar/1.6.0/org.apache.nifi.processors.standard.ListenRELP/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.ListenRELP/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.ListenRELP/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.ListenRELP/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ListenRELP</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;">ListenRELP</h1><h2>Description: </h2><p>Listens for RELP messages being 
sent to a given port over TCP. Each message will be acknowledged after 
successfully writing the message to a FlowFile. Each FlowFile will contain data 
portion of one or more RELP frames. In the case where the RELP frames contain 
syslog messages, the output of this processor can be sent to a ParseSyslog 
processor for further processing.</p><h3>Tags: </h3><p>listen, relp, tcp, 
logs</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 c
 onsidered 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">Local Network Interface</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The name of a local network 
interface to be used to restrict listening to a specific 
LAN.<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
id="name"><strong>Port</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The port to listen on for 
communication.</td></tr><tr><td id="name"><strong>Receive Buffer 
Size</strong></td><td id="default-value">65507 B</td><td 
id="allowable-values"></td><td id="description">The size of each buffer used to 
receive messages. Adjust this value appropriately based o
 n the expected size of the incoming messages.</td></tr><tr><td 
id="name"><strong>Max Size of Message Queue</strong></td><td 
id="default-value">10000</td><td id="allowable-values"></td><td 
id="description">The maximum size of the internal queue used to buffer messages 
being transferred from the underlying channel to the processor. Setting this 
value higher allows more messages to be buffered in memory during surges of 
incoming messages, but increases the total memory used by the 
processor.</td></tr><tr><td id="name"><strong>Max Size of Socket 
Buffer</strong></td><td id="default-value">1 MB</td><td 
id="allowable-values"></td><td id="description">The maximum size of the socket 
buffer that should be used. This is a suggestion to the Operating System to 
indicate how big the socket buffer should be. If this value is set too low, the 
buffer may fill up before the data can be read, and incoming data will be 
dropped.</td></tr><tr><td id="name"><strong>Character Set</strong></td><td 
id="defau
 lt-value">UTF-8</td><td id="allowable-values"></td><td 
id="description">Specifies the character set of the received 
data.</td></tr><tr><td id="name"><strong>Max Batch Size</strong></td><td 
id="default-value">1</td><td id="allowable-values"></td><td 
id="description">The maximum number of messages to add to a single FlowFile. If 
multiple messages are available, they will be concatenated along with the 
&lt;Message Delimiter&gt; up to this configured maximum number of 
messages</td></tr><tr><td id="name"><strong>Batching Message 
Delimiter</strong></td><td id="default-value">\n</td><td 
id="allowable-values"></td><td id="description">Specifies the delimiter to 
place between messages when multiple messages are bundled together (see &lt;Max 
Batch Size&gt; property).</td></tr><tr><td id="name"><strong>Max Number of TCP 
Connections</strong></td><td id="default-value">2</td><td 
id="allowable-values"></td><td id="description">The maximum number of 
concurrent TCP connections to accept.</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.6.0/org.apache.nifi.ssl.StandardRestrictedSSLContextService/index.html">StandardRestrictedSSLContextService</a></td><td
 id="description">The Controller Service to use in order to obtain an SSL 
Context. If this property is set, messages will be received over a secure 
connection.</td></tr><tr><td id="name">Client Auth</td><td 
id="default-value">REQUIRED</td><td 
id="allowable-values"><ul><li>WANT</li><li>REQUIRED</li><li>NONE</li></ul></td><td
 id="description">The client authentication policy to use for the SSL Context. 
Only used if an SSL Context Service is 
provided.</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>Messages
 received successfully will b
 e sent out 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>relp.command</td><td>The
 command of the RELP frames.</td></tr><tr><td>relp.sender</td><td>The sending 
host of the messages.</td></tr><tr><td>relp.port</td><td>The sending port the 
messages were received over.</td></tr><tr><td>relp.txnr</td><td>The transaction 
number of the message. Only included if &lt;Batch Size&gt; is 
1.</td></tr><tr><td>mime.type</td><td>The mime.type of the content which is 
text/plain</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 does not allow an incoming 
relationship.<h3>System Resource Considerations:</h3>None specified.<h3>See 
Also:</h3><p><a 
href="../org.apache.nifi.processors.standard.ParseSyslog/index.html">ParseSyslog</a></p></body>
 </html>
\ No newline at end of file


Reply via email to