Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.EvaluateXPath/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.EvaluateXPath/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.EvaluateXPath/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.EvaluateXPath/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>EvaluateXPath</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;">EvaluateXPath</h1><h2>Description: </h2><p>Evaluates one or more XPaths 
against the content of a FlowFile. The results of those XPaths are assigned to 
FlowFile Attributes or are written to the content of the FlowFile itself, 
depending on configuration of the Processor. XPaths are entered by adding 
user-defined properties; the name of the property maps to the Attribute Name 
into which the result will be placed (if the Destination is flowfile-attribute; 
otherwise, the property name is ignored). The value of the property must be a 
valid XPath expression. If the XPath evaluates to more than one node a
 nd the Return Type is set to 'nodeset' (either directly, or via 'auto-detect' 
with a Destination of 'flowfile-content'), the FlowFile will be unmodified and 
will be routed to failure. If the XPath does not evaluate to a Node, the 
FlowFile will be routed to 'unmatched' without having its contents modified. If 
Destination is flowfile-attribute and the expression matches nothing, 
attributes will be created with empty strings as the value, and the FlowFile 
will always be routed to 'matched'</p><h3>Tags: </h3><p>XML, evaluate, 
XPath</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>Destination</strong></td><td 
id="default-value">flowfile-content</td><td id="allowable-values"><ul><li>fl
 owfile-content</li><li>flowfile-attribute</li></ul></td><td 
id="description">Indicates whether the results of the XPath evaluation are 
written to the FlowFile content or a FlowFile attribute; if using attribute, 
must specify the Attribute Name property. If set to flowfile-content, only one 
XPath may be specified, and the property name is ignored.</td></tr><tr><td 
id="name"><strong>Return Type</strong></td><td 
id="default-value">auto-detect</td><td 
id="allowable-values"><ul><li>auto-detect</li><li>nodeset</li><li>string</li></ul></td><td
 id="description">Indicates the desired return type of the Xpath expressions.  
Selecting 'auto-detect' will set the return type to 'nodeset' for a Destination 
of 'flowfile-content', and 'string' for a Destination of 
'flowfile-attribute'.</td></tr><tr><td id="name"><strong>Validate 
DTD</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 the XML con
 tent should be validated against the DTD.</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">A FlowFile attribute(if &lt;Destination&gt; is set to 
'flowfile-attribute'</td><td id="value">An XPath expression</td><td>If 
&lt;Destination&gt;='flowfile-attribute' then the FlowFile attribute is set to 
the result of the XPath Expression.  If &lt;Destination&gt;='flowfile-content' 
then the FlowFile content is set to the result of the XPath 
Expression.</td></tr></table></p><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>failure</td><td>FlowFiles
 are routed to this relationship when the XPath cannot be evaluated against the 
content of the FlowFile; for instance, if the FlowFile is not valid XML, or if 
the Return Type is 'nodeset' and the XPath evaluates to mu
 ltiple nodes</td></tr><tr><td>unmatched</td><td>FlowFiles are routed to this 
relationship when the XPath does not match the content of the FlowFile and the 
Destination is set to 
flowfile-content</td></tr><tr><td>matched</td><td>FlowFiles are routed to this 
relationship when the XPath is successfully evaluated and the FlowFile is 
modified as a result</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>user-defined</td><td>This
 processor adds user-defined attributes if the &lt;Destination&gt; property is 
