Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.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.2.0/org.apache.nifi.processors.standard.ConvertRecord/index.html?rev=1794596&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.ConvertRecord/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.ConvertRecord/index.html
 Tue May  9 15:27:39 2017
@@ -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, 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><br/><a 
href="../../../nifi-record-serialization-services-nar/1.2.0/org.apache.nifi.json.JsonT
 reeReader/index.html">JsonTreeReader</a><br/><a 
href="../../../nifi-scripting-nar/1.2.0/org.apache.nifi.record.script.ScriptedReader/index.html">ScriptedReader</a><br/><a
 
href="../../../nifi-record-serialization-services-nar/1.2.0/org.apache.nifi.csv.CSVReader/index.html">CSVReader</a><br/><a
 
href="../../../nifi-record-serialization-services-nar/1.2.0/org.apache.nifi.avro.AvroReader/index.html">AvroReader</a><br/><a
 
href="../../../nifi-record-serialization-services-nar/1.2.0/org.apache.nifi.grok.GrokReader/index.html">GrokReader</a><br/><a
 
href="../../../nifi-record-serialization-services-nar/1.2.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><br/><a hr
 
ef="../../../nifi-scripting-nar/1.2.0/org.apache.nifi.record.script.ScriptedRecordSetWriter/index.html">ScriptedRecordSetWriter</a><br/><a
 
href="../../../nifi-record-serialization-services-nar/1.2.0/org.apache.nifi.text.FreeFormTextRecordSetWriter/index.html">FreeFormTextRecordSetWriter</a><br/><a
 
href="../../../nifi-record-serialization-services-nar/1.2.0/org.apache.nifi.avro.AvroRecordSetWriter/index.html">AvroRecordSetWriter</a><br/><a
 
href="../../../nifi-record-serialization-services-nar/1.2.0/org.apache.nifi.json.JsonRecordSetWriter/index.html">JsonRecordSetWriter</a><br/><a
 
href="../../../nifi-record-serialization-services-nar/1.2.0/org.apache.nifi.csv.CSVRecordSetWriter/index.html">CSVRecordSetWriter</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 b
 e 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.</body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.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.2.0/org.apache.nifi.processors.standard.DebugFlow/additionalDetails.html?rev=1794596&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.DebugFlow/additionalDetails.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.DebugFlow/additionalDetails.html
 Tue May  9 15:27:39 2017
@@ -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.2.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.2.0/org.apache.nifi.processors.standard.DebugFlow/index.html?rev=1794596&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.DebugFlow/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.DebugFlow/index.html
 Tue May  9 15:27:39 2017
@@ -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

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.DetectDuplicate/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.DetectDuplicate/index.html?rev=1794596&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.DetectDuplicate/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.DetectDuplicate/index.html
 Tue May  9 15:27:39 2017
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>DetectDuplicate</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;">DetectDuplicate</h1><h2>Description: </h2><p>Caches a value, computed 
from FlowFile attributes, for each incoming FlowFile and determines if the 
cached value has already been seen. If so, routes the FlowFile to 'duplicate' 
with an attribute named 'original.identifier' that specifies the original 
FlowFile's "description", which is specified in the &lt;FlowFile 
Description&gt; property. If the FlowFile is not determined to be a duplicate, 
the Processor routes the FlowFile to 'non-duplicate'</p><h3>Tags: </h3><p>hash, 
dupe, duplicate, dedupe</p><h3>Properties: </h3><p>In the list below, the names 
o
 f 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 FlowFile attribute, or the results of an Attribute 
Expression Language statement, which will be evaluated against a FlowFile in 
order to determine the value used to identify duplicates; it is this value that 
is cached<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>FlowFile 
Description</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">When a FlowFile
  is added to the cache, this value is stored along with it so that if a 
duplicate is found, this description of the original FlowFile will be added to 
the duplicate's "original.flowfile.description" attribute<br/><strong>Supports 
Expression Language: true</strong></td></tr><tr><td id="name">Age Off 
Duration</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">Time interval to age off cached FlowFiles</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>Implementation:</strong><br/><a
 
href="../../../nifi-distributed-cache-services-nar/1.2.0/org.apache.nifi.distributed.cache.client.DistributedMapCacheClientService/index.html">DistributedMapCacheClientService</a></td><td
 id="description">The Controller Service that is used to cache unique 
