Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-spring-nar/1.5.0/org.apache.nifi.spring.SpringContextProcessor/additionalDetails.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-spring-nar/1.5.0/org.apache.nifi.spring.SpringContextProcessor/additionalDetails.html?rev=1821033&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-spring-nar/1.5.0/org.apache.nifi.spring.SpringContextProcessor/additionalDetails.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-spring-nar/1.5.0/org.apache.nifi.spring.SpringContextProcessor/additionalDetails.html
 Fri Jan 12 21:00:14 2018
@@ -0,0 +1,94 @@
+<!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>SpringContextProcessor</title>
+        <link rel="stylesheet" href="../../../../../css/component-usage.css" 
type="text/css" />
+    </head>
+
+    <body>
+        <!-- Processor Documentation 
================================================== -->
+        <h2>Description:</h2>
+        <p>
+            <b>SpringContextProcessor</b> – allows integration of processes 
encapsulated in Spring Application Context to run as NiFi
+            processor by becoming a runtime host for an instance of Spring 
Application Context.
+        </p>
+        <p>
+            Communication between NiFi and process encapsulated within Spring 
Application Context is accomplished via Spring Messaging
+            (one of the core modules of Spring Framework) and supports 3 usage 
modes:
+            <ul>
+                <li><i>Headless</i> - no interaction with NiFi, meaning 
nothing is sent to it and nothing is received from it (i.e., some monitoring 
app).
+                In this case NiFi simply plays the role of the runtime 
host.</li>
+                <li><i>One way (NiFi -&gt; Spring or Spring -&gt; NiFi). </i> 
- This depends on existence of pre-defined message channel in Spring
+                Application Context. The name of the channel should be 
“fromNiFi” and the type 
<i>org.springframework.messaging.MessageChannel.</i></li>
+                <li><i>By-directional (NiFi -&gt; Spring -&gt; NiFi or Spring 
-&gt; NiFi -&gt; Spring)</i> - This depends on existence of two channels
+                in Spring Application Context. One channel receives messages 
from NiFi with name “fromNiFi” and type 
<i>org.springframework.messaging.MessageChannel</i>i>
+                and another is to receive messages from Spring with name 
“toNiFi” and type <i>org.springframework.messaging.PollableChannel.</i></li>
+            </ul>
+            The example below demonstrates template configuration for 
bi-directional Spring Application Context configuration:
+            <code>
+            <pre>
+    &lt;int:channel id=”fromNiFi”/&gt;
+
+    &lt;!—
+    your custom app configuration to receive messages from ‘fromNiFi’ 
channel and optionally send back to NiFi via ‘toNiFi’ channel.
+    It could contain any Spring-based application (i.e., Spring Integration, 
Apache Camel and/or custom code). All you need to do is inject
+    channels into your beans and send/receive messages from it.
+    --&gt;
+
+    &lt;int:channel id="toNiFi"&gt;
+        &lt;int:queue/&gt;
+    &lt;/int:channel&gt;
+            </pre>
+            </code>
+        </p>
+        <p>
+        The component is based on assumption that user has an existing Spring 
Application encapsulated in Spring Context that exposes optional in/out
+        MessagingChannels to allow data to flow to/from ApplicationContext and 
into/out-of. NiFi.
+        Such application is realized by having a directory on the file system, 
which contains contains all required resources for such application to run.
+        Such resources usually are JAR files to satisfy application's 
class-path as well as JAR representing the application and its configuration.
+        Below is the example of what such directory may contain. In this case 
the 'SI_DEMO-0.0.1-SNAPSHOT.jar' represents the actual application and the rest
+        of the JARs represent class-path dependency required by an application.
+        <pre>
+        deps
+         ├── SI_DEMO-0.0.1-SNAPSHOT.jar
+         ├── aopalliance-1.0.jar
+         ├── commons-logging-1.2.jar
+         ├── spring-aop-4.2.4.RELEASE.jar
+         ├── spring-beans-4.2.4.RELEASE.jar
+         ├── spring-context-4.2.4.RELEASE.jar
+         ├── spring-core-4.2.4.RELEASE.jar
+         ├── spring-expression-4.2.4.RELEASE.jar
+         ├── spring-integration-core-4.2.5.RELEASE.jar
+         ├── spring-messaging-4.2.4.RELEASE.jar
+        </pre>
+        </p>
+        <p>
+        You introduce the processor the usual way and then configure its 
properties:
+        <ul>
+        <li><i><b>Application Context config path</b></i> [REQUIRED] - a path 
to the Application Context configuration.
+        The path is relative to the class-path of the application defined by 
the <i>Application Context class path</i> property </li>
+        <li><i><b>Application Context class path</b></i> [REQUIRED] - a path 
to a directory on the file system where application dependencies are. </li>
+        <li><i>Send Timeout</i> [OPTIONAL] - the wait time for sending 
messages to Spring Application Context. Only required if NiFi plans to send 
data to Spring.
+        Defaults to 0 (don't wait). FlowFiles that were successfully sent to 
Spring will be removed from session while FlowFiles that could not be sent to
+        Spring will be routed to <i>failure</i> relationship.</li>
+        <li><i>Receive Timeout</i> - [OPTIONAL] - the wait time for receiving 
messages from Spring Application Context. Only required if NiFi plans to 
receive data from Spring.
+        Defaults to 0 (don't wait). FlowFile is created if and only if a 
message is successfully received from Spring. It is then transferred to 
<i>success</i> relationship.</li>
+        </ul>
+        </p>
+    </body>
+</html>

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-spring-nar/1.5.0/org.apache.nifi.spring.SpringContextProcessor/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-spring-nar/1.5.0/org.apache.nifi.spring.SpringContextProcessor/index.html?rev=1821033&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-spring-nar/1.5.0/org.apache.nifi.spring.SpringContextProcessor/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-spring-nar/1.5.0/org.apache.nifi.spring.SpringContextProcessor/index.html
 Fri Jan 12 21:00:14 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>SpringContextProcessor</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;">SpringContextProcessor</h1><h2>Description: </h2><p>A Processor that 
supports sending and receiving data from application defined in Spring 
Application Context via predefined in/out MessageChannels.</p><p><a 
href="additionalDetails.html">Additional Details...</a></p><h3>Tags: 
</h3><p>Spring, Message, Get, Put, Integration</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>Application Context config path</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
path to the Spring Application Context configuration file relative to the 
classpath</td></tr><tr><td id="name"><strong>Application Context class 
path</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Path to the directory with 
resources (i.e., JARs, configuration files etc.) required to be on the 
classpath of the ApplicationContext.</td></tr><tr><td id="name">Send 
Timeout</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">Timeout for sending data to Spring Application Context. 
Defaults to 0.</td></tr><tr><td id="name">Receive Timeout</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Timeout for receiving date from Spring context. Defaults to 
0.</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 successfully received from Spring Application Context are 
routed to this relationship</td></tr><tr><td>failure</td><td>All FlowFiles that 
cannot be sent to Spring Application Context are routed to this 
relationship</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.</body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-ssl-context-service-nar/1.5.0/org.apache.nifi.ssl.StandardRestrictedSSLContextService/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-ssl-context-service-nar/1.5.0/org.apache.nifi.ssl.StandardRestrictedSSLContextService/index.html?rev=1821033&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-ssl-context-service-nar/1.5.0/org.apache.nifi.ssl.StandardRestrictedSSLContextService/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-ssl-context-service-nar/1.5.0/org.apache.nifi.ssl.StandardRestrictedSSLContextService/index.html
 Fri Jan 12 21:00:14 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>StandardRestrictedSSLContextService</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;">StandardRestrictedSSLContextService</h1><h2>Description: 
</h2><p>Restricted implementation of the SSLContextService. Provides the 
ability to configure keystore and/or truststore properties once and reuse that 
configuration throughout the application, but only allows a restricted set of 
TLS/SSL protocols to be chosen (no SSL protocols are supported). The set of 
protocols selectable will evolve over time as new protocols emerge and older 
protocols are deprecated. This service is recommended over 
StandardSSLContextService if a component doesn't expect to communicate with 
legacy 
 systems since it is unlikely that legacy systems will support these 
protocols.</p><h3>Tags: </h3><p>tls, ssl, secure, certificate, keystore, 
truststore, jks, p12, pkcs12, pkcs</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 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">Keystore Filename</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
fully-qualified filename of the Keystore</td></tr><tr><td id="name">Keystore 
Password</td><td id=
 "default-value"></td><td id="allowable-values"></td><td id="description">The 
password for the Keystore<br/><strong>Sensitive Property: 
true</strong></td></tr><tr><td id="name">Key Password</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
password for the key. If this is not specified, but the Keystore Filename, 
Password, and Type are specified, then the Keystore Password will be assumed to 
be the same as the Key Password.<br/><strong>Sensitive Property: 
true</strong></td></tr><tr><td id="name">Keystore Type</td><td 
id="default-value"></td><td 
id="allowable-values"><ul><li>JKS</li><li>PKCS12</li></ul></td><td 
id="description">The Type of the Keystore</td></tr><tr><td id="name">Truststore 
Filename</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">The fully-qualified filename of the 
Truststore</td></tr><tr><td id="name">Truststore Password</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="desc
 ription">The password for the Truststore<br/><strong>Sensitive Property: 
true</strong></td></tr><tr><td id="name">Truststore Type</td><td 
id="default-value"></td><td 
id="allowable-values"><ul><li>JKS</li><li>PKCS12</li></ul></td><td 
id="description">The Type of the Truststore. Either JKS or 
PKCS12</td></tr><tr><td id="name">TLS Protocol</td><td 
id="default-value">TLS</td><td 
id="allowable-values"><ul><li>TLS</li><li>TLSv1.2</li></ul></td><td 
id="description">The algorithm to use for this SSL context. By default, this 
will choose the highest supported TLS protocol 
version.</td></tr></table><h3>State management: </h3>This component does not 
store state.<h3>Restricted: </h3>This component is not restricted.</body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-ssl-context-service-nar/1.5.0/org.apache.nifi.ssl.StandardSSLContextService/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-ssl-context-service-nar/1.5.0/org.apache.nifi.ssl.StandardSSLContextService/index.html?rev=1821033&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-ssl-context-service-nar/1.5.0/org.apache.nifi.ssl.StandardSSLContextService/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-ssl-context-service-nar/1.5.0/org.apache.nifi.ssl.StandardSSLContextService/index.html
 Fri Jan 12 21:00:14 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>StandardSSLContextService</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;">StandardSSLContextService</h1><h2>Description: </h2><p>Standard 
implementation of the SSLContextService. Provides the ability to configure 
keystore and/or truststore properties once and reuse that configuration 
throughout the application. This service can be used to communicate with both 
legacy and modern systems. If you only need to communicate with non-legacy 
systems, then the StandardRestrictedSSLContextService is recommended as it only 
allows a specific set of SSL protocols to be chosen.</p><h3>Tags: </h3><p>ssl, 
secure, certificate, keystore, truststore, jks, p12, pkcs12, pkcs, tl
 s</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 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">Keystore Filename</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
fully-qualified filename of the Keystore</td></tr><tr><td id="name">Keystore 
Password</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">The password for the Keystore<br/><strong>Sensitive Property: 
true</strong></td></tr><tr><td id="name
 ">Key Password</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The password for the key. If 
this is not specified, but the Keystore Filename, Password, and Type are 
specified, then the Keystore Password will be assumed to be the same as the Key 
Password.<br/><strong>Sensitive Property: true</strong></td></tr><tr><td 
id="name">Keystore Type</td><td id="default-value"></td><td 
id="allowable-values"><ul><li>JKS</li><li>PKCS12</li></ul></td><td 
id="description">The Type of the Keystore</td></tr><tr><td id="name">Truststore 
Filename</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">The fully-qualified filename of the 
Truststore</td></tr><tr><td id="name">Truststore Password</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
password for the Truststore<br/><strong>Sensitive Property: 
true</strong></td></tr><tr><td id="name">Truststore Type</td><td 
id="default-value"></td><td id="allo
 wable-values"><ul><li>JKS</li><li>PKCS12</li></ul></td><td 
id="description">The Type of the Truststore. Either JKS or 
PKCS12</td></tr><tr><td id="name">TLS Protocol</td><td 
id="default-value">TLS</td><td 
id="allowable-values"><ul><li>SSL</li><li>SSLv2Hello</li><li>SSLv3</li><li>TLS</li><li>TLSv1</li><li>TLSv1.1</li><li>TLSv1.2</li></ul></td><td
 id="description">The algorithm to use for this TLS/SSL 
context</td></tr></table><h3>State management: </h3>This component does not 
store state.<h3>Restricted: </h3>This component is not restricted.</body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.controller.ControllerStatusReportingTask/additionalDetails.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.controller.ControllerStatusReportingTask/additionalDetails.html?rev=1821033&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.controller.ControllerStatusReportingTask/additionalDetails.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.controller.ControllerStatusReportingTask/additionalDetails.html
 Fri Jan 12 21:00:14 2018
@@ -0,0 +1,70 @@
+<!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>ControllerStatusReportingTask</title>
+        <link rel="stylesheet" href="../../../../../css/component-usage.css" 
type="text/css" />
+    </head>
+
+    <body>
+        <h2>Description:</h2>
+
+        <p>
+            Reporting Task that creates a log message for each Processor and 
each Connection in the flow.
+
+            For Processors, the following information is included (sorted by 
descending Processing Timing):
+        </p>
+        <ul>
+            <li>Processor Name</li>
+            <li>Processor ID</li>
+            <li>Processor Type</li>
+            <li>Run Status</li>
+            <li>Flow Files In (5 mins)</li>
+            <li>FlowFiles Out (5 mins)</li>
+            <li>Bytes Read from Disk (5 mins)</li>
+            <li>Bytes Written to Disk (5 mins)</li>
+            <li>Number of Tasks Completed (5 mins)</li>
+            <li>Processing Time (5 mins)</li>
+        </ul>
+
+        <p>
+            For Connections, the following information is included (sorted by 
descending size of queued FlowFiles):
+        </p>
+        <ul>
+            <li>Connection Name</li>
+            <li>Connection ID</li>
+            <li>Source Component Name</li>
+            <li>Destination Component Name</li>
+            <li>Flow Files In (5 mins)</li>
+            <li>FlowFiles Out (5 mins)</li>
+            <li>FlowFiles Queued</li>
+        </ul>
+
+        <p>
+            If may be convenient to redirect the logging output of this 
ReportingTask to a separate log file than the typical application log.
+            This can be accomplished by modified the logback.xml file in the 
NiFi conf/ directory such that a logger with the name
+            
<code>org.apache.nifi.controller.ControllerStatusReportingTask</code> is 
configured to write to a separate log.
+        </p>
+
+        <p>
+            Additionally, it may be convenient to disable logging for 
Processors or for Connections or to split them into separate log files. This
+            can be accomplished by using the loggers named 
+            
<code>org.apache.nifi.controller.ControllerStatusReportingTask.Processors</code>
 and 
+            
<code>org.apache.nifi.controller.ControllerStatusReportingTask.Connections</code>,
 respectively.
+        </p>
+    </body>
+</html>

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.controller.ControllerStatusReportingTask/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.controller.ControllerStatusReportingTask/index.html?rev=1821033&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.controller.ControllerStatusReportingTask/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.controller.ControllerStatusReportingTask/index.html
 Fri Jan 12 21:00:14 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ControllerStatusReportingTask</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;">ControllerStatusReportingTask</h1><h2>Description: </h2><p>Logs the 
5-minute stats that are shown in the NiFi Summary Page for Processors and 
Connections, as well optionally logging the deltas between the previous 
iteration and the current iteration. Processors' stats are logged using the 
org.apache.nifi.controller.ControllerStatusReportingTask.Processors logger, 
while Connections' stats are logged using the 
org.apache.nifi.controller.ControllerStatusReportingTask.Connections logger. 
These can be configured in the NiFi logging configuration to log to different 
files, if desired.</p
 ><p><a href="additionalDetails.html">Additional Details...</a></p><h3>Tags: 
 ></h3><p>stats, log</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>Show Deltas</strong></td><td 
 >id="default-value">true</td><td 
 >id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
 >id="description">Specifies whether or not to show the difference in values 
 >between the current status and the previous status</td></tr></table><h3>State 
 >management: </h3>This component does not store state.<h3>Restricted: 
 ></h3>This component is not restricted.</body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.controller.MonitorDiskUsage/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.controller.MonitorDiskUsage/index.html?rev=1821033&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.controller.MonitorDiskUsage/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.controller.MonitorDiskUsage/index.html
 Fri Jan 12 21:00:14 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>MonitorDiskUsage</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;">MonitorDiskUsage</h1><h2>Description: </h2><p>Checks the amount of 
storage space available for the specified directory and warns (via a log 
message and a System-Level Bulletin) if the partition on which it lives exceeds 
some configurable threshold of storage space</p><h3>Tags: </h3><p>disk, 
storage, warning, monitoring, repo</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 Va
 lue</th><th>Allowable Values</th><th>Description</th></tr><tr><td 
id="name"><strong>Threshold</strong></td><td id="default-value">80%</td><td 
id="allowable-values"></td><td id="description">The threshold at which a 
bulletin will be generated to indicate that the disk usage of the partition on 
which the directory found is of concern</td></tr><tr><td 
id="name"><strong>Directory Location</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
directory path of the partition to be monitored.</td></tr><tr><td 
id="name">Directory Display Name</td><td id="default-value">Un-Named</td><td 
id="allowable-values"></td><td id="description">The name to display for the 
directory in alerts.</td></tr></table><h3>State management: </h3>This component 
does not store state.<h3>Restricted: </h3>This component is not 
restricted.</body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.controller.MonitorMemory/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.controller.MonitorMemory/index.html?rev=1821033&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.controller.MonitorMemory/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.controller.MonitorMemory/index.html
 Fri Jan 12 21:00:14 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>MonitorMemory</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;">MonitorMemory</h1><h2>Description: </h2><p>Checks the amount of Java 
Heap available in the JVM for a particular JVM Memory Pool. If the amount of 
space used exceeds some configurable threshold, will warn (via a log message 
and System-Level Bulletin) that the memory pool is exceeding this 
threshold.</p><h3>Tags: </h3><p>monitor, memory, heap, jvm, gc, garbage 
collection, warning</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><ta
 ble id="properties"><tr><th>Name</th><th>Default Value</th><th>Allowable 
Values</th><th>Description</th></tr><tr><td id="name"><strong>Memory 
Pool</strong></td><td id="default-value"></td><td 
id="allowable-values"><ul><li>Code Cache</li><li>Metaspace</li><li>Compressed 
Class Space</li><li>G1 Eden Space</li><li>G1 Survivor Space</li><li>G1 Old 
Gen</li></ul></td><td id="description">The name of the JVM Memory Pool to 
monitor</td></tr><tr><td id="name"><strong>Usage Threshold</strong></td><td 
id="default-value">65%</td><td id="allowable-values"></td><td 
id="description">Indicates the threshold at which warnings should be 
generated</td></tr><tr><td id="name">Reporting Interval</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Indicates how often this reporting task should report 
bulletins while the memory utilization exceeds the configured 
threshold</td></tr></table><h3>State management: </h3>This component does not 
store state.<h3>Restricted: </h3>This
  component is not restricted.</body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.AttributesToJSON/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.AttributesToJSON/index.html?rev=1821033&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.AttributesToJSON/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.AttributesToJSON/index.html
 Fri Jan 12 21:00:14 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>AttributesToJSON</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;">AttributesToJSON</h1><h2>Description: </h2><p>Generates a JSON 
representation of the input FlowFile Attributes. The resulting JSON can be 
written to either a new Attribute 'JSONAttributes' or written to the FlowFile 
as content.</p><h3>Tags: </h3><p>json, attributes, flowfile</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 
Expres
 sion 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">Attributes List</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Comma separated list of 
attributes to be included in the resulting JSON. If this value is left empty 
then all existing Attributes will be included. This list of attributes is case 
sensitive. If an attribute specified in the list is not found it will be be 
emitted to the resulting JSON with an empty string or NULL 
value.</td></tr><tr><td id="name">Attributes Regular Expression</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Regular expression that will be evaluated against the flow 
file attributes to select the matching attributes. This property can be used in 
combination with the attributes list property.<br/><strong>Supports Expression 
Language: true</strong></td></tr><tr><td id="name"><strong>Desti
 nation</strong></td><td id="default-value">flowfile-attribute</td><td 
id="allowable-values"><ul><li>flowfile-attribute</li><li>flowfile-content</li></ul></td><td
 id="description">Control if JSON value is written as a new flowfile attribute 
'JSONAttributes' or written in the flowfile content. Writing to flowfile 
content will overwrite any existing flowfile content.</td></tr><tr><td 
id="name"><strong>Include Core Attributes</strong></td><td 
id="default-value">true</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Determines if the FlowFile 
org.apache.nifi.flowfile.attributes.CoreAttributes which are contained in every 
FlowFile should be included in the final JSON value generated.</td></tr><tr><td 
id="name"><strong>Null Value</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 a non existing or empty attribute will be NULL in the 
resulting JSON. If false a
 n empty string will be placed in the JSON</td></tr></table><h3>Relationships: 
</h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>Successfully
 converted attributes to JSON</td></tr><tr><td>failure</td><td>Failed to 
convert attributes to JSON</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>JSONAttributes</td><td>JSON
 representation of Attributes</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.</body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.Base64EncodeContent/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.Base64EncodeContent/index.html?rev=1821033&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.Base64EncodeContent/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.Base64EncodeContent/index.html
 Fri Jan 12 21:00:14 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>Base64EncodeContent</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;">Base64EncodeContent</h1><h2>Description: </h2><p>Encodes or decodes 
content to and from base64</p><h3>Tags: </h3><p>encode, 
base64</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>Mode</strong></td><td id="default-value">Encode</td><td 
id="allowable-values"><ul><li>Encode</li><li>Decode</
 li></ul></td><td id="description">Specifies whether the content should be 
encoded or decoded</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 encoded or decoded will be routed to 
success</td></tr><tr><td>failure</td><td>Any FlowFile that cannot be encoded or 
decoded will be routed to failure</td></tr></table><h3>Reads Attributes: 
</h3>None specified.<h3>Writes Attributes: </h3>None specified.<h3>State 
management: </h3>This component does not store state.<h3>Restricted: </h3>This 
component is not restricted.<h3>Input requirement: </h3>This component requires 
an incoming relationship.</body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.CompressContent/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.CompressContent/index.html?rev=1821033&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.CompressContent/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.CompressContent/index.html
 Fri Jan 12 21:00:14 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>CompressContent</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;">CompressContent</h1><h2>Description: </h2><p>Compresses or decompresses 
the contents of FlowFiles using a user-specified compression algorithm and 
updates the mime.type attribute as appropriate</p><h3>Tags: </h3><p>content, 
compress, decompress, gzip, bzip2, lzma, xz-lzma2, snappy, snappy 
framed</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</t
 h><th>Description</th></tr><tr><td id="name"><strong>Mode</strong></td><td 
id="default-value">compress</td><td 
id="allowable-values"><ul><li>compress</li><li>decompress</li></ul></td><td 
id="description">Indicates whether the processor should compress content or 
decompress content. Must be either 'compress' or 'decompress'</td></tr><tr><td 
id="name"><strong>Compression Format</strong></td><td id="default-value">use 
mime.type attribute</td><td id="allowable-values"><ul><li>use mime.type 
attribute</li><li>gzip</li><li>bzip2</li><li>xz-lzma2</li><li>lzma</li><li>snappy</li><li>snappy
 framed</li></ul></td><td id="description">The compression format to use. Valid 
values are: GZIP, BZIP2, XZ-LZMA2, LZMA, Snappy, and Snappy 
Framed</td></tr><tr><td id="name"><strong>Compression Level</strong></td><td 
id="default-value">1</td><td 
id="allowable-values"><ul><li>0</li><li>1</li><li>2</li><li>3</li><li>4</li><li>5</li><li>6</li><li>7</li><li>8</li><li>9</li></ul></td><td
 id="description">The com
 pression level to use; this is valid only when using GZIP compression. A lower 
value results in faster processing but less compression; a value of 0 indicates 
no compression but simply archiving</td></tr><tr><td id="name"><strong>Update 
Filename</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 remove the filename extension when decompressing 
data (only if the extension indicates the appropriate compression format) and 
add the appropriate extension when compressing 
data</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>FlowFiles
 will be transferred to the success relationship after successfully being 
compressed or decompressed</td></tr><tr><td>failure</td><td>FlowFiles will be 
transferred to the failure relationship if they fail to 
compress/decompress</td></tr></table><h3>Reads Attributes: </h3><table id=
 
"reads-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>mime.type</td><td>If
 the Compression Format is set to use mime.type attribute, this attribute is 
used to determine the compression type. Otherwise, this attribute is 
ignored.</td></tr></table><h3>Writes Attributes: </h3><table 
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>mime.type</td><td>If
 the Mode property is set to compress, the appropriate MIME Type is set. If the 
Mode property is set to decompress and the file is successfully decompressed, 
this attribute is removed, as the MIME Type is no longer 
known.</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.</body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.ControlRate/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.ControlRate/index.html?rev=1821033&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.ControlRate/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.ControlRate/index.html
 Fri Jan 12 21:00:14 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ControlRate</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;">ControlRate</h1><h2>Description: </h2><p>Controls the rate at which data 
is transferred to follow-on processors. If you configure a very small Time 
Duration, then the accuracy of the throttle gets worse. You can improve this 
accuracy by decreasing the Yield Duration, at the expense of more Tasks given 
to the processor.</p><h3>Tags: </h3><p>rate control, throttle, rate, 
throughput</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><ta
 ble id="properties"><tr><th>Name</th><th>Default Value</th><th>Allowable 
Values</th><th>Description</th></tr><tr><td id="name"><strong>Rate Control 
Criteria</strong></td><td id="default-value">data rate</td><td 
id="allowable-values"><ul><li>data rate <img 
src="../../../../../html/images/iconInfo.png" alt="Rate is controlled by 
counting bytes transferred per time duration." title="Rate is controlled by 
counting bytes transferred per time duration."></img></li><li>flowfile count 
<img src="../../../../../html/images/iconInfo.png" alt="Rate is controlled by 
counting flowfiles transferred per time duration" title="Rate is controlled by 
counting flowfiles transferred per time duration"></img></li><li>attribute 
value <img src="../../../../../html/images/iconInfo.png" alt="Rate is 
controlled by accumulating the value of a specified attribute that is 
transferred per time duration" title="Rate is controlled by accumulating the 
value of a specified attribute that is transferred per time durati
 on"></img></li></ul></td><td id="description">Indicates the criteria that is 
used to control the throughput rate. Changing this value resets the rate 
counters.</td></tr><tr><td id="name"><strong>Maximum Rate</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
maximum rate at which data should pass through this processor. The format of 
this property is expected to be a positive integer, or a Data Size (such as '1 
MB') if Rate Control Criteria is set to 'data rate'.</td></tr><tr><td 
id="name">Rate Controlled Attribute</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The name of an attribute whose 
values build toward the rate limit if Rate Control Criteria is set to 
'attribute value'. The value of the attribute referenced by this property must 
be a positive long, or the FlowFile will be routed to failure. This value is 
ignored if Rate Control Criteria is not set to 'attribute value'. Changing this 
value res
 ets the rate counters.</td></tr><tr><td id="name"><strong>Time 
Duration</strong></td><td id="default-value">1 min</td><td 
id="allowable-values"></td><td id="description">The amount of time to which the 
Maximum Rate pertains. Changing this value resets the rate 
counters.</td></tr><tr><td id="name">Grouping Attribute</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">By 
default, a single "throttle" is used for all FlowFiles. If this value is 
specified, a separate throttle is used for each value specified by the 
attribute with this name. Changing this value resets the rate 
counters.</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>FlowFiles
 are transferred to this relationship under normal 
conditions</td></tr><tr><td>failure</td><td>FlowFiles will be routed to this 
relationship if they are missing a necessary Rate Controlled Attribute or the 
attribute is not in the expec
 ted format</td></tr></table><h3>Reads Attributes: </h3>None 
specified.<h3>Writes Attributes: </h3>None specified.<h3>State management: 
</h3>This component does not store state.<h3>Restricted: </h3>This component is 
not restricted.<h3>Input requirement: </h3>This component requires an incoming 
relationship.</body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.ConvertCharacterSet/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.ConvertCharacterSet/index.html?rev=1821033&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.ConvertCharacterSet/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.ConvertCharacterSet/index.html
 Fri Jan 12 21:00:14 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ConvertCharacterSet</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;">ConvertCharacterSet</h1><h2>Description: </h2><p>Converts a FlowFile's 
content from one character set to another</p><h3>Tags: </h3><p>text, convert, 
characterset, character set</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>Allowabl
 e Values</th><th>Description</th></tr><tr><td id="name"><strong>Input 
Character Set</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The name of the CharacterSet to 
expect for Input<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Output Character 
Set</strong></td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">The name of the CharacterSet to convert 
to<br/><strong>Supports Expression Language: 
true</strong></td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td></td></tr></table><h3>Reads
 Attributes: </h3>None specified.<h3>Writes Attributes: </h3>None 
specified.<h3>State management: </h3>This component does not store 
state.<h3>Restricted: </h3>This component is not restricted.<h3>Input 
requirement: </h3>This component requires an incoming 
relationship.</body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.ConvertJSONToSQL/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.ConvertJSONToSQL/index.html?rev=1821033&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.ConvertJSONToSQL/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.ConvertJSONToSQL/index.html
 Fri Jan 12 21:00:14 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ConvertJSONToSQL</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;">ConvertJSONToSQL</h1><h2>Description: </h2><p>Converts a JSON-formatted 
FlowFile into an UPDATE, INSERT, or DELETE SQL statement. The incoming FlowFile 
is expected to be "flat" JSON message, meaning that it consists of a single 
JSON element and each field maps to a simple type. If a field maps to a JSON 
object, that JSON object will be interpreted as Text. If the input is an array 
of JSON elements, each element in the array is output as a separate FlowFile to 
the 'sql' relationship. Upon successful conversion, the original FlowFile is 
routed to the 'original' relationship and the SQL is routed 
 to the 'sql' relationship.</p><h3>Tags: </h3><p>json, sql, database, rdbms, 
insert, update, delete, relational, flat</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>JDBC Connection Pool</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-hive-nar/1.5.0/org.apache.nifi.dbcp.hive.HiveConnectionPool/index.html">HiveConnectionPool</a><br/><a
 
href="../../../nifi-dbcp-service-nar/1.5.0/org.apache.nifi.dbcp.DBCPConnectionPool/ind
 ex.html">DBCPConnectionPool</a></td><td id="description">Specifies the JDBC 
Connection Pool to use in order to convert the JSON message to a SQL statement. 
The Connection Pool is necessary in order to determine the appropriate database 
column types.</td></tr><tr><td id="name"><strong>Statement 
Type</strong></td><td id="default-value"></td><td 
id="allowable-values"><ul><li>UPDATE</li><li>INSERT</li><li>DELETE</li></ul></td><td
 id="description">Specifies the type of SQL Statement to 
generate</td></tr><tr><td id="name"><strong>Table Name</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
name of the table that the statement should update<br/><strong>Supports 
Expression Language: true</strong></td></tr><tr><td id="name">Catalog 
Name</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">The name of the catalog that the statement should update. This 
may not apply for the database that you are updating. In this cas
 e, leave the field empty<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Schema Name</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
name of the schema that the table belongs to. This may not apply for the 
database that you are updating. In this case, leave the field 
empty<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
id="name">Translate Field Names</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, the Processor will attempt to translate JSON field 
names into the appropriate column names for the table specified. If false, the 
JSON field names must match the column names exactly, or the column will not be 
updated</td></tr><tr><td id="name">Unmatched Field Behavior</td><td 
id="default-value">Ignore Unmatched Fields</td><td 
id="allowable-values"><ul><li>Ignore Unmatched Fields <img 
src="../../../../../ht
 ml/images/iconInfo.png" alt="Any field in the JSON document that cannot be 
mapped to a column in the database is ignored" title="Any field in the JSON 
document that cannot be mapped to a column in the database is 
ignored"></img></li><li>Fail <img src="../../../../../html/images/iconInfo.png" 
alt="If the JSON document has any field that cannot be mapped to a column in 
the database, the FlowFile will be routed to the failure relationship" 
title="If the JSON document has any field that cannot be mapped to a column in 
the database, the FlowFile will be routed to the failure 
relationship"></img></li></ul></td><td id="description">If an incoming JSON 
element has a field that does not map to any of the database table's columns, 
this property specifies how to handle the situation</td></tr><tr><td 
id="name">Unmatched Column Behavior</td><td id="default-value">Fail on 
Unmatched Columns</td><td id="allowable-values"><ul><li>Ignore Unmatched 
Columns <img src="../../../../../html/images/iconInfo
 .png" alt="Any column in the database that does not have a field in the JSON 
document will be assumed to not be required.  No notification will be logged" 
title="Any column in the database that does not have a field in the JSON 
document will be assumed to not be required.  No notification will be 
logged"></img></li><li>Warn on Unmatched Columns <img 
src="../../../../../html/images/iconInfo.png" alt="Any column in the database 
that does not have a field in the JSON document will be assumed to not be 
required.  A warning will be logged" title="Any column in the database that 
does not have a field in the JSON document will be assumed to not be required.  
A warning will be logged"></img></li><li>Fail on Unmatched Columns <img 
src="../../../../../html/images/iconInfo.png" alt="A flow will fail if any 
column in the database that does not have a field in the JSON document.  An 
error will be logged" title="A flow will fail if any column in the database 
that does not have a field in the JSON
  document.  An error will be logged"></img></li></ul></td><td 
id="description">If an incoming JSON element does not have a field mapping for 
all of the database table's columns, this property specifies how to handle the 
situation</td></tr><tr><td id="name">Update Keys</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">A 
comma-separated list of column names that uniquely identifies a row in the 
database for UPDATE statements. If the Statement Type is UPDATE and this 
property is not set, the table's Primary Keys are used. In this case, if no 
Primary Key exists, the conversion to SQL will fail if Unmatched Column 
Behaviour is set to FAIL. This property is ignored if the Statement Type is 
INSERT<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
id="name">Quote Column Identifiers</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 option will caus
 e all column names to be quoted, allowing you to use reserved words as column 
names in your tables.</td></tr><tr><td id="name">Quote Table 
Identifiers</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 option will cause the table name to be quoted to 
support the use of special characters in the table name</td></tr><tr><td 
id="name"><strong>SQL Parameter Attribute Prefix</strong></td><td 
id="default-value">sql</td><td id="allowable-values"></td><td 
id="description">The string to be prepended to the outgoing flow file 
attributes, such as &lt;sql&gt;.args.1.value, where &lt;sql&gt; is replaced 
with the specified value<br/><strong>Supports Expression Language: 
true</strong></td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>sql</td><td>A
 FlowFile is routed to this relationship when its contents have successfully 
been converted into a S
 QL statement</td></tr><tr><td>failure</td><td>A FlowFile is routed to this 
relationship if it cannot be converted into a SQL statement. Common causes 
include invalid JSON content or the JSON content missing a required field (if 
using an INSERT statement type).</td></tr><tr><td>original</td><td>When a 
FlowFile is converted to SQL, the original JSON FlowFile is 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>Sets
 mime.type of FlowFile that is routed to 'sql' to 
'text/plain'.</td></tr><tr><td>&lt;sql&gt;.table</td><td>Sets the 
&lt;sql&gt;.table attribute of FlowFile that is routed to 'sql' to the name of 
the table that is updated by the SQL statement. The prefix for this attribute 
('sql', e.g.) is determined by the SQL Parameter Attribute Prefix 
property.</td></tr><tr><td>&lt;sql&gt;.catalog</td><td>If the Catalog name is s
 et for this database, specifies the name of the catalog that the SQL statement 
will update. If no catalog is used, this attribute will not be added. The 
prefix for this attribute ('sql', e.g.) is determined by the SQL Parameter 
Attribute Prefix property.</td></tr><tr><td>fragment.identifier</td><td>All 
FlowFiles routed to the 'sql' relationship for the same incoming FlowFile 
(multiple will be output for the same incoming FlowFile if the incoming 
FlowFile is a JSON Array) will have the same value for the fragment.identifier 
attribute. This can then be used to correlate the 
results.</td></tr><tr><td>fragment.count</td><td>The number of SQL FlowFiles 
that were produced for same incoming FlowFile. This can be used in conjunction 
with the fragment.identifier attribute in order to know how many FlowFiles 
belonged to the same incoming 
FlowFile.</td></tr><tr><td>fragment.index</td><td>The position of this FlowFile 
in the list of outgoing FlowFiles that were all derived from the same incomin
 g FlowFile. This can be used in conjunction with the fragment.identifier and 
fragment.count attributes to know which FlowFiles originated from the same 
incoming FlowFile and in what order the SQL FlowFiles were 
produced</td></tr><tr><td>&lt;sql&gt;.args.N.type</td><td>The output SQL 
statements are parametrized in order to avoid SQL Injection Attacks. The types 
of the Parameters to use are stored in attributes named 
&lt;sql&gt;.args.1.type, &lt;sql&gt;.args.2.type, &lt;sql&gt;.args.3.type, and 
so on. The type is a number representing a JDBC Type constant. Generally, this 
is useful only for software to read and interpret but is added so that a 
processor such as PutSQL can understand how to interpret the values. The prefix 
for this attribute ('sql', e.g.) is determined by the SQL Parameter Attribute 
Prefix property.</td></tr><tr><td>&lt;sql&gt;.args.N.value</td><td>The output 
SQL statements are parametrized in order to avoid SQL Injection Attacks. The 
values of the Parameters to use ar
 e stored in the attributes named sql.args.1.value, sql.args.2.value, 
sql.args.3.value, and so on. Each of these attributes has a corresponding 
&lt;sql&gt;.args.N.type attribute that indicates how the value should be 
interpreted when inserting it into the database.The prefix for this attribute 
('sql', e.g.) is determined by the SQL Parameter Attribute Prefix 
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>See 
Also:</h3><p><a 
href="../org.apache.nifi.processors.standard.PutSQL/index.html">PutSQL</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.5.0/org.apache.nifi.processors.standard.ConvertRecord/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.ConvertRecord/index.html?rev=1821033&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.ConvertRecord/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.ConvertRecord/index.html
 Fri Jan 12 21:00:14 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ConvertRecord</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;">ConvertRecord</h1><h2>Description: </h2><p>Converts records from one 
data format to another using configured Record Reader and Record Write 
Controller Services. The Reader and Writer must be configured with "matching" 
schemas. By this, we mean the schemas must have the same field names. The types 
of the fields do not have to be the same if a field value can be coerced from 
one type to another. For instance, if the input schema has a field named 
"balance" of type double, the output schema can have a field named "balance" 
with a type of string, double, or float. If any field is present in the input 
 that is not present in the output, the field will be left out of the output. 
If any field is specified in the output schema but is not present in the input 
data/schema, then the field will not be present in the output or will have a 
null value, depending on the writer.</p><h3>Tags: </h3><p>convert, record, 
generic, schema, json, csv, avro, log, logs, freeform, text</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.5.0/org.apache.nifi.csv.CSV
 Reader/index.html">CSVReader</a><br/><a 
href="../../../nifi-scripting-nar/1.5.0/org.apache.nifi.record.script.ScriptedReader/index.html">ScriptedReader</a><br/><a
 
href="../../../nifi-record-serialization-services-nar/1.5.0/org.apache.nifi.grok.GrokReader/index.html">GrokReader</a><br/><a
 
href="../../../nifi-record-serialization-services-nar/1.5.0/org.apache.nifi.json.JsonTreeReader/index.html">JsonTreeReader</a><br/><a
 
href="../../../nifi-record-serialization-services-nar/1.5.0/org.apache.nifi.avro.AvroReader/index.html">AvroReader</a><br/><a
 
href="../../../nifi-record-serialization-services-nar/1.5.0/org.apache.nifi.json.JsonPathReader/index.html">JsonPathReader</a></td><td
 id="description">Specifies the Controller Service to use for reading incoming 
data</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.5.0/org.apache.nifi.text.FreeFormTextRecordSetWriter/index.html">FreeFormTextRecordSetWriter</a><br/><a
 
href="../../../nifi-record-serialization-services-nar/1.5.0/org.apache.nifi.csv.CSVRecordSetWriter/index.html">CSVRecordSetWriter</a><br/><a
 
href="../../../nifi-record-serialization-services-nar/1.5.0/org.apache.nifi.avro.AvroRecordSetWriter/index.html">AvroRecordSetWriter</a><br/><a
 
href="../../../nifi-record-serialization-services-nar/1.5.0/org.apache.nifi.json.JsonRecordSetWriter/index.html">JsonRecordSetWriter</a><br/><a
 
href="../../../nifi-scripting-nar/1.5.0/org.apache.nifi.record.script.ScriptedRecordSetWriter/index.html">ScriptedRecordSetWriter</a></td><td
 id="description">Specifies the Controller Service to use for writing out the 
records</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 successfully transformed will be 
 routed to this relationship</td></tr><tr><td>failure</td><td>If a FlowFile 
cannot be transformed from the configured input format to the configured output 
format, the unchanged FlowFile 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>Sets
 the mime.type attribute to the MIME Type specified by the Record 
Writer</td></tr><tr><td>record.count</td><td>The number of records in the 
FlowFile</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.</body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.CountText/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.CountText/index.html?rev=1821033&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.CountText/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.CountText/index.html
 Fri Jan 12 21:00:14 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>CountText</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;">CountText</h1><h2>Description: </h2><p>Counts various metrics on 
incoming text. The requested results will be recorded as attributes. The 
resulting flowfile will not have its content modified.</p><h3>Tags: 
</h3><p>count, text, line, word, character</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>C
 ount Lines</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 enabled, will count the number of lines present in the 
incoming text.</td></tr><tr><td id="name"><strong>Count Non-Empty 
Lines</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 enabled, will count the number of lines that contain a 
non-whitespace character present in the incoming text.</td></tr><tr><td 
id="name"><strong>Count Words</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 enabled, will count the number of words (alphanumeric 
character groups bounded by whitespace) present in the incoming text. Common 
logical delimiters [_-.] do not bound a word unless 'Split Words on Symbols' is 
true.</td></tr><tr><td id="name"><strong>Count Characters</strong></td><td 
id="de
 fault-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">If enabled, will count the number of characters (including 
whitespace and symbols, but not including newlines and carriage returns) 
present in the incoming text.</td></tr><tr><td id="name"><strong>Split Words on 
Symbols</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 enabled, the word count will identify strings separated by 
common logical delimiters [ _ - . ] as independent words (ex. 
split-words-on-symbols = 4 words).</td></tr><tr><td id="name"><strong>Character 
Encoding</strong></td><td id="default-value">UTF-8</td><td 
id="allowable-values"><ul><li>ISO-8859-1</li><li>UTF-8</li><li>UTF-16</li><li>UTF-16LE</li><li>UTF-16BE</li><li>US-ASCII</li></ul></td><td
 id="description">Specifies a character encoding to 
use.</td></tr></table><h3>Relationships: </h3><table id="relationships"><tr><th
 >Name</th><th>Description</th></tr><tr><td>success</td><td>The flowfile 
 >contains the original content with one or more attributes added containing 
 >the respective counts</td></tr><tr><td>failure</td><td>If the flowfile text 
 >cannot be counted for some reason, the original file will be routed to this 
 >destination and nothing will be routed elsewhere</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>text.line.count</td><td>The
 > number of lines of text present in the FlowFile 
 >content</td></tr><tr><td>text.line.nonempty.count</td><td>The number of lines 
 >of text (with at least one non-whitespace character) present in the original 
 >FlowFile</td></tr><tr><td>text.word.count</td><td>The number of words present 
 >in the original FlowFile</td></tr><tr><td>text.character.count</td><td>The 
 >number of characters (given the specified character encoding) present in the 
 >original FlowFile</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>See 
 >Also:</h3><p><a 
 >href="../org.apache.nifi.processors.standard.SplitText/index.html">SplitText</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.5.0/org.apache.nifi.processors.standard.DebugFlow/additionalDetails.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.DebugFlow/additionalDetails.html?rev=1821033&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.DebugFlow/additionalDetails.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.DebugFlow/additionalDetails.html
 Fri Jan 12 21:00:14 2018
@@ -0,0 +1,48 @@
+<!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>DebugFlow</title>
+        <link rel="stylesheet" href="../../../../../css/component-usage.css" 
type="text/css"/>
+    </head>
+
+    <body>
+        <!-- Processor Documentation 
================================================== -->
+        <p>
+            When triggered, the processor loops through the appropriate 
response list (based on whether or not it
+            received a FlowFile).  A response is produced the configured 
number of times for each pass through its
+            response list, as long as the processor is running.
+        </p><p>
+            Triggered by a FlowFile, the processor can produce the following 
responses.
+            <ol>
+                <li>transfer FlowFile to success relationship.</li>
+                <li>transfer FlowFile to failure relationship.</li>
+                <li>rollback the FlowFile without penalty.</li>
+                <li>rollback the FlowFile and yield the context.</li>
+                <li>rollback the FlowFile with penalty.</li>
+                <li>throw an exception.</li>
+            </ol>
+        </p><p>
+            Triggered without a FlowFile, the processor can produce the 
following responses.
+            <ol>
+                <li>do nothing and return.</li>
+                <li>throw an exception.</li>
+                <li>yield the context.</li>
+            </ol>
+        </p>
+    </body>
+</html>

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.DebugFlow/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.DebugFlow/index.html?rev=1821033&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.DebugFlow/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.DebugFlow/index.html
 Fri Jan 12 21:00:14 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>DebugFlow</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;">DebugFlow</h1><h2>Description: </h2><p>The DebugFlow processor aids 
testing and debugging the FlowFile framework by allowing various responses to 
be explicitly triggered in response to the receipt of a FlowFile or a timer 
event without a FlowFile if using timer or cron based scheduling.  It can force 
responses needed to exercise or test various failure modes that can occur when 
a processor runs.</p><p><a href="additionalDetails.html">Additional 
Details...</a></p><h3>Tags: </h3><p>test, debug, processor, utility, flow, 
FlowFile</p><h3>Properties: </h3><p>In the list below, the names of required 
propert
 ies 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>FlowFile Success 
Iterations</strong></td><td id="default-value">1</td><td 
id="allowable-values"></td><td id="description">Number of FlowFiles to forward 
to success relationship.</td></tr><tr><td id="name"><strong>FlowFile Failure 
Iterations</strong></td><td id="default-value">0</td><td 
id="allowable-values"></td><td id="description">Number of FlowFiles to forward 
to failure relationship.</td></tr><tr><td id="name"><strong>FlowFile Rollback 
Iterations</strong></td><td id="default-value">0</td><td 
id="allowable-values"></td><td id="description">Number of FlowFiles to roll 
back (without penalty).</td></tr><tr><td id="name"><strong>FlowFile Rollback 
Yield Iterations</strong></td><td id="default-value">0</td><
 td id="allowable-values"></td><td id="description">Number of FlowFiles to roll 
back and yield.</td></tr><tr><td id="name"><strong>FlowFile Rollback Penalty 
Iterations</strong></td><td id="default-value">0</td><td 
id="allowable-values"></td><td id="description">Number of FlowFiles to roll 
back with penalty.</td></tr><tr><td id="name"><strong>FlowFile Exception 
Iterations</strong></td><td id="default-value">0</td><td 
id="allowable-values"></td><td id="description">Number of FlowFiles to throw 
exception.</td></tr><tr><td id="name"><strong>FlowFile Exception 
Class</strong></td><td id="default-value">java.lang.RuntimeException</td><td 
id="allowable-values"></td><td id="description">Exception class to be thrown 
(must extend java.lang.RuntimeException).</td></tr><tr><td id="name"><strong>No 
FlowFile Skip Iterations</strong></td><td id="default-value">1</td><td 
id="allowable-values"></td><td id="description">Number of times to skip 
onTrigger if no FlowFile.</td></tr><tr><td id="name"><stron
 g>No FlowFile Exception Iterations</strong></td><td 
id="default-value">0</td><td id="allowable-values"></td><td 
id="description">Number of times to throw NPE exception if no 
FlowFile.</td></tr><tr><td id="name"><strong>No FlowFile Yield 
Iterations</strong></td><td id="default-value">0</td><td 
id="allowable-values"></td><td id="description">Number of times to yield if no 
FlowFile.</td></tr><tr><td id="name"><strong>No FlowFile Exception 
Class</strong></td><td id="default-value">java.lang.RuntimeException</td><td 
id="allowable-values"></td><td id="description">Exception class to be thrown if 
no FlowFile (must extend java.lang.RuntimeException).</td></tr><tr><td 
id="name"><strong>Write Iterations</strong></td><td 
id="default-value">0</td><td id="allowable-values"></td><td 
id="description">Number of times to write to the FlowFile</td></tr><tr><td 
id="name"><strong>Content Size</strong></td><td id="default-value">1 KB</td><td 
id="allowable-values"></td><td id="description">The number of 
 bytes to write each time that the FlowFile is written to</td></tr><tr><td 
id="name"><strong>@OnScheduled Pause Time</strong></td><td id="default-value">0 
sec</td><td id="allowable-values"></td><td id="description">Specifies how long 
the processor should sleep in the @OnScheduled method, so that the processor 
can be forced to take a long time to start up</td></tr><tr><td 
id="name"><strong>Fail When @OnScheduled called</strong></td><td 
id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Specifies whether or not the Processor should throw an 
Exception when the methods annotated with @OnScheduled are 
called</td></tr><tr><td id="name"><strong>@OnUnscheduled Pause 
Time</strong></td><td id="default-value">0 sec</td><td 
id="allowable-values"></td><td id="description">Specifies how long the 
processor should sleep in the @OnUnscheduled method, so that the processor can 
be forced to take a long time to respond when user clicks st
 op</td></tr><tr><td id="name"><strong>Fail When @OnUnscheduled 
called</strong></td><td id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Specifies whether or not the Processor should throw an 
Exception when the methods annotated with @OnUnscheduled are 
called</td></tr><tr><td id="name"><strong>@OnStopped Pause 
Time</strong></td><td id="default-value">0 sec</td><td 
id="allowable-values"></td><td id="description">Specifies how long the 
processor should sleep in the @OnStopped method, so that the processor can be 
forced to take a long time to shutdown</td></tr><tr><td id="name"><strong>Fail 
When @OnStopped called</strong></td><td id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Specifies whether or not the Processor should throw an 
Exception when the methods annotated with @OnStopped are 
called</td></tr></table><h3>Relationships: </h3><table id="relatio
 
nships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>FlowFiles
 processed successfully.</td></tr><tr><td>failure</td><td>FlowFiles that failed 
to process.</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.</body></html>
\ No newline at end of file


Reply via email to