set to flowfile-attribute.</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.EvaluateXQuery/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.EvaluateXQuery/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.EvaluateXQuery/additionalDetails.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.EvaluateXQuery/additionalDetails.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1,149 @@
+<!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>EvaluateXQuery</title>
+        <link rel="stylesheet" href="../../../../../css/component-usage.css"
+              type="text/css" />
+    </head>
+
+
+    <body>
+
+        <!-- Processor Documentation 
================================================== -->
+
+
+        <p>
+            <strong>Examples:</strong>
+        </p>
+
+        <p>This processor produces one attribute or FlowFile per
+            XQueryResult. If only one attribute or FlowFile is desired, the
+            following examples demonstrate how this can be achieved using the
+            XQuery language. The examples below reference the following sample
+            XML:</p>
+
+        <pre>
+               <code>
+  &lt;?xml version="1.0" encoding="UTF-8"?&gt;
+  &lt;?xml-stylesheet type="text/xsl" href="foo.xsl"?&gt;
+  &lt;ns:fruitbasket xmlns:ns="http://namespace/1"&gt;
+    &lt;fruit taste="crisp"&gt;    
+      &lt;!-- Apples are my favorite--&gt;   
+      &lt;name&gt;apple&lt;/name&gt;   
+      &lt;color&gt;red&lt;/color&gt;  
+    &lt;/fruit&gt;  
+    &lt;fruit&gt;   
+      &lt;name&gt;apple&lt;/name&gt;   
+      &lt;color&gt;green&lt;/color&gt;  
+    &lt;/fruit&gt;  
+    &lt;fruit&gt;   
+      &lt;name&gt;banana&lt;/name&gt;   
+      &lt;color&gt;yellow&lt;/color&gt;  
+    &lt;/fruit&gt;  
+    &lt;fruit taste="sweet"&gt;   
+      &lt;name&gt;orange&lt;/name&gt;   
+      &lt;color&gt;orange&lt;/color&gt;  
+    &lt;/fruit&gt;  
+    &lt;fruit&gt;   
+      &lt;name&gt;blueberry&lt;/name&gt;   
+      &lt;color&gt;blue&lt;/color&gt;  
+    &lt;/fruit&gt;  
+      &lt;fruit taste="tart"&gt;   
+      &lt;name&gt;raspberry&lt;/name&gt;   
+      &lt;color&gt;red&lt;/color&gt;  
+    &lt;/fruit&gt;  
+    &lt;fruit&gt;   
+      &lt;name&gt;none&lt;/name&gt;    
+      &lt;color/&gt;  
+    &lt;/fruit&gt;
+  &lt;/ns:fruitbasket&gt;
+</code>
+        </pre>
+
+        <p>
+        <ul>
+            <li>XQuery to return all "fruit" nodes individually (7 Results):
+                <ul>
+                    <li>//fruit</li>
+                </ul>
+            </li>
+            <li>XQuery to return only the first "fruit" node (1 Result):
+                <ul>
+                    <li>//fruit[1]</li>
+                </ul>
+            </li>
+            <li>XQuery to return only the last "fruit" node (1 Result):
+                <ul>
+                    <li>//fruit[count(//fruit)]</li>
+                </ul>
+            </li>
+            <li>XQuery to return all "fruit" nodes, wrapped in a "basket" tag
+                (1 Result):
+                <ul>
+                    <li>&lt;basket&gt;{//fruit}&lt;/basket&gt;</li>
+                </ul>
+            </li>
+            <li>XQuery to return all "fruit" names individually (7 Results):
+                <ul>
+                    <li>//fruit/text()</li>
+                </ul>
+            </li>
+            <li>XQuery to return only the first "fruit" name (1 Result):
+                <ul>
+                    <li>//fruit[1]/text()</li>
+                </ul>
+            </li>
+            <li>XQuery to return only the last "fruit" name (1 Result):
+                <ul>
+                    <li>//fruit[count(//fruit)]/text()</li>
+                </ul>
+            </li>
+            <li>XQuery to return all "fruit" names as a comma separated list
+                (1 Result):
+                <ul>
+                    <li>string-join((for $x in //fruit return $x/name/text()), 
',
+                        ')</li>
+                </ul>
+            </li>
+            <li>XQuery to return all "fruit" colors and names as a comma
+                separated list (1 Result):
+                <ul>
+                    <li>string-join((for $y in (for $x in //fruit return
+                        string-join(($x/color/text() , $x/name/text()), ' ')) 
return $y),
+                        ', ')</li>
+                </ul>
+            </li>
+            <li>XQuery to return all "fruit" colors and names as a comma
+                separated list (1 Result):
+                <ul>
+                    <li>string-join((for $y in (for $x in //fruit return
+                        string-join(($x/color/text() , $x/name/text()), ' ')) 
return $y),
+                        ', ')</li>
+                </ul>
+            </li>
+            <li>XQuery to return all "fruit" colors and names as a new line
+                separated list (1 Result):
+                <ul>
+                    <li>string-join((for $y in (for $x in //fruit return
+                        string-join(($x/color/text() , $x/name/text()), ' ')) 
return $y),
+                        '\n')</li>
+                </ul>
+            </li>
+        </ul>
+    </body>
+</html>

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.EvaluateXQuery/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.EvaluateXQuery/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.EvaluateXQuery/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.EvaluateXQuery/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>EvaluateXQuery</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;">EvaluateXQuery</h1><h2>Description: </h2><p>Evaluates one or more 
XQueries against the content of a FlowFile.  The results of those XQueries are 
assigned to FlowFile Attributes or are written to the content of the FlowFile 
itself, depending on configuration of the Processor.  XQueries are entered by 
adding user-defined properties; the name of the property maps to the Attribute 
Name into which the result will be placed (if the Destination is 
'flowfile-attribute'; otherwise, the property name is ignored).  The value of 
the property must be a valid XQuery.  If the XQuery returns more than one result
 , new attributes or FlowFiles (for Destinations of 'flowfile-attribute' or 
'flowfile-content' respectively) will be created for each result (attributes 
will have a '.n' one-up number appended to the specified attribute name).  If 
any provided XQuery returns a result, the FlowFile(s) will be routed to 
'matched'. If no provided XQuery returns a result, the FlowFile will be routed 
to 'unmatched'.  If the Destination is 'flowfile-attribute' and the XQueries 
matche nothing, no attributes will be applied to the FlowFile.</p><p><a 
href="additionalDetails.html">Additional Details...</a></p><h3>Tags: 
</h3><p>XML, evaluate, XPath, XQuery</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>Des
 tination</strong></td><td id="default-value">flowfile-content</td><td 
id="allowable-values"><ul><li>flowfile-content</li><li>flowfile-attribute</li></ul></td><td
 id="description">Indicates whether the results of the XQuery evaluation are 
written to the FlowFile content or a FlowFile attribute. If set to 
&lt;flowfile-content&gt;, only one XQuery may be specified and the property 
name is ignored.  If set to &lt;flowfile-attribute&gt; and the XQuery returns 
more than one result, multiple attributes will be added to theFlowFile, each 
named with a '.n' one-up number appended to the specified attribute 
name</td></tr><tr><td id="name"><strong>Output: Method</strong></td><td 
id="default-value">xml</td><td 
id="allowable-values"><ul><li>xml</li><li>html</li><li>text</li></ul></td><td 
id="description">Identifies the overall method that should be used for 
outputting a result tree.</td></tr><tr><td id="name"><strong>Output: Omit XML 
Declaration</strong></td><td id="default-value">false</td><td i
 d="allowable-values"></td><td id="description">Specifies whether the processor 
should output an XML declaration when transforming a result 
tree.</td></tr><tr><td id="name"><strong>Output: Indent</strong></td><td 
id="default-value">false</td><td id="allowable-values"></td><td 
id="description">Specifies whether the processor may add additional whitespace 
when outputting a result tree.</td></tr><tr><td id="name"><strong>Validate 
DTD</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 the XML content should be validated 
against the DTD.</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">A FlowFile attribute(if &lt;Destination&gt; is set to 
'flowfile-attribute'</td><td id="value">An XQuery</td><td>If 
 &lt;Destination&gt;='flowfile-attribute' then the FlowFile attribute is set to 
the result of the XQuery.  If &lt;Destination&gt;='flowfile-content' then the 
FlowFile content is set to the result of the 
XQuery.</td></tr></table></p><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>failure</td><td>FlowFiles
 are routed to this relationship when the XQuery cannot be evaluated against 
the content of the FlowFile.</td></tr><tr><td>unmatched</td><td>FlowFiles are 
routed to this relationship when the XQuery does not match the content of the 
FlowFile and the Destination is set to 
flowfile-content</td></tr><tr><td>matched</td><td>FlowFiles are routed to this 
relationship when the XQuery is successfully evaluated and the FlowFile is 
modified as a result</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>user-defined</td><td>This
 p
 rocessor adds user-defined attributes if the &lt;Destination&gt; property is 
set to flowfile-attribute .</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.ExecuteProcess/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.ExecuteProcess/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.ExecuteProcess/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.ExecuteProcess/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ExecuteProcess</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;">ExecuteProcess</h1><h2>Description: </h2><p>Runs an operating system 
command specified by the user and writes the output of that command to a 
FlowFile. If the command is expected to be long-running, the Processor can 
output the partial data on a specified interval. When this option is used, the 
output is expected to be in textual format, as it typically does not make sense 
to split binary data on arbitrary time-based intervals.</p><h3>Tags: 
</h3><p>command, process, source, external, invoke, script</p><h3>Properties: 
</h3><p>In the list below, the names of required properties appear in <strong>bo
 ld</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>Command</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Specifies the command to be 
executed; if just the name of an executable is provided, it must be in the 
user's environment PATH.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Command Arguments</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
arguments to supply to the executable delimited by white space. White space can 
be escaped by enclosing it in double-quotes.<br/><strong>Supports Expression 
Language: true</strong></td></tr><tr
 ><td id="name">Batch Duration</td><td id="default-value"></td><td 
 >id="allowable-values"></td><td id="description">If the process is expected to 
 >be long-running and produce textual output, a batch duration can be specified 
 >so that the output will be captured for this amount of time and a FlowFile 
 >will then be sent out with the results and a new FlowFile will be started, 
 >rather than waiting for the process to finish before sending out the 
 >results</td></tr><tr><td id="name">Redirect Error Stream</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 redirect any error stream output of the process 
 >to the output stream. This is particularly helpful for processes which write 
 >extensively to the error stream or for troubleshooting.</td></tr><tr><td 
 >id="name">Working Directory</td><td id="default-value"></td><td 
 >id="allowable-values"></td><td id="description">The directory to use as the 
 >current working directo
 ry when executing the command<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Argument 
Delimiter</strong></td><td id="default-value"> </td><td 
id="allowable-values"></td><td id="description">Delimiter to use to separate 
arguments for a command [default: space]. Must be a single 
character.</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">An environment variable name</td><td id="value">An environment 
variable value</td><td>These environment variables are passed to the process 
spawned by this Processor</td></tr></table></p><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>All
 created FlowFiles are routed to this relationship</td></tr></table><h3>Reads 
Attributes: </h3>None specified.<h3>Writes 
 Attributes: </h3><table 
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>command</td><td>Executed
 command</td></tr><tr><td>command.arguments</td><td>Arguments of the 
command</td></tr></table><h3>State management: </h3>This component does not 
store state.<h3>Restricted: </h3><table id="restrictions"><tr><th>Required 
Permission</th><th>Explanation</th></tr><tr><td>execute code</td><td>Provides 
operator the ability to execute arbitrary code assuming all permissions that 
NiFi has.</td></tr></table><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.ExecuteSQL/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.ExecuteSQL/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.ExecuteSQL/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.ExecuteSQL/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ExecuteSQL</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;">ExecuteSQL</h1><h2>Description: </h2><p>Executes provided SQL select 
query. Query result will be converted to Avro format. Streaming is used so 
arbitrarily large result sets are supported. This processor can be scheduled to 
run on a timer, or cron expression, using the standard scheduling methods, or 
it can be triggered by an incoming FlowFile. If it is triggered by an incoming 
FlowFile, then attributes of that FlowFile will be available when evaluating 
the select query, and the query may use the ? to escape parameters. In this 
case, the parameters to use must exist as FlowFile attributes with the na
 ming convention sql.args.N.type and sql.args.N.value, where N is a positive 
integer. The sql.args.N.type is expected to be a number indicating the JDBC 
Type. The content of the FlowFile is expected to be in UTF-8 format. FlowFile 
attribute 'executesql.row.count' indicates how many rows were 
selected.</p><h3>Tags: </h3><p>sql, select, jdbc, query, 
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 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>Database Connection Pooling Service</strong></td><td 
id="default-value"></td><td id="allowable-values"><strong>Controller Service 
API: </strong><br/>DBCPS
 ervice<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">SQL select query</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
SQL select query to execute. The query can be empty, a constant value, or built 
from attributes using Expression Language. If this property is specified, it 
will be used regardless of the content of incoming flowfiles. If this property 
is empty, the content of the incoming flow file is expected to contain a valid 
SQL select query, to be issued by the processor to the database. Note that 
Expression Language is not evaluated for flow file 
contents.<br/><strong>Supports Expression 
 Language: true</strong></td></tr><tr><td id="name"><strong>Max Wait 
Time</strong></td><td id="default-value">0 seconds</td><td 
id="allowable-values"></td><td id="description">The maximum amount of time 
allowed for a running SQL select query  , zero means there is no limit. Max 
time less than 1 second will be equal to zero.</td></tr><tr><td 
id="name"><strong>Normalize Table/Column Names</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 change non-Avro-compatible characters in column 
names to Avro-compatible characters. For example, colons and periods will be 
changed to underscores in order to build a valid Avro record.</td></tr><tr><td 
id="name"><strong>Use Avro Logical Types</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 use Avro Logical Types for DECIMAL/NUMBER, DATE, 
TIME and TIMESTAMP colum
 ns. If disabled, written as string. If enabled, Logical types are used and 
written as its underlying type, specifically, DECIMAL/NUMBER as logical 
'decimal': written as bytes with additional precision and scale meta data, DATE 
as logical 'date-millis': written as int denoting days since Unix epoch 
(1970-01-01), TIME as logical 'time-millis': written as int denoting 
milliseconds since Unix epoch, and TIMESTAMP as logical 'timestamp-millis': 
written as long denoting milliseconds since Unix epoch. If a reader of written 
Avro records also knows these logical types, then these values can be 
deserialized with more context depending on reader 
implementation.</td></tr><tr><td id="name"><strong>Default Decimal 
Precision</strong></td><td id="default-value">10</td><td 
id="allowable-values"></td><td id="description">When a DECIMAL/NUMBER value is 
written as a 'decimal' Avro logical type, a specific 'precision' denoting 
number of available digits is required. Generally, precision is defined by c
 olumn data type definition or database engines default. However undefined 
precision (0) can be returned from some database engines. 'Default Decimal 
Precision' is used when writing those undefined precision 
numbers.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Default Decimal 
Scale</strong></td><td id="default-value">0</td><td 
id="allowable-values"></td><td id="description">When a DECIMAL/NUMBER value is 
written as a 'decimal' Avro logical type, a specific 'scale' denoting number of 
available decimal digits is required. Generally, scale is defined by column 
data type definition or database engines default. However when undefined 
precision (0) is returned, scale can also be uncertain with some database 
engines. 'Default Decimal Scale' is used when writing those undefined numbers. 
If a value has more decimals than specified scale, then the value will be 
rounded-up, e.g. 1.53 becomes 2 with scale 0, and 1.5 with scale 
1.<br/><strong>Support
 s 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>Successfully
 created FlowFile from SQL query result 
set.</td></tr><tr><td>failure</td><td>SQL query execution failed. Incoming 
FlowFile will be penalized and routed to this 
relationship</td></tr></table><h3>Reads Attributes: </h3><table 
id="reads-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>sql.args.N.type</td><td>Incoming
 FlowFiles are expected to be parametrized SQL statements. The type of each 
Parameter is specified as an integer that represents the JDBC Type of the 
parameter.</td></tr><tr><td>sql.args.N.value</td><td>Incoming FlowFiles are 
expected to be parametrized SQL statements. The value of the Parameters are 
specified as sql.args.1.value, sql.args.2.value, sql.args.3.value, and so on. 
The type of the sql.args.1.value Parameter is specified by the sql.args.1.type 
attribute.</td></tr><tr><td
 >sql.args.N.format</td><td>This attribute is always optional, but default 
 >options may not always work for your data. Incoming FlowFiles are expected to 
 >be parametrized SQL statements. In some cases a format option needs to be 
 >specified, currently this is only applicable for binary data types, dates, 
 >times and timestamps. Binary Data Types (defaults to 'ascii') - ascii: each 
 >string character in your attribute value represents a single byte. This is 
 >the format provided by Avro Processors. base64: the string is a Base64 
 >encoded string that can be decoded to bytes. hex: the string is hex encoded 
 >with all letters in upper case and no '0x' at the beginning. 
 >Dates/Times/Timestamps - Date, Time and Timestamp formats all support both 
 >custom formats or named format ('yyyy-MM-dd','ISO_OFFSET_DATE_TIME') as 
 >specified according to java.time.format.DateTimeFormatter. If not specified, 
 >a long value input is expected to be an unix epoch (milli seconds from 
 >1970/1/1), or a string value in 'yyyy-MM-d
 d' format for Date, 'HH:mm:ss.SSS' for Time (some database engines e.g. Derby 
or MySQL do not support milliseconds and will truncate milliseconds), 
'yyyy-MM-dd HH:mm:ss.SSS' for Timestamp is used.</td></tr></table><h3>Writes 
Attributes: </h3><table 
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>executesql.row.count</td><td>Contains
 the number of rows returned in the select 
query</td></tr><tr><td>executesql.query.duration</td><td>Duration of the query 
in milliseconds</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.ExecuteStreamCommand/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.ExecuteStreamCommand/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.ExecuteStreamCommand/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.ExecuteStreamCommand/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ExecuteStreamCommand</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;">ExecuteStreamCommand</h1><h2>Description: </h2><p>Executes an external 
command on the contents of a flow file, and creates a new flow file with the 
results of the command.</p><h3>Tags: </h3><p>command execution, command, 
stream, execute</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="pr
 operties"><tr><th>Name</th><th>Default Value</th><th>Allowable 
Values</th><th>Description</th></tr><tr><td id="name">Command Arguments</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
arguments to supply to the executable delimited by the ';' 
character.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Command Path</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Specifies the command to be executed; if just the name of an 
executable is provided, it must be in the user's environment 
PATH.<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
id="name">Ignore STDIN</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, the contents of the incoming flowfile will not be 
passed to the executing command</td></tr><tr><td id="name">Working 
Directory</td><td id="default-va
 lue"></td><td id="allowable-values"></td><td id="description">The directory to 
use as the current working directory when executing the 
command<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Argument 
Delimiter</strong></td><td id="default-value">;</td><td 
id="allowable-values"></td><td id="description">Delimiter to use to separate 
arguments for a command [default: ;]. Must be a single 
character</td></tr><tr><td id="name">Output Destination Attribute</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">If 
set, the output of the stream command will be put into an attribute of the 
original FlowFile instead of a separate FlowFile. There will no longer be a 
relationship for 'output stream' or 'nonzero status'. The value of this 
property will be the key for the output attribute.</td></tr><tr><td 
id="name">Max Attribute Length</td><td id="default-value">256</td><td 
id="allowable-values"></td><td id="description">If r
 outing the output of the stream command to an attribute, 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 truncated to fit. Consider making this smaller if 
able.</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">An environment variable name</td><td id="value">An environment 
variable value</td><td>These environment variables are passed to the process 
spawned by this Processor</td></tr></table></p><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>output 
stream</td><td>The destination path for the flow file created from the 
command's output, if the returne
 d status code is zero.</td></tr><tr><td>nonzero status</td><td>The destination 
path for the flow file created from the command's output, if the returned 
status code is non-zero. All flow files routed to this relationship will be 
penalized.</td></tr><tr><td>original</td><td>FlowFiles that were successfully 
processed.</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>execution.command</td><td>The
 name of the command 
executed</td></tr><tr><td>execution.command.args</td><td>The semi-colon 
delimited list of arguments</td></tr><tr><td>execution.status</td><td>The exit 
status code returned from executing the 
command</td></tr><tr><td>execution.error</td><td>Any error messages returned 
from executing the command</td></tr></table><h3>State management: </h3>This 
component does not store state.<h3>Restricted: </h3><table 
id="restrictions"><tr><th>Required Permission</th><th>Expla
 nation</th></tr><tr><td>execute code</td><td>Provides operator the ability to 
execute arbitrary code assuming all permissions that NiFi 
has.</td></tr></table><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.ExtractGrok/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.ExtractGrok/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.ExtractGrok/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.ExtractGrok/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ExtractGrok</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;">ExtractGrok</h1><h2>Description: </h2><p>Evaluates one or more Grok 
Expressions against the content of a FlowFile, adding the results as attributes 
or replacing the content of the FlowFile with a JSON notation of the matched 
content</p><h3>Tags: </h3><p>grok, log, text, parse, delimit, 
extract</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>Grok 
Expression</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Grok 
expression</td></tr><tr><td id="name"><strong>Grok Pattern 
file</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Grok Pattern file 
definition</td></tr><tr><td id="name"><strong>Destination</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 Grok output value is written as a new flowfile 
attributes, in this case each of the Grok identifier that is matched in the 
flowfile will be added as an attribute, prefixed with "grok." or written in the 
flowfile content. Writing to flowfile content will overwrite any existing 
flowfile content.</td></tr><tr><td id="name"><strong>Character 
Set</strong></td><td id="default-value">UTF-8</td><td id="allowable-values"></td
 ><td id="description">The Character Set in which the file is 
 >encoded</td></tr><tr><td id="name"><strong>Maximum Buffer 
 >Size</strong></td><td id="default-value">1 MB</td><td 
 >id="allowable-values"></td><td id="description">Specifies the maximum amount 
 >of data to buffer (per file) in order to apply the Grok expressions. Files 
 >larger than the specified maximum will not be fully 
 >evaluated.</td></tr><tr><td id="name"><strong>Named captures 
 >only</strong></td><td id="default-value">false</td><td 
 >id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
 >id="description">Only store named captures from 
 >grok</td></tr></table><h3>Relationships: </h3><table 
 >id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>unmatched</td><td>FlowFiles
 > are routed to this relationship when no provided Grok Expression matches the 
 >content of the FlowFile</td></tr><tr><td>matched</td><td>FlowFiles are routed 
 >to this relationship when the Grok Expression is successfully evaluated and 
 >the Flow
 File is modified as a result</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>grok.XXX</td><td>When
 operating in flowfile-attribute mode, each of the Grok identifier that is 
matched in the flowfile will be added as an attribute, prefixed with "grok." 
For example,if the grok identifier "timestamp" is matched, then the value will 
be added to an attribute named "grok.timestamp"</td></tr></table><h3>State 
management: </h3>This component does not store state.<h3>Restricted: </h3>This 
component is not restricted.<h3>System Resource Considerations:</h3>None 
specified.</body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.ExtractText/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.ExtractText/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.ExtractText/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.ExtractText/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1,2 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ExtractText</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;">ExtractText</h1><h2>Description: </h2><p>Evaluates one or more Regular 
Expressions against the content of a FlowFile.  The results of those Regular 
Expressions are assigned to FlowFile Attributes.  Regular Expressions are 
entered by adding user-defined properties; the name of the property maps to the 
Attribute Name into which the result will be placed.  The first capture group, 
if any found, will be placed into that attribute name.But all capture groups, 
including the matching string sequence itself will also be provided at that 
attribute name with an index value provided, with the exception of a ca
 pturing group that is optional and does not match - for example, given the 
attribute name "regex" and expression "abc(def)?(g)" we would add an attribute 
"regex.1" with a value of "def" if the "def" matched. If the "def" did not 
match, no attribute named "regex.1" would be added but an attribute named 
"regex.2" with a value of "g" will be added regardless.The value of the 
property must be a valid Regular Expressions with one or more capturing groups. 
If the Regular Expression matches more than once, only the first match will be 
used unless the property enabling repeating capture group is set to true. If 
any provided Regular Expression matches, the FlowFile(s) will be routed to 
'matched'. If no provided Regular Expression matches, the FlowFile will be 
routed to 'unmatched' and no attributes will be applied to the 
FlowFile.</p><h3>Tags: </h3><p>evaluate, extract, Text, Regular Expression, 
regex</p><h3>Properties: </h3><p>In the list below, the names of required 
properties appear in <s
 trong>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>Character 
Set</strong></td><td id="default-value">UTF-8</td><td 
id="allowable-values"></td><td id="description">The Character Set in which the 
file is encoded</td></tr><tr><td id="name"><strong>Maximum Buffer 
Size</strong></td><td id="default-value">1 MB</td><td 
id="allowable-values"></td><td id="description">Specifies the maximum amount of 
data to buffer (per file) in order to apply the regular expressions.  Files 
larger than the specified maximum will not be fully evaluated.</td></tr><tr><td 
id="name">Maximum Capture Group Length</td><td id="default-value">1024</td><td 
id="allowable-values"></td><td id="description">Specifies the maximum number of 
characters a given capture group value can have.  Any characters beyond 
 the max will be truncated.</td></tr><tr><td id="name"><strong>Enable Canonical 
Equivalence</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 that two characters match only when their full 
canonical decompositions match.</td></tr><tr><td id="name"><strong>Enable 
Case-insensitive Matching</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 that two characters match even if they are in a 
different case.  Can also be specified via the embedded flag 
(?i).</td></tr><tr><td id="name"><strong>Permit Whitespace and Comments in 
Pattern</strong></td><td id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">In this mode, whitespace is ignored, and embedded comments 
starting with # are ignored until the end of a line.  Can also be specified via 
the em
 bedded flag (?x).</td></tr><tr><td id="name"><strong>Enable DOTALL 
Mode</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 that the expression '.' should match any character, 
including a line terminator.  Can also be specified via the embedded flag 
(?s).</td></tr><tr><td id="name"><strong>Enable Literal Parsing of the 
Pattern</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 that Metacharacters and escape characters should be 
given no special meaning.</td></tr><tr><td id="name"><strong>Enable Multiline 
Mode</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 that '^' and '$' should match just after and just 
before a line terminator or end of sequence, instead of only the beginning or 
end of the entire input. 
  Can also be specified via the embeded flag (?m).</td></tr><tr><td 
id="name"><strong>Enable Unicode-aware Case Folding</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 used with 'Enable Case-insensitive Matching', matches in 
a manner consistent with the Unicode Standard.  Can also be specified via the 
embedded flag (?u).</td></tr><tr><td id="name"><strong>Enable Unicode 
Predefined Character Classes</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 conformance with the Unicode Technical Standard #18: 
Unicode Regular Expression Annex C: Compatibility Properties.  Can also be 
specified via the embedded flag (?U).</td></tr><tr><td id="name"><strong>Enable 
Unix Lines Mode</strong></td><td id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Ind
 icates that only the '
+' line terminator is recognized in the behavior of '.', '^', and '$'.  Can 
also be specified via the embedded flag (?d).</td></tr><tr><td 
id="name"><strong>Include Capture Group 0</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 that Capture Group 0 should be included as an 
attribute. Capture Group 0 represents the entirety of the regular expression 
match, is typically not used, and could have considerable 
length.</td></tr><tr><td id="name"><strong>Enable repeating capture 
group</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 set to true, every string matching the capture groups will 
be extracted. Otherwise, if the Regular Expression matches more than once, only 
the first match will be extracted.</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">A FlowFile attribute</td><td id="value">A Regular Expression with 
one or more capturing group</td><td>The first capture group, if any found, will 
be placed into that attribute name.But all capture groups, including the 
matching string sequence itself will also be provided at that attribute name 
with an index value provided.</td></tr></table></p><h3>Relationships: 
</h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>unmatched</td><td>FlowFiles
 are routed to this relationship when no provided Regular Expression matches 
the content of the FlowFile</td></tr><tr><td>matched</td><td>FlowFiles are 
routed to this relationship when the Regular Expression is successfully 
evaluated and the FlowFile is modified as a result</td></tr></table><h3>Reads 
Attributes: </h3>None specified.<h3>Writes Attributes: </h3>None 
specified.<h3>State managem
 ent: </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.FetchDistributedMapCache/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.FetchDistributedMapCache/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.FetchDistributedMapCache/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.FetchDistributedMapCache/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>FetchDistributedMapCache</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;">FetchDistributedMapCache</h1><h2>Description: </h2><p>Computes cache 
key(s) from FlowFile attributes, for each incoming FlowFile, and fetches the 
value(s) from the Distributed Map Cache associated with each key. If configured 
without a destination attribute, the incoming FlowFile's content is replaced 
with the binary data received by the Distributed Map Cache. If there is no 
value stored under that key then the flow file will be routed to 'not-found'. 
Note that the processor will always attempt to read the entire cached value 
into memory before placing it in it's destination. This could
  be potentially problematic if the cached value is very large.</p><h3>Tags: 
</h3><p>map, cache, fetch, distributed</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>Cache Entry Identifier</strong></td><td 
id="default-value">${hash.value}</td><td id="allowable-values"></td><td 
id="description">A comma-delimited list of FlowFile attributes, or the results 
of Attribute Expression Language statements, which will be evaluated against a 
FlowFile in order to determine the value(s) used to identify duplicates; it is 
these values that are cached. NOTE: Only a singl
 e Cache Entry Identifier is allowed unless Put Cache Value In Attribute is 
specified. Multiple cache lookups are only supported when the destination is a 
set of attributes (see the documentation for 'Put Cache Value In Attribute' for 
more details including naming convention.<br/><strong>Supports Expression 
Language: true</strong></td></tr><tr><td id="name"><strong>Distributed Cache 
Service</strong></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">The Controller Service that is used to get the cached 
values.</td></tr><tr><td id="name">Put Cache Value In Attribute</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">If 
set, the cache value received will be put into an attribute of the FlowFile 
instead of a the content of theFlowFile. The attribute key to put to is 
determined by evaluating value of this property. If multiple Cache Entry 
Identifiers are selected, multiple attributes will be written, using the 
evaluated value of this property, appended by a period (.) and the name of the 
cache entry identifier.<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 cache value to an attribute of the FlowFile (by 
setting the "Pu
 t Cache Value in attribute" property), 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">Character Set</td><td id="default-value">UTF-8</td><td 
id="allowable-values"></td><td id="description">The Character Set in which the 
cached value is encoded. This will only be used when routing to an 
attribute.</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>If
 the cache was successfully communicated with it will be routed to this 
relationship</td></tr><tr><td>failure</td><td>If unable to communicate with the 
cache or if the cache entry is evaluated to be blank, the FlowFile will be 
penalized and routed to this relationship</td></
 tr><tr><td>not-found</td><td>If a FlowFile's Cache Entry Identifier was not 
found in the cache, 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>user-defined</td><td>If
 the 'Put Cache Value In Attribute' property is set then whatever it is set to 
will become the attribute key and the value would be whatever the response was 
from the Distributed Map Cache. If multiple cache entry identifiers are 
selected, multiple attributes will be written, using the evaluated value of 
this property, appended by a period (.) and the name of the cache entry 
identifier. For example, if the Cache Entry Identifier property is set to 
'id,name', and the user-defined property is named 'fetched', then two 
attributes will be written, fetched.id and fetched.name, containing their 
respective values.</td></tr></table><h3>State management: </h3>This componen
 t does not store state.<h3>Restricted: </h3>This component is not 
restricted.<h3>Input requirement: </h3>This component requires an incoming 
relationship.<h3>System Resource Considerations:</h3>None specified.<h3>See 
Also:</h3><p><a 
href="../../../nifi-distributed-cache-services-nar/1.6.0/org.apache.nifi.distributed.cache.client.DistributedMapCacheClientService/index.html">DistributedMapCacheClientService</a>,
 <a 
href="../../../nifi-distributed-cache-services-nar/1.6.0/org.apache.nifi.distributed.cache.server.map.DistributedMapCacheServer/index.html">DistributedMapCacheServer</a>,
 <a 
href="../org.apache.nifi.processors.standard.PutDistributedMapCache/index.html">PutDistributedMapCache</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.FetchFTP/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.FetchFTP/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.FetchFTP/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.FetchFTP/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>FetchFTP</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;">FetchFTP</h1><h2>Description: </h2><p>Fetches the content of a file from 
a remote SFTP server and overwrites the contents of an incoming FlowFile with 
the content of the remote file.</p><h3>Tags: </h3><p>ftp, get, retrieve, files, 
fetch, remote, ingest, source, input</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>, a
 nd 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 host to fetch the data from<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 Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Username</strong></td><td 
id="default-value"></td><td id="allo
 wable-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"><strong>Remote File</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
fully qualified filename on the remote system<br/><strong>Supports Expression 
Language: true</strong></td></tr><tr><td id="name"><strong>Completion 
Strategy</strong></td><td id="default-value">None</td><td 
id="allowable-values"><ul><li>None <img 
src="../../../../../html/images/iconInfo.png" alt="Leave the file as-is" 
title="Leave the file as-is"></img></li><li>Move File <img 
src="../../../../../html/images/iconInfo.png" alt="Move the file to the 
directory specified by the &lt;Move Destinatio
 n Directory&gt; property" title="Move the file to the directory specified by 
the &lt;Move Destination Directory&gt; property"></img></li><li>Delete File 
<img src="../../../../../html/images/iconInfo.png" alt="Deletes the original 
file from the remote system" title="Deletes the original file from the remote 
system"></img></li></ul></td><td id="description">Specifies what to do with the 
original file on the server once it has been pulled into NiFi. If the 
Completion Strategy fails, a warning will be logged but the data will still be 
transferred.</td></tr><tr><td id="name">Move Destination Directory</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
directory on the remote server to the move the original file to once it has 
been ingested into NiFi. This property is ignored unless the Completion 
Strategy is set to "Move File". The specified directory must already exist 
onthe remote system, or the rename will fail.<br/><strong>Supports Expression 
Lang
 uage: true</strong></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>Use Compression</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 ZLIB compression should be used when 
transferring files</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="description">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></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><tr><td>comms.failure</td><td>Any FlowFile that could not be 
fetched from the remote server due to a communications failure will be 
transferred to this Relationship.</td></tr><tr><td>not.found</td><td>Any 
FlowFile for which we receive a 'Not Found' message from the remote server will 
be transferred to this 
Relationship.</td></tr><tr><td>permission.denied</td><td>Any FlowFile that 
could not be fetched from the remote server due to insufficient permissions 
will be transferred to this Relationshi
 p.</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 or IP address from which the file was 
pulled</td></tr><tr><td>ftp.remote.port</td><td>The port that was used to 
communicate with the remote FTP 
server</td></tr><tr><td>ftp.remote.filename</td><td>The name of the remote file 
that was pulled</td></tr><tr><td>filename</td><td>The filename is updated to 
point to the filename fo the remote file</td></tr><tr><td>path</td><td>If the 
Remote File contains a directory name, that directory name will be added to the 
FlowFile using the 'path' attribute</td></tr></table><h3>State management: 
</h3>This component does not store state.<h3>Restricted: </h3>This component is 
not restricted.<h3>Input requirement: </h3>This component requires an incoming 
relationship.<h3>System Resource Considerations:</h3>None specified.<h3>See 
Also:</h3><p><a href=
 "../org.apache.nifi.processors.standard.GetSFTP/index.html">GetSFTP</a>, <a 
href="../org.apache.nifi.processors.standard.PutSFTP/index.html">PutSFTP</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></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.FetchFile/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.FetchFile/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.FetchFile/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.FetchFile/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>FetchFile</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;">FetchFile</h1><h2>Description: </h2><p>Reads the contents of a file from 
disk and streams it into the contents of an incoming FlowFile. Once this is 
done, the file is optionally moved elsewhere or deleted to help keep the file 
system organized.</p><h3>Tags: </h3><p>local, files, filesystem, ingest, 
ingress, get, source, input, fetch</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>File to Fetch</strong></td><td 
id="default-value">${absolute.path}/${filename}</td><td 
id="allowable-values"></td><td id="description">The fully-qualified filename of 
the file to fetch from the file system<br/><strong>Supports Expression 
Language: true</strong></td></tr><tr><td id="name"><strong>Completion 
Strategy</strong></td><td id="default-value">None</td><td 
id="allowable-values"><ul><li>None <img 
src="../../../../../html/images/iconInfo.png" alt="Leave the file as-is" 
title="Leave the file as-is"></img></li><li>Move File <img 
src="../../../../../html/images/iconInfo.png" alt="Moves the file to the 
directory specified by the &lt;Move Destination Directory&gt; property" 
title="Moves the file to the directory specified by the &lt;Move Destination 
Directory&gt; property"><
 /img></li><li>Delete File <img src="../../../../../html/images/iconInfo.png" 
alt="Deletes the original file from the file system" title="Deletes the 
original file from the file system"></img></li></ul></td><td 
id="description">Specifies what to do with the original file on the file system 
once it has been pulled into NiFi</td></tr><tr><td id="name">Move Destination 
Directory</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">The directory to the move the original file to once it has 
been fetched from the file system. This property is ignored unless the 
Completion Strategy is set to "Move File". If the directory does not exist, it 
will be created.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Move Conflict 
Strategy</strong></td><td id="default-value">Rename</td><td 
id="allowable-values"><ul><li>Rename <img 
src="../../../../../html/images/iconInfo.png" alt="The existing destination 
file should remain intact.
  The newly ingested file should be moved to the destination directory but be 
renamed to a random filename" title="The existing destination file should 
remain intact. The newly ingested file should be moved to the destination 
directory but be renamed to a random filename"></img></li><li>Replace File <img 
src="../../../../../html/images/iconInfo.png" alt="The newly ingested file 
should replace the existing file in the Destination Directory" title="The newly 
ingested file should replace the existing file in the Destination 
Directory"></img></li><li>Keep Existing <img 
src="../../../../../html/images/iconInfo.png" alt="The existing file should in 
the Destination Directory should stay intact and the newly ingested file should 
be deleted" title="The existing file should in the Destination Directory should 
stay intact and the newly ingested file should be deleted"></img></li><li>Fail 
<img src="../../../../../html/images/iconInfo.png" alt="The existing 
destination file should remain intact a
 nd the incoming FlowFile should be routed to failure" title="The existing 
destination file should remain intact and the incoming FlowFile should be 
routed to failure"></img></li></ul></td><td id="description">If Completion 
Strategy is set to Move File and a file already exists in the destination 
directory with the same name, this property specifies how that naming conflict 
should be resolved</td></tr><tr><td id="name"><strong>Log level when file not 
found</strong></td><td id="default-value">ERROR</td><td 
id="allowable-values"><ul><li>TRACE</li><li>DEBUG</li><li>INFO</li><li>WARN</li><li>ERROR</li><li>FATAL</li><li>NONE</li></ul></td><td
 id="description">Log level to use in case the file does not exist when the 
processor is triggered</td></tr><tr><td id="name"><strong>Log level when 
permission denied</strong></td><td id="default-value">ERROR</td><td 
id="allowable-values"><ul><li>TRACE</li><li>DEBUG</li><li>INFO</li><li>WARN</li><li>ERROR</li><li>FATAL</li><li>NONE</li></ul></td><td
 i
 d="description">Log level to use in case user jwitt does not have sufficient 
permissions to read the file</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 fetched from the file system will be transferred 
to this Relationship.</td></tr><tr><td>not.found</td><td>Any FlowFile that 
could not be fetched from the file system because the file could not be found 
will be transferred to this 
Relationship.</td></tr><tr><td>permission.denied</td><td>Any FlowFile that 
could not be fetched from the file system due to the user running NiFi not 
having sufficient permissions will be transferred to this 
Relationship.</td></tr><tr><td>failure</td><td>Any FlowFile that could not be 
fetched from the file system for any reason other than insufficient permissions 
or the file not existing will be transferred to this 
Relationship.</td></tr></table><h3>Reads Attributes: </h3>None specified.<h
 3>Writes Attributes: </h3>None specified.<h3>State management: </h3>This 
component does not store state.<h3>Restricted: </h3><table 
id="restrictions"><tr><th>Required 
Permission</th><th>Explanation</th></tr><tr><td>read 
filesystem</td><td>Provides operator the ability to read from any file that 
NiFi has access to.</td></tr><tr><td>write filesystem</td><td>Provides operator 
the ability to delete any file that NiFi has access 
to.</td></tr></table><h3>Input requirement: </h3>This component requires an 
incoming relationship.<h3>System Resource Considerations:</h3>None 
specified.<h3>See Also:</h3><p><a 
href="../org.apache.nifi.processors.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.ListFile/index.html">ListFile</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.FetchSFTP/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.FetchSFTP/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.FetchSFTP/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.FetchSFTP/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>FetchSFTP</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;">FetchSFTP</h1><h2>Description: </h2><p>Fetches the content of a file 
from a remote SFTP server and overwrites the contents of an incoming FlowFile 
with the content of the remote file.</p><h3>Tags: </h3><p>sftp, get, retrieve, 
files, fetch, remote, ingest, source, input</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>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 host to fetch the data from<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 Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Username</strong></td><td 
id="default-value"></td><td id="a
 llowable-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"><strong>Remote File</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description"
 >The fully qualified filename on the remote system<br/><strong>Supports 
 >Expression Language: true</strong></td></tr><tr><td 
 >id="name"><strong>Completion Strategy</strong></td><td 
 >id="default-value">None</td><td id="allowable-values"><ul><li>None <img 
 >src="../../../../../html/images/iconInfo.png" alt="Leave the file as-is" 
 >title="Leave the file as-is"></img></li><li>Move File <img 
 >src="../../../../../html/images/iconInfo.png" alt="Move the file to the 
 >directory specified by the &lt;Move Destination Directory&gt; property" 
 >title="Move the file to the directory specified by the &lt;Move Destination 
 >Directory&gt; property"></img></li><li>Delete File <img 
 >src="../../../../../html/images/iconInfo.png" alt="Deletes the original file 
 >from the remote system" title="Deletes the original file from the remote 
 >system"></img></li></ul></td><td id="description">Specifies what to do with 
 >the original file on the server once it has been pulled into NiFi. If the 
 >Completion Strategy fails, a warning w
 ill be logged but the data will still be transferred.</td></tr><tr><td 
id="name">Move Destination Directory</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The directory on the remote 
server to the move the original file to once it has been ingested into NiFi. 
This property is ignored unless the Completion Strategy is set to "Move File". 
The specified directory must already exist onthe remote system, or the rename 
will fail.<br/><strong>Supports Expression Language: 
true</strong></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 e
 lapse 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">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>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"><strong>Use 
Compression</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 ZLIB compression should be 
used when transferring files</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><tr><td>comms.failure</td><td>Any FlowFile that could not be 
fetched from the remote server due to a communications failure will be 
transferred to this Relationship.</td></tr><tr><td>not.found</td><td>Any 
FlowFile for which we receive a 'Not Found' message from the remote server will 
be transferred to this 
Relationship.</td></tr><tr><td>permission.denied</td><td>Any FlowFile that 
could not be fetched from the remote server due to insufficient permissions 
will be transferred 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>sftp.remote.host</td><td>Th
 e hostname or IP address from which the file was 
pulled</td></tr><tr><td>sftp.remote.port</td><td>The port that was used to 
communicate with the remote SFTP 
server</td></tr><tr><td>sftp.remote.filename</td><td>The name of the remote 
file that was pulled</td></tr><tr><td>filename</td><td>The filename is updated 
to point to the filename fo the remote file</td></tr><tr><td>path</td><td>If 
the Remote File contains a directory name, that directory name will be added to 
the FlowFile using the 'path' attribute</td></tr></table><h3>State management: 
</h3>This component does not store state.<h3>Restricted: </h3>This component is 
not restricted.<h3>Input requirement: </h3>This component requires an incoming 
relationship.<h3>System Resource Considerations:</h3>None specified.<h3>See 
Also:</h3><p><a 
href="../org.apache.nifi.processors.standard.GetSFTP/index.html">GetSFTP</a>, 
<a 
href="../org.apache.nifi.processors.standard.PutSFTP/index.html">PutSFTP</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></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.FlattenJson/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.FlattenJson/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.FlattenJson/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.FlattenJson/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>FlattenJson</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;">FlattenJson</h1><h2>Description: </h2><p>Provides the user with the 
ability to take a nested JSON document and flatten it into a simple key/value 
pair document. The keys are combined at each level with a user-defined 
separator that defaults to '.'. Support three kinds of flatten mode, normal, 
keep-arrays and dot notation for MongoDB query. Default flatten mode is 
'keep-arrays'.</p><h3>Tags: </h3><p>json, flatten</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 ind
 icates 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">Separator</td><td id="default-value">.</td><td 
id="allowable-values"></td><td id="description">The separator character used 
for joining keys. Must be a JSON-legal character.<br/><strong>Supports 
Expression Language: true</strong></td></tr><tr><td id="name"><strong>Flatten 
Mode</strong></td><td id="default-value">keep arrays</td><td 
id="allowable-values"><ul><li>normal <img 
src="../../../../../html/images/iconInfo.png" alt="Flattens every objects into 
a single level json" title="Flattens every objects into a single level 
json"></img></li><li>keep arrays <img 
src="../../../../../html/images/iconInfo.png" alt="Flattens every objects and 
keep arrays format" title="Flattens every objects and keep arrays fo
 rmat"></img></li><li>dot notation <img 
src="../../../../../html/images/iconInfo.png" alt="Conforms to MongoDB dot 
notation to update also nested documents" title="Conforms to MongoDB dot 
notation to update also nested documents"></img></li></ul></td><td 
id="description">Specifies how json is 
flattened</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>Successfully
 flattened files go to this 
relationship.</td></tr><tr><td>failure</td><td>Files that cannot be flattened 
go 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.<h3>System Resource Considerations:</h3>None 
specified.</body></html>
\ No newline at end of file


Reply via email to