identifiers, used to determine duplicates</td></tr><tr><td id
 ="name">Cache The Entry Identifier</td><td id="default-value">true</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">When true this cause the processor to check for duplicates and 
cache the Entry Identifier. When false, the processor would only check for 
duplicates and not cache the Entry Identifier, requiring another processor to 
add identifiers to the distributed cache.</td></tr></table><h3>Relationships: 
</h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>duplicate</td><td>If
 a FlowFile has been detected to be a duplicate, it will be routed to this 
relationship</td></tr><tr><td>non-duplicate</td><td>If a FlowFile's Cache Entry 
Identifier was not found in the cache, it will be routed to this 
relationship</td></tr><tr><td>failure</td><td>If unable to communicate with the 
cache, the FlowFile will be penalized and routed to this 
relationship</td></tr></table><h3>Reads Attributes: </h3>None 
specified.<h3>Writes Att
 ributes: </h3><table 
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>original.flowfile.description</td><td>All
 FlowFiles routed to the duplicate relationship will have an attribute added 
named original.flowfile.description. The value of this attribute is determined 
by the attributes of the original copy of the data and by the FlowFile 
Description property.</td></tr></table><h3>State management: </h3>This 
component does not store state.<h3>Restricted: </h3>This component is not 
restricted.<h3>See Also:</h3><p><a 
href="../../../nifi-distributed-cache-services-nar/1.2.0/org.apache.nifi.distributed.cache.client.DistributedMapCacheClientService/index.html">DistributedMapCacheClientService</a>,
 <a 
href="../../../nifi-distributed-cache-services-nar/1.2.0/org.apache.nifi.distributed.cache.server.map.DistributedMapCacheServer/index.html">DistributedMapCacheServer</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.2.0/org.apache.nifi.processors.standard.DistributeLoad/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.DistributeLoad/index.html?rev=1794596&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.DistributeLoad/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.DistributeLoad/index.html
 Tue May  9 15:27:39 2017
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>DistributeLoad</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;">DistributeLoad</h1><h2>Description: </h2><p>Distributes FlowFiles to 
downstream processors based on a Distribution Strategy. If using the Round 
Robin strategy, the default is to assign each destination a weighting of 1 
(evenly distributed). However, optional propertiescan be added to the change 
this; adding a property with the name '5' and value '10' means that the 
relationship with name '5' will be receive 10 FlowFiles in each iteration 
instead of 1.</p><h3>Tags: </h3><p>distribute, load balance, route, round 
robin, weighted</p><h3>Properties: </h3><p>In the list below, the names of 
required pro
 perties 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>Number of 
Relationships</strong></td><td id="default-value">1</td><td 
id="allowable-values"></td><td id="description">Determines the number of 
Relationships to which the load should be distributed</td></tr><tr><td 
id="name"><strong>Distribution Strategy</strong></td><td 
id="default-value">round robin</td><td id="allowable-values"><ul><li>round 
robin</li><li>next available</li><li>load distribution 
service</li></ul></td><td id="description">Determines how the load will be 
distributed. If using Round Robin, will not distribute any FlowFiles unless all 
destinations can accept FlowFiles; when using Next Available, will distribute 
FlowFiles as long as at least 1 destination can accept FlowFiles.</td></tr><
 /table><h3>Dynamic Properties: </h3><p>Dynamic Properties allow the user to 
specify both the name and value of a property.<table 
id="dynamic-properties"><tr><th>Name</th><th>Value</th><th>Description</th></tr><tr><td
 id="name">The relationship name(positive number)</td><td id="value">The 
relationship Weight(positive number)</td><td>adding a property with the name 
'5' and value '10' means that the relationship with name '5' will be receive 10 
FlowFiles in each iteration instead of 
1.</td></tr></table></p><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>1</td><td>Where
 to route flowfiles for this relationship index</td></tr></table><h3>Dynamic 
Relationships: </h3><p>A Dynamic Relationship may be created based on how the 
user configures the Processor.<table 
id="dynamic-relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>A 
number 1..&lt;Number Of Relationships&gt;</td><td>FlowFiles are sent to this 
relationship per the &lt;
 Distribution Strategy&gt;</td></tr></table></p><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-standard-nar/1.2.0/org.apache.nifi.processors.standard.DuplicateFlowFile/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.DuplicateFlowFile/index.html?rev=1794596&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.DuplicateFlowFile/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.DuplicateFlowFile/index.html
 Tue May  9 15:27:39 2017
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>DuplicateFlowFile</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;">DuplicateFlowFile</h1><h2>Description: </h2><p>Intended for load 
testing, this processor will create the configured number of copies of each 
incoming FlowFile</p><h3>Tags: </h3><p>test, load, duplicate</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>Number of 
Copies</strong></td><td id="de
 fault-value">100</td><td id="allowable-values"></td><td 
id="description">Specifies how many copies of each incoming FlowFile will be 
made</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>The
 original FlowFile and all copies will be sent 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-standard-nar/1.2.0/org.apache.nifi.processors.standard.EncryptContent/additionalDetails.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.EncryptContent/additionalDetails.html?rev=1794596&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.EncryptContent/additionalDetails.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.EncryptContent/additionalDetails.html
 Tue May  9 15:27:39 2017
@@ -0,0 +1,30 @@
+<!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>EncryptContent</title>
+        <link rel="stylesheet" href="../../../../../css/component-usage.css" 
type="text/css"/>
+    </head>
+
+    <body>
+        <!-- Processor Documentation 
================================================== -->
+        <p>
+            <strong>Note:</strong> This processor supports OpenPGP algorithms 
that are compatible with third party programs.
+            However, it currently cannot add a digital signature to an 
encrypted FlowFile.
+        </p>
+    </body>
+</html>

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.EncryptContent/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.EncryptContent/index.html?rev=1794596&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.EncryptContent/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.EncryptContent/index.html
 Tue May  9 15:27:39 2017
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>EncryptContent</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;">EncryptContent</h1><h2>Description: </h2><p>Encrypts or Decrypts a 
FlowFile using either symmetric encryption with a password and randomly 
generated salt, or asymmetric encryption using a public and secret 
key.</p><p><a href="additionalDetails.html">Additional 
Details...</a></p><h3>Tags: </h3><p>encryption, decryption, password, JCE, 
OpenPGP, PGP, GPG</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 consid
 ered "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>Mode</strong></td><td id="default-value">Encrypt</td><td 
id="allowable-values"><ul><li>Encrypt</li><li>Decrypt</li></ul></td><td 
id="description">Specifies whether the content should be encrypted or 
decrypted</td></tr><tr><td id="name"><strong>Key Derivation 
Function</strong></td><td id="default-value">BCRYPT</td><td 
id="allowable-values"><ul><li>NiFi Legacy KDF <img 
src="../../../../../html/images/iconInfo.png" alt="MD5 @ 1000 iterations" 
title="MD5 @ 1000 iterations"></img></li><li>OpenSSL EVP_BytesToKey <img 
src="../../../../../html/images/iconInfo.png" alt="Single iteration MD5 
compatible with PKCS#5 v1.5" ti
 tle="Single iteration MD5 compatible with PKCS#5 v1.5"></img></li><li>Bcrypt 
<img src="../../../../../html/images/iconInfo.png" alt="Bcrypt with 
configurable work factor. See Admin Guide" title="Bcrypt with configurable work 
factor. See Admin Guide"></img></li><li>Scrypt <img 
src="../../../../../html/images/iconInfo.png" alt="Scrypt with configurable 
cost parameters. See Admin Guide" title="Scrypt with configurable cost 
parameters. See Admin Guide"></img></li><li>PBKDF2 <img 
src="../../../../../html/images/iconInfo.png" alt="PBKDF2 with configurable 
hash function and iteration count. See Admin Guide" title="PBKDF2 with 
configurable hash function and iteration count. See Admin 
Guide"></img></li><li>None <img src="../../../../../html/images/iconInfo.png" 
alt="The cipher is given a raw key conforming to the algorithm specifications" 
title="The cipher is given a raw key conforming to the algorithm 
specifications"></img></li></ul></td><td id="description">Specifies the key 
derivation fun
 ction to generate the key from the password (and salt)</td></tr><tr><td 
id="name"><strong>Encryption Algorithm</strong></td><td 
id="default-value">MD5_128AES</td><td id="allowable-values"><ul><li>MD5_128AES 
<img src="../../../../../html/images/iconInfo.png" 
alt="org.apache.nifi.security.util.EncryptionMethod@53f7a906[Algorithm 
name=PBEWITHMD5AND128BITAES-CBC-OPENSSL,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" 
title="org.apache.nifi.security.util.EncryptionMethod@53f7a906[Algorithm 
name=PBEWITHMD5AND128BITAES-CBC-OPENSSL,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>MD5_192AES <img 
src="../../../../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHMD5AND192BITAES-CBC-OPENSSL,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" t
 itle="EncryptionMethod[Algorithm 
name=PBEWITHMD5AND192BITAES-CBC-OPENSSL,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>MD5_256AES <img 
src="../../../../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHMD5AND256BITAES-CBC-OPENSSL,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHMD5AND256BITAES-CBC-OPENSSL,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>MD5_DES <img 
src="../../../../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHMD5ANDDES,Requires unlimited strength JCE policy=false,Algorithm 
Provider=BC,Compatible with strong KDFs=false,Keyed cipher=false]" 
title="EncryptionMethod[Algorithm name=PBEWITHMD5ANDDES,Requires unlimited 
strength JCE 
 policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>MD5_RC2 <img 
src="../../../../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHMD5ANDRC2,Requires unlimited strength JCE policy=false,Algorithm 
Provider=BC,Compatible with strong KDFs=false,Keyed cipher=false]" 
title="EncryptionMethod[Algorithm name=PBEWITHMD5ANDRC2,Requires unlimited 
strength JCE policy=false,Algorithm Provider=BC,Compatible with strong 
KDFs=false,Keyed cipher=false]"></img></li><li>SHA1_RC2 <img 
src="../../../../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHA1ANDRC2,Requires unlimited strength JCE policy=false,Algorithm 
Provider=BC,Compatible with strong KDFs=false,Keyed cipher=false]" 
title="EncryptionMethod[Algorithm name=PBEWITHSHA1ANDRC2,Requires unlimited 
strength JCE policy=false,Algorithm Provider=BC,Compatible with strong 
KDFs=false,Keyed cipher=false]"></img></li><li>SHA1_DES <img src="../../../../..
 /html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHA1ANDDES,Requires unlimited strength JCE policy=false,Algorithm 
Provider=BC,Compatible with strong KDFs=false,Keyed cipher=false]" 
title="EncryptionMethod[Algorithm name=PBEWITHSHA1ANDDES,Requires unlimited 
strength JCE policy=false,Algorithm Provider=BC,Compatible with strong 
KDFs=false,Keyed cipher=false]"></img></li><li>SHA_128AES <img 
src="../../../../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND128BITAES-CBC-BC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND128BITAES-CBC-BC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA_192AES <img 
src="../../../../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND192BITAES-CBC-BC,Requires unli
 mited strength JCE policy=true,Algorithm Provider=BC,Compatible with strong 
KDFs=false,Keyed cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND192BITAES-CBC-BC,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA_256AES <img 
src="../../../../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND256BITAES-CBC-BC,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND256BITAES-CBC-BC,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA_40RC2 <img 
src="../../../../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND40BITRC2-CBC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keye
 d cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND40BITRC2-CBC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA_128RC2 <img 
src="../../../../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND128BITRC2-CBC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND128BITRC2-CBC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA_40RC4 <img 
src="../../../../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND40BITRC4,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND40BITRC4,Requires unlimited stren
 gth JCE policy=false,Algorithm Provider=BC,Compatible with strong 
KDFs=false,Keyed cipher=false]"></img></li><li>SHA_128RC4 <img 
src="../../../../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND128BITRC4,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND128BITRC4,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA256_128AES <img 
src="../../../../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHA256AND128BITAES-CBC-BC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHA256AND128BITAES-CBC-BC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed ciphe
 r=false]"></img></li><li>SHA256_192AES <img 
src="../../../../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHA256AND192BITAES-CBC-BC,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHA256AND192BITAES-CBC-BC,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA256_256AES <img 
src="../../../../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHA256AND256BITAES-CBC-BC,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHA256AND256BITAES-CBC-BC,Requires unlimited strength JCE 
policy=true,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA_2KEYTRIPLEDES <img src="../../../../../h
 tml/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND2-KEYTRIPLEDES-CBC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND2-KEYTRIPLEDES-CBC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA_3KEYTRIPLEDES <img 
src="../../../../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND3-KEYTRIPLEDES-CBC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]" title="EncryptionMethod[Algorithm 
name=PBEWITHSHAAND3-KEYTRIPLEDES-CBC,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>SHA_TWOFISH <img 
src="../../../../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PBEWI
 THSHAANDTWOFISH-CBC,Requires unlimited strength JCE policy=false,Algorithm 
Provider=BC,Compatible with strong KDFs=false,Keyed cipher=false]" 
title="EncryptionMethod[Algorithm name=PBEWITHSHAANDTWOFISH-CBC,Requires 
unlimited strength JCE policy=false,Algorithm Provider=BC,Compatible with 
strong KDFs=false,Keyed cipher=false]"></img></li><li>PGP <img 
src="../../../../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PGP,Requires unlimited strength JCE policy=false,Algorithm 
Provider=BC,Compatible with strong KDFs=false,Keyed cipher=false]" 
title="EncryptionMethod[Algorithm name=PGP,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>PGP_ASCII_ARMOR <img 
src="../../../../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=PGP-ASCII-ARMOR,Requires unlimited strength JCE policy=false,Algorithm 
Provider=BC,Compatible with strong KDFs=false,Keyed cipher=false]" 
title="Encrypt
 ionMethod[Algorithm name=PGP-ASCII-ARMOR,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=false,Keyed 
cipher=false]"></img></li><li>AES_CBC <img 
src="../../../../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=AES/CBC/PKCS7Padding,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=true,Keyed 
cipher=true]" title="EncryptionMethod[Algorithm 
name=AES/CBC/PKCS7Padding,Requires unlimited strength JCE 
policy=false,Algorithm Provider=BC,Compatible with strong KDFs=true,Keyed 
cipher=true]"></img></li><li>AES_CTR <img 
src="../../../../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=AES/CTR/NoPadding,Requires unlimited strength JCE policy=false,Algorithm 
Provider=BC,Compatible with strong KDFs=true,Keyed cipher=true]" 
title="EncryptionMethod[Algorithm name=AES/CTR/NoPadding,Requires unlimited 
strength JCE policy=false,Algorithm Provider=BC,Compatible with strong KDFs=t
 rue,Keyed cipher=true]"></img></li><li>AES_GCM <img 
src="../../../../../html/images/iconInfo.png" alt="EncryptionMethod[Algorithm 
name=AES/GCM/NoPadding,Requires unlimited strength JCE policy=false,Algorithm 
Provider=BC,Compatible with strong KDFs=true,Keyed cipher=true]" 
title="EncryptionMethod[Algorithm name=AES/GCM/NoPadding,Requires unlimited 
strength JCE policy=false,Algorithm Provider=BC,Compatible with strong 
KDFs=true,Keyed cipher=true]"></img></li></ul></td><td id="description">The 
Encryption Algorithm to use</td></tr><tr><td id="name"><strong>Allow insecure 
cryptographic modes</strong></td><td id="default-value">not-allowed</td><td 
id="allowable-values"><ul><li>Allowed <img 
src="../../../../../html/images/iconInfo.png" alt="Operation will not be 
blocked and no alerts will be presented when unsafe combinations of encryption 
algorithms and passwords are provided" title="Operation will not be blocked and 
no alerts will be presented when unsafe combinations of encryption algor
 ithms and passwords are provided"></img></li><li>Not Allowed <img 
src="../../../../../html/images/iconInfo.png" alt="When set, operation will be 
blocked and alerts will be presented to the user if unsafe combinations of 
encryption algorithms and passwords are provided on a JVM with limited strength 
crypto. To fix this, see the Admin Guide." title="When set, operation will be 
blocked and alerts will be presented to the user if unsafe combinations of 
encryption algorithms and passwords are provided on a JVM with limited strength 
crypto. To fix this, see the Admin Guide."></img></li></ul></td><td 
id="description">Overrides the default behavior to prevent unsafe combinations 
of encryption algorithms and short passwords on JVMs with limited strength 
cryptographic jurisdiction policies</td></tr><tr><td id="name">Password</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
Password to use for encrypting or decrypting the data<br/><strong>Sensitive 
Proper
 ty: true</strong></td></tr><tr><td id="name">Raw Key (hexadecimal)</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">In 
keyed encryption, this is the raw key, encoded in 
hexadecimal<br/><strong>Sensitive Property: true</strong></td></tr><tr><td 
id="name">Public Keyring File</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">In a PGP encrypt mode, this 
keyring contains the public key of the recipient</td></tr><tr><td 
id="name">Public Key User Id</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">In a PGP encrypt mode, this 
user id of the recipient</td></tr><tr><td id="name">Private Keyring 
File</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">In a PGP decrypt mode, this keyring contains the private key 
of the recipient</td></tr><tr><td id="name">Private Keyring Passphrase</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="descripti
 on">In a PGP decrypt mode, this is the private keyring 
passphrase<br/><strong>Sensitive Property: 
true</strong></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 encrypted or decrypted will be routed to 
success</td></tr><tr><td>failure</td><td>Any FlowFile that cannot be encrypted 
or decrypted 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.</body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.EnforceOrder/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.EnforceOrder/index.html?rev=1794596&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.EnforceOrder/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.EnforceOrder/index.html
 Tue May  9 15:27:39 2017
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>EnforceOrder</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;">EnforceOrder</h1><h2>Description: </h2><p>Enforces expected ordering of 
FlowFiles those belong to the same data group.  Although 
PriorityAttributePrioritizer can be used on a connection to ensure that flow 
files going through that connection are in priority order, depending on 
error-handling, branching, and other flow designs, it is possible for FlowFiles 
to get out-of-order. EnforceOrder can be used to enforce original ordering for 
those FlowFiles. [IMPORTANT] In order to take effect of EnforceOrder, 
FirstInFirstOutPrioritizer should be used at EVERY downstream relationship 
UNTIL the order of Flow
 Files physically get FIXED by operation such as MergeContent or being stored 
to the final destination.</p><h3>Tags: </h3><p>sort, order</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>Group Identifier</strong></td><td 
id="default-value">${filename}</td><td id="allowable-values"></td><td 
id="description">EnforceOrder is capable of multiple ordering groups. 'Group 
Identifier' is used to determine which group a FlowFile belongs to. This 
property will be evaluated with each incoming FlowFile. If evaluated result is 
empty, the FlowFile will be routed to failu
 re.<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
id="name"><strong>Order Attribute</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">A name of FlowFile attribute 
whose value will be used to enforce order of FlowFiles within a group. If a 
FlowFile does not have this attribute, or its value is not an integer, the 
FlowFile will be routed to failure.</td></tr><tr><td id="name"><strong>Initial 
Order</strong></td><td id="default-value">0</td><td 
id="allowable-values"></td><td id="description">When the first FlowFile of a 
group arrives, initial target order will be computed and stored in the managed 
state. After that, target order will start being tracked by EnforceOrder and 
stored in the state management store. If Expression Language is used but 
evaluated result was not an integer, then the FlowFile will be routed to 
failure, and initial order will be left unknown until consecutive FlowFiles 
provide a valid initial ord
 er.<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
id="name">Maximum Order</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">If specified, any FlowFiles 
that have larger order will be routed to failure. This property is computed 
only once for a given group. After a maximum order is computed, it will be 
persisted in the state management store and used for other FlowFiles belonging 
to the same group. If Expression Language is used but evaluated result was not 
an integer, then the FlowFile will be routed to failure, and maximum order will 
be left unknown until consecutive FlowFiles provide a valid maximum 
order.<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
id="name"><strong>Batch Count</strong></td><td id="default-value">1000</td><td 
id="allowable-values"></td><td id="description">The maximum number of FlowFiles 
that EnforceOrder can process at an execution.</td></tr><tr><td 
id="name"><strong>Wait T
 imeout</strong></td><td id="default-value">10 min</td><td 
id="allowable-values"></td><td id="description">Indicates the duration after 
which waiting FlowFiles will be routed to the 'overtook' 
relationship.</td></tr><tr><td id="name"><strong>Inactive 
Timeout</strong></td><td id="default-value">30 min</td><td 
id="allowable-values"></td><td id="description">Indicates the duration after 
which state for an inactive group will be cleared from managed state. Group is 
determined as inactive if any new incoming FlowFile has not seen for a group 
for specified duration. Inactive Timeout must be longer than Wait Timeout. If a 
FlowFile arrives late after its group is already cleared, it will be treated as 
a brand new group, but will never match the order since expected preceding 
FlowFiles are already gone. The FlowFile will eventually timeout for waiting 
and routed to 'overtook'. To avoid this, group states should be kept long 
enough, however, shorter duration would be helpful for reusing the sa
 me group identifier again.</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>overtook</td><td>A
 FlowFile that waited for preceding FlowFiles longer than Wait Timeout and 
overtook those FlowFiles, will be routed to this 
relationship.</td></tr><tr><td>skipped</td><td>A FlowFile that has an order 
younger than current, which means arrived too late and skipped, will be routed 
to this relationship.</td></tr><tr><td>success</td><td>A FlowFile with a 
matching order number will be routed to this 
relationship.</td></tr><tr><td>wait</td><td>A FlowFile with non matching order 
will be routed to this relationship</td></tr><tr><td>failure</td><td>A 
FlowFiles which does not have required attributes, or fails to compute those 
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>EnforceO
 rder.startedAt</td><td>All FlowFiles going through this processor will have 
this attribute. This value is used to determine wait 
timeout.</td></tr><tr><td>EnforceOrder.result</td><td>All FlowFiles going 
through this processor will have this attribute denoting which relationship it 
was routed to.</td></tr><tr><td>EnforceOrder.detail</td><td>FlowFiles routed to 
'failure' or 'skipped' relationship will have this attribute describing 
details.</td></tr><tr><td>EnforceOrder.expectedOrder</td><td>FlowFiles routed 
to 'wait' or 'skipped' relationship will have this attribute denoting expected 
order when the FlowFile was processed.</td></tr></table><h3>State management: 
</h3><table 
id="stateful"><tr><th>Scope</th><th>Description</th></tr><tr><td>LOCAL</td><td>EnforceOrder
 uses following states per ordering group: '&lt;groupId&gt;.target' is a order 
number which is being waited to arrive next. When a FlowFile with a matching 
order arrives, or a FlowFile overtakes the FlowFile being waited for 
 because of wait timeout, target order will be updated to (FlowFile.order + 1). 
'&lt;groupId&gt;.max is the maximum order number for a group. 
'&lt;groupId&gt;.updatedAt' is a timestamp when the order of a group was 
updated last time. These managed states will be removed automatically once a 
group is determined as inactive, see 'Inactive Timeout' for 
detail.</td></tr></table><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.2.0/org.apache.nifi.processors.standard.EvaluateJsonPath/additionalDetails.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.EvaluateJsonPath/additionalDetails.html?rev=1794596&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.EvaluateJsonPath/additionalDetails.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.EvaluateJsonPath/additionalDetails.html
 Tue May  9 15:27:39 2017
@@ -0,0 +1,31 @@
+<!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>EvaluateJsonPath</title>
+        <link rel="stylesheet" href="../../../../../css/component-usage.css" 
type="text/css"/>
+    </head>
+
+    <body>
+        <!-- Processor Documentation 
================================================== -->
+        <p>
+            <strong>Note:</strong> The underlying JsonPath library loads the 
entirety of the streamed content into and performs
+            result evaluations in memory. Accordingly, it is important to 
consider the anticipated profile of content being
+            evaluated by this processor and the hardware supporting it 
especially when working against large JSON documents.
+        </p>
+    </body>
+</html>

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.EvaluateJsonPath/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.EvaluateJsonPath/index.html?rev=1794596&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.EvaluateJsonPath/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.EvaluateJsonPath/index.html
 Tue May  9 15:27:39 2017
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>EvaluateJsonPath</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;">EvaluateJsonPath</h1><h2>Description: </h2><p>Evaluates one or more 
JsonPath expressions against the content of a FlowFile. The results of those 
expressions are assigned to FlowFile Attributes or are written to the content 
of the FlowFile itself, depending on configuration of the Processor. JsonPaths 
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 JsonPath expression. A Return Type o
 f 'auto-detect' will make a determination based off the configured 
destination. When 'Destination' is set to 'flowfile-attribute,' a return type 
of 'scalar' will be used. When 'Destination' is set to 'flowfile-content,' a 
return type of 'JSON' will be used.If the JsonPath evaluates to a JSON array or 
JSON object and the Return Type is set to 'scalar' the FlowFile will be 
unmodified and will be routed to failure. A Return Type of JSON can return 
scalar values if the provided JsonPath evaluates to the specified value and 
will be routed as a match.If Destination is 'flowfile-content' and the JsonPath 
does not evaluate to a defined path, 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><p><a 
href="additionalDetails.html">Additional Details...</a></p><h3>Tags: </h3><p>JS
 ON, evaluate, JsonPath</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>flowfile-content</li><li>flowfile-attribute</li></ul></td><td
 id="description">Indicates whether the results of the JsonPath 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 
JsonPath 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>jso
 n</li><li>scalar</li></ul></td><td id="description">Indicates the desired 
return type of the JSON Path expressions.  Selecting 'auto-detect' will set the 
return type to 'json' for a Destination of 'flowfile-content', and 'scalar' for 
a Destination of 'flowfile-attribute'.</td></tr><tr><td id="name"><strong>Path 
Not Found Behavior</strong></td><td id="default-value">ignore</td><td 
id="allowable-values"><ul><li>warn</li><li>ignore</li></ul></td><td 
id="description">Indicates how to handle missing JSON path expressions when 
destination is set to 'flowfile-attribute'. Selecting 'warn' will generate a 
warning when a JSON path expression is not found.</td></tr><tr><td 
id="name"><strong>Null Value Representation</strong></td><td 
id="default-value">empty string</td><td id="allowable-values"><ul><li>empty 
string</li><li>the string 'null'</li></ul></td><td id="description">Indicates 
the desired representation of JSON Path expressions resulting in a null 
value.</td></tr></table><h3>Dynamic Pro
 perties: </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">A JsonPath expression</td><td>If 
&lt;Destination&gt;='flowfile-attribute' then that FlowFile attribute will be 
set to any JSON objects that match the JsonPath.  If 
&lt;Destination&gt;='flowfile-content' then the FlowFile content will be 
updated to any JSON objects that match the 
JsonPath.</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 JsonPath cannot be evaluated against 
the content of the FlowFile; for instance, if the FlowFile is not valid 
JSON</td></tr><tr><td>unmatched</td><td>FlowFiles are routed to this 
relationship when the JsonPath does not m
 atch 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 JsonPath 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 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.2.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.2.0/org.apache.nifi.processors.standard.EvaluateXPath/index.html?rev=1794596&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.EvaluateXPath/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.EvaluateXPath/index.html
 Tue May  9 15:27:39 2017
@@ -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></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></t
 r><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 multiple 
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 
re
 lationship 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.</body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.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.2.0/org.apache.nifi.processors.standard.EvaluateXQuery/additionalDetails.html?rev=1794596&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.EvaluateXQuery/additionalDetails.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.EvaluateXQuery/additionalDetails.html
 Tue May  9 15:27:39 2017
@@ -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.2.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.2.0/org.apache.nifi.processors.standard.EvaluateXQuery/index.html?rev=1794596&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.EvaluateXQuery/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.EvaluateXQuery/index.html
 Tue May  9 15:27:39 2017
@@ -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></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><tab
 le 
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
 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.</body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.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.2.0/org.apache.nifi.processors.standard.ExecuteProcess/index.html?rev=1794596&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.ExecuteProcess/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.2.0/org.apache.nifi.processors.standard.ExecuteProcess/index.html
 Tue May  9 15:27:39 2017
@@ -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, 
restricted</p><h3>Properties: </h3><p>In the list below, the names of required 
properties appear i
 n <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>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.</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="de
 fault-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"><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>Provides op
 erator the ability to execute arbitrary code assuming all permissions that 
NiFi has.</body></html>
\ No newline at end of file


Reply via email to