Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-record-serialization-services-nar/1.6.0/org.apache.nifi.json.JsonTreeReader/additionalDetails.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-record-serialization-services-nar/1.6.0/org.apache.nifi.json.JsonTreeReader/additionalDetails.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-record-serialization-services-nar/1.6.0/org.apache.nifi.json.JsonTreeReader/additionalDetails.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-record-serialization-services-nar/1.6.0/org.apache.nifi.json.JsonTreeReader/additionalDetails.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1,241 @@
+<!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>JsonTreeReader</title>
+        <link rel="stylesheet" href="../../../../../css/component-usage.css" 
type="text/css"/>
+    </head>
+
+    <body>
+        <p>
+               The JsonTreeReader Controller Service reads a JSON Object and 
creates a Record object for the entire
+               JSON Object tree. The Controller Service must be configured 
with a Schema that describes the structure
+               of the JSON data. If any field exists in the JSON that is not 
in the schema, that field will be skipped.
+               If the schema contains a field for which no JSON field exists, 
a null value will be used in the Record
+               (or the default value defined in the schema, if applicable).
+        </p>
+        
+        <p>
+               If the root element of the JSON is a JSON Array, each JSON 
Object within that array will be treated as
+               its own separate Record. If the root element is a JSON Object, 
the JSON will all be treated as a single
+               Record.
+        </p>
+
+
+               <h2>Schemas and Type Coercion</h2>
+               
+               <p>
+                       When a record is parsed from incoming data, it is 
separated into fields. Each of these fields is then looked up against the
+                       configured schema (by field name) in order to determine 
what the type of the data should be. If the field is not present in
+                       the schema, that field is omitted from the Record. If 
the field is found in the schema, the data type of the received data
+                       is compared against the data type specified in the 
schema. If the types match, the value of that field is used as-is. If the
+                       schema indicates that the field should be of a 
different type, then the Controller Service will attempt to coerce the data
+                       into the type specified by the schema. If the field 
cannot be coerced into the specified type, an Exception will be thrown.
+               </p>
+               
+               <p>
+                       The following rules apply when attempting to coerce a 
field value from one data type to another:
+               </p>
+                       
+               <ul>
+                       <li>Any data type can be coerced into a String 
type.</li>
+                       <li>Any numeric data type (Byte, Short, Int, Long, 
Float, Double) can be coerced into any other numeric data type.</li>
+                       <li>Any numeric value can be coerced into a Date, Time, 
or Timestamp type, by assuming that the Long value is the number of
+                       milliseconds since epoch (Midnight GMT, January 1, 
1970).</li>
+                       <li>A String value can be coerced into a Date, Time, or 
Timestamp type, if its format matches the configured "Date Format," "Time 
Format,"
+                               or "Timestamp Format."</li>
+                       <li>A String value can be coerced into a numeric value 
if the value is of the appropriate type. For example, the String value
+                               <code>8</code> can be coerced into any numeric 
type. However, the String value <code>8.2</code> can be coerced into a Double 
or Float
+                               type but not an Integer.</li>
+                       <li>A String value of "true" or "false" (regardless of 
case) can be coerced into a Boolean value.</li>
+                       <li>A String value that is not empty can be coerced 
into a Char type. If the String contains more than 1 character, the first 
character is used
+                               and the rest of the characters are ignored.</li>
+                       <li>Any "date/time" type (Date, Time, Timestamp) can be 
coerced into any other "date/time" type.</li>
+                       <li>Any "date/time" type can be coerced into a Long 
type, representing the number of milliseconds since epoch (Midnight GMT, 
January 1, 1970).</li>
+                       <li>Any "date/time" type can be coerced into a String. 
The format of the String is whatever DateFormat is configured for the 
corresponding
+                               property (Date Format, Time Format, Timestamp 
Format property). If no value is specified, then the value will be converted 
into a String
+                               representation of the number of milliseconds 
since epoch (Midnight GMT, January 1, 1970).</li>
+               </ul>
+               
+               <p>
+                       If none of the above rules apply when attempting to 
coerce a value from one data type to another, the coercion will fail and an 
Exception
+                       will be thrown.
+               </p>
+               
+               
+        <h2>Examples</h2>
+        
+        <p>
+               As an example, consider the following JSON is read:
+        </p>
+<code>
+<pre>
+[{
+    "id": 17,
+    "name": "John",
+    "child": {
+        "id": "1"
+    },
+    "dob": "10-29-1982"
+    "siblings": [
+        { "name": "Jeremy", "id": 4 },
+        { "name": "Julia", "id": 8}
+    ]
+  },
+  {
+    "id": 98,
+    "name": "Jane",
+    "child": {
+        "id": 2
+    },
+    "dob": "08-30-1984"
+    "gender": "F",
+    "siblingIds": [],
+    "siblings": []
+  }]
+</pre>
+</code>
+        
+        <p>
+               Also, consider that the schema that is configured for this JSON 
is as follows (assuming that the AvroSchemaRegistry
+               Controller Service is chosen to denote the Schema:
+        </p>
+
+<code>
+<pre>
+{
+       "namespace": "nifi",
+       "name": "person",
+       "type": "record",
+       "fields": [
+               { "name": "id", "type": "int" },
+               { "name": "name", "type": "string" },
+               { "name": "gender", "type": "string" },
+               { "name": "dob", "type": {
+                       "type": "int",
+                       "logicalType": "date"
+               }},
+               { "name": "siblings", "type": {
+                       "type": "array",
+                       "items": {
+                               "type": "record",
+                               "fields": [
+                                       { "name": "name", "type": "string" }
+                               ]
+                       }
+               }}
+       ]
+}
+</pre>
+</code>
+        
+        <p>
+               Let us also assume that this Controller Service is configured 
with the "Date Format" property set to "MM-dd-yyyy", as this
+               matches the date format used for our JSON data. This will 
result in the JSON creating two separate records, because the root
+               element is a JSON array with two elements.
+        </p>
+        
+        <p>
+               The first Record will consist of the following values:
+        </p>
+        
+        <table>
+               <tr>
+                       <th>Field Name</th>
+                       <th>Field Value</th>
+               </tr>
+               <tr>
+                       <td>id</td>
+                       <td>17</td>
+               </tr>
+               <tr>
+                       <td>name</td>
+                       <td>John</td>
+               </tr>
+               <tr>
+                       <td>gender</td>
+                       <td><i>null</i></td>
+               </tr>
+               <tr>
+                       <td>dob</td>
+                       <td>11-30-1983</td>
+               </tr>
+               <tr>
+                       <td>siblings</td>
+                       <td>
+                               <i>array with two elements, each of which is 
itself a Record:</i>
+                               <br />
+                               <table>
+                                       <tr>
+                                                       <th>Field Name</th>
+                                                       <th>Field Value</th>
+                                               </tr>
+                                               <tr>
+                                                       <td>name</td>
+                                                       <td>Jeremy</td>
+                                               </tr>
+                               </table>
+                               <br />
+                               <i>and:</i>
+                               <br />
+                               <table>
+                                               <tr>
+                                                       <th>Field Name</th>
+                                                       <th>Field Value</th>
+                                               </tr>
+                                               <tr>
+                                                       <td>name</td>
+                                                       <td>Julia</td>
+                                               </tr>
+                               </table>
+                       </td>
+               </tr>
+        </table>
+        
+        <p>
+               The second Record will consist of the following values:
+        </p>
+        
+               <table>
+                       <tr>
+                       <th>Field Name</th>
+                       <th>Field Value</th>
+               </tr>
+               <tr>
+                       <td>id</td>
+                       <td>98</td>
+               </tr>
+               <tr>
+                       <td>name</td>
+                       <td>Jane</td>
+               </tr>
+               <tr>
+                       <td>gender</td>
+                       <td>F</td>
+               </tr>
+               <tr>
+                       <td>dob</td>
+                       <td>08-30-1984</td>
+               </tr>
+               <tr>
+                       <td>siblings</td>
+                       <td><i>empty array</i></td>
+               </tr>
+        </table>
+        
+    </body>
+</html>

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-record-serialization-services-nar/1.6.0/org.apache.nifi.json.JsonTreeReader/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-record-serialization-services-nar/1.6.0/org.apache.nifi.json.JsonTreeReader/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-record-serialization-services-nar/1.6.0/org.apache.nifi.json.JsonTreeReader/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-record-serialization-services-nar/1.6.0/org.apache.nifi.json.JsonTreeReader/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>JsonTreeReader</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;">JsonTreeReader</h1><h2>Description: </h2><p>Parses JSON into individual 
Record objects. The Record that is produced will contain all top-level elements 
of the corresponding JSON Object. The root JSON element can be either a single 
element or an array of JSON elements, and each element in that array will be 
treated as a separate record. If the schema that is configured contains a field 
that is not present in the JSON, a null value will be used. If the JSON 
contains a field that is not present in the schema, that field will be skipped. 
See the Usage of the Controller Service for more information an
 d examples.</p><p><a href="additionalDetails.html">Additional 
Details...</a></p><h3>Tags: </h3><p>json, tree, record, reader, 
parser</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>Schema Access Strategy</strong></td><td 
id="default-value">schema-name</td><td id="allowable-values"><ul><li>Use 
'Schema Name' Property <img src="../../../../../html/images/iconInfo.png" 
alt="The name of the Schema to use is specified by the 'Schema Name' Property. 
The value of this property is used to lookup the Schema in the configured 
Schema Registry service." title="The na
 me of the Schema to use is specified by the 'Schema Name' Property. The value 
of this property is used to lookup the Schema in the configured Schema Registry 
service."></img></li><li>Use 'Schema Text' Property <img 
src="../../../../../html/images/iconInfo.png" alt="The text of the Schema 
itself is specified by the 'Schema Text' Property. The value of this property 
must be a valid Avro Schema. If Expression Language is used, the value of the 
'Schema Text' property must be valid after substituting the expressions." 
title="The text of the Schema itself is specified by the 'Schema Text' 
Property. The value of this property must be a valid Avro Schema. If Expression 
Language is used, the value of the 'Schema Text' property must be valid after 
substituting the expressions."></img></li><li>HWX Schema Reference Attributes 
<img src="../../../../../html/images/iconInfo.png" alt="The FlowFile contains 3 
Attributes that will be used to lookup a Schema from the configured Schema 
Registry: 'schem
 a.identifier', 'schema.version', and 'schema.protocol.version'" title="The 
FlowFile contains 3 Attributes that will be used to lookup a Schema from the 
configured Schema Registry: 'schema.identifier', 'schema.version', and 
'schema.protocol.version'"></img></li><li>HWX Content-Encoded Schema Reference 
<img src="../../../../../html/images/iconInfo.png" alt="The content of the 
FlowFile contains a reference to a schema in the Schema Registry service. The 
reference is encoded as a single byte indicating the 'protocol version', 
followed by 8 bytes indicating the schema identifier, and finally 4 bytes 
indicating the schema version, as per the Hortonworks Schema Registry 
serializers and deserializers, found at 
https://github.com/hortonworks/registry"; title="The content of the FlowFile 
contains a reference to a schema in the Schema Registry service. The reference 
is encoded as a single byte indicating the 'protocol version', followed by 8 
bytes indicating the schema identifier, and finally 4
  bytes indicating the schema version, as per the Hortonworks Schema Registry 
serializers and deserializers, found at 
https://github.com/hortonworks/registry";></img></li><li>Confluent 
Content-Encoded Schema Reference <img 
src="../../../../../html/images/iconInfo.png" alt="The content of the FlowFile 
contains a reference to a schema in the Schema Registry service. The reference 
is encoded as a single 'Magic Byte' followed by 4 bytes representing the 
identifier of the schema, as outlined at 
http://docs.confluent.io/current/schema-registry/docs/serializer-formatter.html.
 This is based on version 3.2.x of the Confluent Schema Registry." title="The 
content of the FlowFile contains a reference to a schema in the Schema Registry 
service. The reference is encoded as a single 'Magic Byte' followed by 4 bytes 
representing the identifier of the schema, as outlined at 
http://docs.confluent.io/current/schema-registry/docs/serializer-formatter.html.
 This is based on version 3.2.x of the Confluent 
 Schema Registry."></img></li></ul></td><td id="description">Specifies how to 
obtain the schema that is to be used for interpreting the 
data.</td></tr><tr><td id="name">Schema Registry</td><td 
id="default-value"></td><td id="allowable-values"><strong>Controller Service 
API: </strong><br/>SchemaRegistry<br/><strong>Implementations: </strong><a 
href="../../../nifi-registry-nar/1.6.0/org.apache.nifi.schemaregistry.services.AvroSchemaRegistry/index.html">AvroSchemaRegistry</a><br/><a
 
href="../../../nifi-confluent-platform-nar/1.6.0/org.apache.nifi.confluent.schemaregistry.ConfluentSchemaRegistry/index.html">ConfluentSchemaRegistry</a><br/><a
 
href="../../../nifi-hwx-schema-registry-nar/1.6.0/org.apache.nifi.schemaregistry.hortonworks.HortonworksSchemaRegistry/index.html">HortonworksSchemaRegistry</a></td><td
 id="description">Specifies the Controller Service to use for the Schema 
Registry</td></tr><tr><td id="name">Schema Name</td><td 
id="default-value">${schema.name}</td><td id="allowable
 -values"></td><td id="description">Specifies the name of the schema to lookup 
in the Schema Registry property<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Schema Version</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Specifies the version of the schema to lookup in the Schema 
Registry. If not specified then the latest version of the schema will be 
retrieved.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Schema Branch</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Specifies the name of the branch to use when looking up the 
schema in the Schema Registry property. If the chosen Schema Registry does not 
support branching, this value will be ignored.<br/><strong>Supports Expression 
Language: true</strong></td></tr><tr><td id="name">Schema Text</td><td 
id="default-value">${avro.schema}</td><td id="allowable-values"></td><td 
id="description">T
 he text of an Avro-formatted Schema<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Date Format</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Specifies the format to use when reading/writing Date fields. 
If not specified, Date fields will be assumed to be number of milliseconds 
since epoch (Midnight, Jan 1, 1970 GMT). If specified, the value must match the 
Java Simple Date Format (for example, MM/dd/yyyy for a two-digit month, 
followed by a two-digit day, followed by a four-digit year, all separated by 
'/' characters, as in 01/01/2017).</td></tr><tr><td id="name">Time 
Format</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">Specifies the format to use when reading/writing Time fields. 
If not specified, Time fields will be assumed to be number of milliseconds 
since epoch (Midnight, Jan 1, 1970 GMT). If specified, the value must match the 
Java Simple Date Format (for example, HH:
 mm:ss for a two-digit hour in 24-hour format, followed by a two-digit minute, 
followed by a two-digit second, all separated by ':' characters, as in 
18:04:15).</td></tr><tr><td id="name">Timestamp Format</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Specifies the format to use when reading/writing Timestamp 
fields. If not specified, Timestamp fields will be assumed to be number of 
milliseconds since epoch (Midnight, Jan 1, 1970 GMT). If specified, the value 
must match the Java Simple Date Format (for example, MM/dd/yyyy HH:mm:ss for a 
two-digit month, followed by a two-digit day, followed by a four-digit year, 
all separated by '/' characters; and then followed by a two-digit hour in 
24-hour format, followed by a two-digit minute, followed by a two-digit second, 
all separated by ':' characters, as in 01/01/2017 
18:04:15).</td></tr></table><h3>State management: </h3>This component does not 
store state.<h3>Restricted: </h3>This component is not res
 tricted.<h3>System Resource Considerations:</h3>None specified.<h3>See 
Also:</h3><p><a 
href="../org.apache.nifi.json.JsonPathReader/index.html">JsonPathReader</a></p></body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-record-serialization-services-nar/1.6.0/org.apache.nifi.text.FreeFormTextRecordSetWriter/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-record-serialization-services-nar/1.6.0/org.apache.nifi.text.FreeFormTextRecordSetWriter/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-record-serialization-services-nar/1.6.0/org.apache.nifi.text.FreeFormTextRecordSetWriter/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-record-serialization-services-nar/1.6.0/org.apache.nifi.text.FreeFormTextRecordSetWriter/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>FreeFormTextRecordSetWriter</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;">FreeFormTextRecordSetWriter</h1><h2>Description: </h2><p>Writes the 
contents of a RecordSet as free-form text. The configured text is able to make 
use of the Expression Language to reference each of the fields that are 
available in a Record. Each record in the RecordSet will be separated by a 
single newline character.</p><h3>Tags: </h3><p>text, freeform, expression, 
language, el, record, recordset, resultset, writer, 
serialize</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 consider
 ed 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>Text</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The text to use when writing 
the results. This property will evaluate the Expression Language using any of 
the fields available in a Record.<br/><strong>Supports Expression Language: 
true</strong></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 to use when writing the data to the 
FlowFile</td></tr></table><h3>State management: </h3>This component does not 
store state.<h3>Restricted: </h3>This component is not restricted.<h3>System 
Resource Consideratio
 ns:</h3>None specified.</body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-redis-nar/1.6.0/org.apache.nifi.redis.service.RedisConnectionPoolService/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-redis-nar/1.6.0/org.apache.nifi.redis.service.RedisConnectionPoolService/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-redis-nar/1.6.0/org.apache.nifi.redis.service.RedisConnectionPoolService/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-redis-nar/1.6.0/org.apache.nifi.redis.service.RedisConnectionPoolService/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>RedisConnectionPoolService</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;">RedisConnectionPoolService</h1><h2>Description: </h2><p>A service that 
provides connections to Redis.</p><h3>Tags: </h3><p>redis, 
cache</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>Redis 
Mode</strong></td><td id="default-value">Standalone</td><td 
id="allowable-values"><ul><li>Standalone <img 
src="../../../../../html/images/iconInfo.png" alt="A single standalone Redis 
instance." title="A single standalone Redis instance."></img></li><li>Sentinel 
<img src="../../../../../html/images/iconInfo.png" alt="Redis Sentinel which 
provides high-availability. Described further at 
https://redis.io/topics/sentinel"; title="Redis Sentinel which provides 
high-availability. Described further at 
https://redis.io/topics/sentinel";></img></li><li>Cluster <img 
src="../../../../../html/images/iconInfo.png" alt="Clustered Redis which 
provides sharding and replication. Described further at https:/
 /redis.io/topics/cluster-spec" title="Clustered Redis which provides sharding 
and replication. Described further at 
https://redis.io/topics/cluster-spec";></img></li></ul></td><td 
id="description">The type of Redis being communicated with - standalone, 
sentinel, or clustered.</td></tr><tr><td id="name"><strong>Connection 
String</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The connection string for 
Redis. In a standalone instance this value will be of the form hostname:port. 
In a sentinel instance this value will be the comma-separated list of 
sentinels, such as host1:port1,host2:port2,host3:port3. In a clustered instance 
this value will be the comma-separated list of cluster masters, such as 
host1:port,host2:port,host3:port.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Database 
Index</strong></td><td id="default-value">0</td><td 
id="allowable-values"></td><td id="description">The database in
 dex to be used by connections created from this connection pool. See the 
databases property in redis.conf, by default databases 0-15 will be 
available.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Communication 
Timeout</strong></td><td id="default-value">10 seconds</td><td 
id="allowable-values"></td><td id="description">The timeout to use when 
attempting to communicate with Redis.</td></tr><tr><td 
id="name"><strong>Cluster Max Redirects</strong></td><td 
id="default-value">5</td><td id="allowable-values"></td><td 
id="description">The maximum number of redirects that can be performed when 
clustered.</td></tr><tr><td id="name">Sentinel Master</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
name of the sentinel master, require when Mode is set to 
Sentinel<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">The password used to authenticate to the Redis 
 >server. See the requirepass property in redis.conf.<br/><strong>Sensitive 
 >Property: true</strong><br/><strong>Supports Expression Language: 
 >true</strong></td></tr><tr><td id="name"><strong>Pool - Max 
 >Total</strong></td><td id="default-value">8</td><td 
 >id="allowable-values"></td><td id="description">The maximum number of 
 >connections that can be allocated by the pool (checked out to clients, or 
 >idle awaiting checkout). A negative value indicates that there is no 
 >limit.</td></tr><tr><td id="name"><strong>Pool - Max Idle</strong></td><td 
 >id="default-value">8</td><td id="allowable-values"></td><td 
 >id="description">The maximum number of idle connections that can be held in 
 >the pool, or a negative value if there is no limit.</td></tr><tr><td 
 >id="name"><strong>Pool - Min Idle</strong></td><td 
 >id="default-value">0</td><td id="allowable-values"></td><td 
 >id="description">The target for the minimum number of idle connecti
 ons to maintain in the pool. If the configured value of Min Idle is greater 
than the configured value for Max Idle, then the value of Max Idle will be used 
instead.</td></tr><tr><td id="name"><strong>Pool - Block When 
Exhausted</strong></td><td id="default-value">true</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Whether or not clients should block and wait when trying to 
obtain a connection from the pool when the pool has no available connections. 
Setting this to false means an error will occur immediately when a client 
requests a connection and none are available.</td></tr><tr><td 
id="name"><strong>Pool - Max Wait Time</strong></td><td id="default-value">10 
seconds</td><td id="allowable-values"></td><td id="description">The amount of 
time to wait for an available connection when Block When Exhausted is set to 
true.</td></tr><tr><td id="name"><strong>Pool - Min Evictable Idle 
Time</strong></td><td id="default-value">60 seconds</td><td i
 d="allowable-values"></td><td id="description">The minimum amount of time an 
object may sit idle in the pool before it is eligible for 
eviction.</td></tr><tr><td id="name"><strong>Pool - Time Between Eviction 
Runs</strong></td><td id="default-value">30 seconds</td><td 
id="allowable-values"></td><td id="description">The amount of time between 
attempting to evict idle connections from the pool.</td></tr><tr><td 
id="name"><strong>Pool - Num Tests Per Eviction Run</strong></td><td 
id="default-value">-1</td><td id="allowable-values"></td><td 
id="description">The number of connections to tests per eviction attempt. A 
negative value indicates to test all connections.</td></tr><tr><td 
id="name"><strong>Pool - Test On Create</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 or not connections should be tested upon 
creation.</td></tr><tr><td id="name"><strong>Pool - Test On 
Borrow</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 or not connections should be tested upon borrowing 
from the pool.</td></tr><tr><td id="name"><strong>Pool - Test On 
Return</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 or not connections should be tested upon returning to 
the pool.</td></tr><tr><td id="name"><strong>Pool - Test While 
Idle</strong></td><td id="default-value">true</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Whether or not connections should be tested while 
idle.</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-redis-nar/1.6.0/org.apache.nifi.redis.service.RedisDistributedMapCacheClientService/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-redis-nar/1.6.0/org.apache.nifi.redis.service.RedisDistributedMapCacheClientService/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-redis-nar/1.6.0/org.apache.nifi.redis.service.RedisDistributedMapCacheClientService/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-redis-nar/1.6.0/org.apache.nifi.redis.service.RedisDistributedMapCacheClientService/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>RedisDistributedMapCacheClientService</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;">RedisDistributedMapCacheClientService</h1><h2>Description: </h2><p>An 
implementation of DistributedMapCacheClient that uses Redis as the backing 
cache. This service relies on the WATCH, MULTI, and EXEC commands in Redis, 
which are not fully supported when Redis is clustered. As a result, this 
service can only be used with a Redis Connection Pool that is configured for 
standalone or sentinel mode. Sentinel mode can be used to provide 
high-availability configurations.</p><h3>Tags: </h3><p>redis, distributed, 
cache, map</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.</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>Redis Connection Pool</strong></td><td 
id="default-value"></td><td id="allowable-values"><strong>Controller Service 
API: </strong><br/>RedisConnectionPool<br/><strong>Implementation: </strong><a 
href="../org.apache.nifi.redis.service.RedisConnectionPoolService/index.html">RedisConnectionPoolService</a></td><td
 id="description">No Description Provided.</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-registry-nar/1.6.0/org.apache.nifi.schemaregistry.services.AvroSchemaRegistry/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-registry-nar/1.6.0/org.apache.nifi.schemaregistry.services.AvroSchemaRegistry/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-registry-nar/1.6.0/org.apache.nifi.schemaregistry.services.AvroSchemaRegistry/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-registry-nar/1.6.0/org.apache.nifi.schemaregistry.services.AvroSchemaRegistry/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>AvroSchemaRegistry</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;">AvroSchemaRegistry</h1><h2>Description: </h2><p>Provides a service for 
registering and accessing schemas. You can register a schema as a dynamic 
property where 'name' represents the schema name and 'value' represents the 
textual representation of the actual schema following the syntax and semantics 
of Avro's Schema format.</p><h3>Tags: </h3><p>schema, registry, avro, json, 
csv</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>Validate Field 
 >Names</strong></td><td id="default-value">true</td><td 
 >id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
 >id="description">Whether or not to validate the field names in the Avro 
 >schema based on Avro naming rules. If set to true, all field names must be 
 >valid Avro names, which must begin with [A-Za-z_], and subsequently contain 
 >only [A-Za-z0-9_]. If set to false, no validation will be performed on the 
 >field names.</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-rethinkdb-nar/1.6.0/org.apache.nifi.processors.rethinkdb.DeleteRethinkDB/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-rethinkdb-nar/1.6.0/org.apache.nifi.processors.rethinkdb.DeleteRethinkDB/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-rethinkdb-nar/1.6.0/org.apache.nifi.processors.rethinkdb.DeleteRethinkDB/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-rethinkdb-nar/1.6.0/org.apache.nifi.processors.rethinkdb.DeleteRethinkDB/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>DeleteRethinkDB</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;">DeleteRethinkDB</h1><h2>Description: </h2><p>Processor to remove a JSON 
document from RethinkDB (https://www.rethinkdb.com/) using the document 
id.</p><h3>Tags: </h3><p>rethinkdb, delete, remove</p><h3>Properties: 
</h3><p>In the list below, the names of required properties appear in 
<strong>bold</strong>. Any other properties (not in bold) are considered 
optional. The table also indicates any default values, whether a property 
supports the <a href="../../../../../html/expression-language-guide.html">NiFi 
Expression Language</a>, and whether a property is considered "sensitive", 
meaning that its 
 value will be encrypted. Before entering a value in a sensitive property, 
ensure that the <strong>nifi.properties</strong> file has an entry for the 
property <strong>nifi.sensitive.props.key</strong>.</p><table 
id="properties"><tr><th>Name</th><th>Default Value</th><th>Allowable 
Values</th><th>Description</th></tr><tr><td id="name"><strong>DB 
Name</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">RethinkDB database to connect 
to</td></tr><tr><td id="name"><strong>Hostname</strong></td><td 
id="default-value">localhost</td><td id="allowable-values"></td><td 
id="description">RethinkDB hostname</td></tr><tr><td id="name"><strong>DB 
Port</strong></td><td id="default-value">28015</td><td 
id="allowable-values"></td><td id="description">RethinkDB database port to 
connect to</td></tr><tr><td id="name">Username</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Username for accessing RethinkDB</td></tr><tr><td id="nam
 e">Password</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">Password for user<br/><strong>Sensitive Property: 
true</strong></td></tr><tr><td id="name"><strong>Table name</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">RethinkDB table to connect to</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">Specifies the character set of the document 
data.<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
id="name"><strong>Document Identifier</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">A 
FlowFile attribute, or attribute expression used for determining RethinkDB key 
for the Flow File content<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Return deleted 
value</strong></td><td id="default-value">true</td><td
  id="allowable-values"><ul><li>True <img 
src="../../../../../html/images/iconInfo.png" alt="Return changed document" 
title="Return changed document"></img></li><li>False <img 
src="../../../../../html/images/iconInfo.png" alt="Do not return changed 
document" title="Do not return changed document"></img></li></ul></td><td 
id="description">Return old value which were deleted<br/><strong>Supports 
Expression Language: true</strong></td></tr><tr><td id="name"><strong>Durablity 
of documents</strong></td><td id="default-value">hard</td><td 
id="allowable-values"><ul><li>Hard <img 
src="../../../../../html/images/iconInfo.png" alt="Save change to disk before 
ack" title="Save change to disk before ack"></img></li><li>Soft <img 
src="../../../../../html/images/iconInfo.png" alt="Don't save changes to disk 
before ack" title="Don't save changes to disk before 
ack"></img></li></ul></td><td id="description">Durability of documents being 
inserted<br/><strong>Supports Expression Language: true</strong>
 </td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>Sucessful
 FlowFiles are routed to this 
relationship</td></tr><tr><td>not_found</td><td>Document not found are routed 
to this relationship</td></tr><tr><td>failure</td><td>Failed 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>rethinkdb.error.message</td><td>RethinkDB
 error message</td></tr><tr><td>rethinkdb.delete.errors</td><td>Error count 
while delete documents</td></tr><tr><td>rethinkdb.delete.deleted</td><td>Number 
of documents deleted</td></tr><tr><td>rethinkdb.delete.inserted</td><td>Number 
of documents inserted</td></tr><tr><td>rethinkdb.delete.replaced</td><td>Number 
of documents replaced</td></tr><tr><td>rethinkdb.delete.skipped</td><td>Number 
of documents skipped</td></tr><tr><td>ret
 hinkdb.delete.unchanged</td><td>Number of documents unchanged since they 
already existed</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.rethinkdb.PutRethinkDB/index.html">PutRethinkDB</a>,
 <a 
href="../org.apache.nifi.processors.rethinkdb.GetRethinkDB/index.html">GetRethinkDB</a></p></body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-rethinkdb-nar/1.6.0/org.apache.nifi.processors.rethinkdb.GetRethinkDB/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-rethinkdb-nar/1.6.0/org.apache.nifi.processors.rethinkdb.GetRethinkDB/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-rethinkdb-nar/1.6.0/org.apache.nifi.processors.rethinkdb.GetRethinkDB/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-rethinkdb-nar/1.6.0/org.apache.nifi.processors.rethinkdb.GetRethinkDB/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>GetRethinkDB</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;">GetRethinkDB</h1><h2>Description: </h2><p>Processor to get a JSON 
document from RethinkDB (https://www.rethinkdb.com/) using the document id. The 
FlowFile will contain the retrieved document</p><h3>Tags: </h3><p>rethinkdb, 
get, read, 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, 
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>DB 
Name</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">RethinkDB database to connect 
to</td></tr><tr><td id="name"><strong>Hostname</strong></td><td 
id="default-value">localhost</td><td id="allowable-values"></td><td 
id="description">RethinkDB hostname</td></tr><tr><td id="name"><strong>DB 
Port</strong></td><td id="default-value">28015</td><td 
id="allowable-values"></td><td id="description">RethinkDB database port to 
connect to</td></tr><tr><td id="name">Username</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Username for ac
 cessing RethinkDB</td></tr><tr><td id="name">Password</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Password for user<br/><strong>Sensitive Property: 
true</strong></td></tr><tr><td id="name"><strong>Table name</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">RethinkDB table to connect to</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">Specifies the character set of the document 
data.<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
id="name"><strong>Document Identifier</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">A 
FlowFile attribute, or attribute expression used for determining RethinkDB key 
for the Flow File content<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Read Mode</strong></td><td 
 id="default-value">single</td><td id="allowable-values"><ul><li>Single <img 
src="../../../../../html/images/iconInfo.png" alt="Read values from memory from 
primary replica (Default)" title="Read values from memory from primary replica 
(Default)"></img></li><li>Majority <img 
src="../../../../../html/images/iconInfo.png" alt="Read values committed to 
disk on majority of replicas" title="Read values committed to disk on majority 
of replicas"></img></li><li>Outdated <img 
src="../../../../../html/images/iconInfo.png" alt="Read values from memory from 
an arbitrary replica " title="Read values from memory from an arbitrary replica 
"></img></li></ul></td><td id="description">Read mode used for 
consistency<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Max size of 
documents</strong></td><td id="default-value">1 MB</td><td 
id="allowable-values"></td><td id="description">Maximum size of documents 
allowed to be posted in one batch</td></tr></table><h3
 >Relationships: </h3><table 
 >id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>Sucessful
 > FlowFiles are routed to this 
 >relationship</td></tr><tr><td>not_found</td><td>Document not found are routed 
 >to this relationship</td></tr><tr><td>failure</td><td>Failed 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>rethinkdb.error.message</td><td>RethinkDB
 > error message</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.rethinkdb.PutRethinkDB/index.html">PutRethinkDB</a>,
 > <a href="../org.apache.nifi.processors.rethinkdb.DeleteRethink
 DB/index.html">DeleteRethinkDB</a></p></body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-rethinkdb-nar/1.6.0/org.apache.nifi.processors.rethinkdb.PutRethinkDB/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-rethinkdb-nar/1.6.0/org.apache.nifi.processors.rethinkdb.PutRethinkDB/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-rethinkdb-nar/1.6.0/org.apache.nifi.processors.rethinkdb.PutRethinkDB/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-rethinkdb-nar/1.6.0/org.apache.nifi.processors.rethinkdb.PutRethinkDB/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>PutRethinkDB</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;">PutRethinkDB</h1><h2>Description: </h2><p>Processor to write the JSON 
content of a FlowFile to RethinkDB (https://www.rethinkdb.com/). The flow file 
should contain either JSON Object an array of JSON documents</p><h3>Tags: 
</h3><p>rethinkdb, stream, insert, update, write, put</p><h3>Properties: 
</h3><p>In the list below, the names of required properties appear in 
<strong>bold</strong>. Any other properties (not in bold) are considered 
optional. The table also indicates any default values, whether a property 
supports the <a href="../../../../../html/expression-language-guide.html">NiFi 
Expression La
 nguage</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>DB 
Name</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">RethinkDB database to connect 
to</td></tr><tr><td id="name"><strong>Hostname</strong></td><td 
id="default-value">localhost</td><td id="allowable-values"></td><td 
id="description">RethinkDB hostname</td></tr><tr><td id="name"><strong>DB 
Port</strong></td><td id="default-value">28015</td><td 
id="allowable-values"></td><td id="description">RethinkDB database port to 
connect to</td></tr><tr><td id="name">Username</td><td 
id="default-value"></td><td id="allowable-values"></td
 ><td id="description">Username for accessing RethinkDB</td></tr><tr><td 
 >id="name">Password</td><td id="default-value"></td><td 
 >id="allowable-values"></td><td id="description">Password for 
 >user<br/><strong>Sensitive Property: true</strong></td></tr><tr><td 
 >id="name"><strong>Table name</strong></td><td id="default-value"></td><td 
 >id="allowable-values"></td><td id="description">RethinkDB table to connect 
 >to</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">Specifies the character set of the document 
 >data.<br/><strong>Supports Expression Language: 
 >true</strong></td></tr><tr><td id="name"><strong>Conflict 
 >strategy</strong></td><td id="default-value">update</td><td 
 >id="allowable-values"><ul><li>Update <img 
 >src="../../../../../html/images/iconInfo.png" alt="Update the document having 
 >same id with new values" title="Update the document having same id with new 
 >values"></img></li><li>Replace <img 
 src="../../../../../html/images/iconInfo.png" alt="Replace the document with 
having same id new document" title="Replace the document with having same id 
new document"></img></li><li>Error <img 
src="../../../../../html/images/iconInfo.png" alt="Return error if the document 
with same id exists" title="Return error if the document with same id 
exists"></img></li></ul></td><td id="description">Conflict strategy to be used 
in case of inserting existing document.<br/><strong>Supports Expression 
Language: true</strong></td></tr><tr><td id="name"><strong>Durablity of 
documents</strong></td><td id="default-value">hard</td><td 
id="allowable-values"><ul><li>Hard <img 
src="../../../../../html/images/iconInfo.png" alt="Save change to disk before 
ack" title="Save change to disk before ack"></img></li><li>Soft <img 
src="../../../../../html/images/iconInfo.png" alt="Don't save changes to disk 
before ack" title="Don't save changes to disk before 
ack"></img></li></ul></td><td id="description">Durabi
 lity of documents being inserted<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Max size of 
documents</strong></td><td id="default-value">1 MB</td><td 
id="allowable-values"></td><td id="description">Maximum size of documents 
allowed to be posted in one batch</td></tr></table><h3>Relationships: 
</h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>Sucessful
 FlowFiles are routed to this 
relationship</td></tr><tr><td>failure</td><td>Failed 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>rethinkdb.error.message</td><td>RethinkDB
 error message</td></tr><tr><td>rethinkdb.insert.errors</td><td>Error count 
while inserting 
documents</td></tr><tr><td>rethinkdb.insert.deleted</td><td>Number of documents 
deleted</td></tr><tr><td>rethinkdb.insert.gener
 ated_keys</td><td>Keys generated on inserting 
documents</td></tr><tr><td>rethinkdb.insert.inserted</td><td>Number of 
documents inserted</td></tr><tr><td>rethinkdb.insert.replaced</td><td>Number of 
documents replaced</td></tr><tr><td>rethinkdb.insert.skipped</td><td>Number of 
documents skipped because they already 
existed</td></tr><tr><td>rethinkdb.insert.unchanged</td><td>Number of documents 
unchanged since they already 
existed</td></tr><tr><td>rethinkdb.insert.first_error</td><td>First error while 
inserting documents</td></tr><tr><td>rethinkdb.insert.warnings</td><td>Warning 
message in case of large number of ids being returned on 
insertion</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.rethinkdb.GetRethinkD
 B/index.html">GetRethinkDB</a>, <a 
href="../org.apache.nifi.processors.rethinkdb.DeleteRethinkDB/index.html">DeleteRethinkDB</a></p></body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-riemann-nar/1.6.0/org.apache.nifi.processors.riemann.PutRiemann/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-riemann-nar/1.6.0/org.apache.nifi.processors.riemann.PutRiemann/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-riemann-nar/1.6.0/org.apache.nifi.processors.riemann.PutRiemann/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-riemann-nar/1.6.0/org.apache.nifi.processors.riemann.PutRiemann/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>PutRiemann</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;">PutRiemann</h1><h2>Description: </h2><p>Send events to Riemann 
(http://riemann.io) when FlowFiles pass through this processor. You can use 
events to notify Riemann that a FlowFile passed through, or you can attach a 
more meaningful metric, such as, the time a FlowFile took to get to this 
processor. All attributes attached to events support the NiFi Expression 
Language.</p><h3>Tags: </h3><p>riemann, monitoring, metrics</p><h3>Properties: 
</h3><p>In the list below, the names of required properties appear in 
<strong>bold</strong>. Any other properties (not in bold) are considered 
optional. The table als
 o 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>Riemann Address</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Hostname of Riemann 
server</td></tr><tr><td id="name"><strong>Riemann Port</strong></td><td 
id="default-value">5555</td><td id="allowable-values"></td><td 
id="description">Port that Riemann is listening on</td></tr><tr><td 
id="name"><strong>Transport Protocol</strong></td><td 
id="default-value">TCP</td><td 
id="allowable-values"><ul><li>TCP</li><li>UDP</li></ul></td><td 
id="description">Transport protocol to speak to Riemann in</td></tr><tr><td 
id="name"><strong>Timeout</strong></td><td id="default-value">1000</td><td 
id="allowable-values"></td><td id="description">Timeout in millis
 econds when writing events to Riemann</td></tr><tr><td id="name">Batch 
Size</td><td id="default-value">100</td><td id="allowable-values"></td><td 
id="description">Batch size for incoming FlowFiles</td></tr><tr><td 
id="name">Description</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Description associated to the 
event<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
id="name">Service</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Name of service associated to 
this event (e.g. FTP File Fetched)<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">State</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">State of service associated to this event in string form (e.g. 
ok, warning, foo)<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Metric</td><td 
id="default-value"></td><td id="allowable-values"
 ></td><td id="description">Floating point number associated to this 
 >event<br/><strong>Supports Expression Language: 
 >true</strong></td></tr><tr><td id="name">TTL</td><td 
 >id="default-value"></td><td id="allowable-values"></td><td 
 >id="description">Floating point value in seconds until Riemann considers this 
 >event as "expired"<br/><strong>Supports Expression Language: 
 >true</strong></td></tr><tr><td id="name">Tags</td><td 
 >id="default-value"></td><td id="allowable-values"></td><td 
 >id="description">Comma separated list of tags associated to the 
 >event<br/><strong>Supports Expression Language: 
 >true</strong></td></tr><tr><td id="name">Host</td><td 
 >id="default-value">${hostname()}</td><td id="allowable-values"></td><td 
 >id="description">A hostname associated to this event (e.g. 
 >nifi-app1)<br/><strong>Supports Expression Language: 
 >true</strong></td></tr><tr><td id="name">Time</td><td 
 >id="default-value"></td><td id="allowable-values"></td><td 
 >id="description">Time of event in unix epoch seconds (
 long), default: (current time)<br/><strong>Supports Expression Language: 
true</strong></td></tr></table><h3>Dynamic Properties: </h3><p>Dynamic 
Properties allow the user to specify both the name and value of a 
property.<table 
id="dynamic-properties"><tr><th>Name</th><th>Value</th><th>Description</th></tr><tr><td
 id="name">Custom Event Attribute</td><td id="value">Any value or 
expression</td><td>These values will be attached to the Riemann event as a 
custom attribute<br/><strong>Supports Expression Language: 
true</strong></td></tr></table></p><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>Metrics
 successfully written to Riemann</td></tr><tr><td>failure</td><td>Metrics which 
failed to write to Riemann</td></tr></table><h3>Reads Attributes: </h3>None 
specified.<h3>Writes Attributes: </h3>None specified.<h3>State management: 
</h3>This component does not store state.<h3>Restricted: </h3>This component is 
not restricted.
 <h3>Input requirement: </h3>This component requires an incoming 
relationship.<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-scripting-nar/1.6.0/org.apache.nifi.lookup.script.ScriptedLookupService/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-scripting-nar/1.6.0/org.apache.nifi.lookup.script.ScriptedLookupService/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-scripting-nar/1.6.0/org.apache.nifi.lookup.script.ScriptedLookupService/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-scripting-nar/1.6.0/org.apache.nifi.lookup.script.ScriptedLookupService/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ScriptedLookupService</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;">ScriptedLookupService</h1><h2>Description: </h2><p>Allows the user to 
provide a scripted LookupService instance in order to enrich records from an 
incoming flow file.</p><h3>Tags: </h3><p>lookup, record, script, invoke, 
groovy, python, jython, jruby, ruby, javascript, js, lua, 
luaj</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>Script 
 >Engine</strong></td><td id="default-value">Clojure</td><td 
 >id="allowable-values"><ul><li>Clojure</li><li>ECMAScript</li><li>Groovy</li><li>lua</li><li>python</li><li>ruby</li></ul></td><td
 > id="description">The engine to execute scripts</td></tr><tr><td 
 >id="name">Script File</td><td id="default-value"></td><td 
 >id="allowable-values"></td><td id="description">Path to script file to 
 >execute. Only one of Script File or Script Body may be 
 >used<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
 >id="name">Script Body</td><td id="default-value"></td><td 
 >id="allowable-values"></td><td id="description">Body of script to execute. 
 >Only one of Script File or Script Body may be used</td></tr><tr><td 
 >id="name">Module Directory</td><td id="default-value"></td><td 
 >id="allowable-values"></td><td id="desc
 ription">Comma-separated list of paths to files and/or directories which 
contain modules required by the script.<br/><strong>Supports Expression 
Language: true</strong></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>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-scripting-nar/1.6.0/org.apache.nifi.processors.script.ExecuteScript/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-scripting-nar/1.6.0/org.apache.nifi.processors.script.ExecuteScript/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-scripting-nar/1.6.0/org.apache.nifi.processors.script.ExecuteScript/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-scripting-nar/1.6.0/org.apache.nifi.processors.script.ExecuteScript/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ExecuteScript</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;">ExecuteScript</h1><h2>Description: </h2><p>Experimental - Executes a 
script given the flow file and a process session.  The script is responsible 
for handling the incoming flow file (transfer to SUCCESS or remove, e.g.) as 
well as any flow files created by the script. If the handling is incomplete or 
incorrect, the session will be rolled back. Experimental: Impact of sustained 
usage not yet verified.</p><h3>Tags: </h3><p>script, execute, groovy, python, 
jython, jruby, ruby, javascript, js, lua, luaj, clojure</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>Script Engine</strong></td><td 
id="default-value">Clojure</td><td 
id="allowable-values"><ul><li>Clojure</li><li>ECMAScript</li><li>Groovy</li><li>lua</li><li>python</li><li>ruby</li></ul></td><td
 id="description">The engine to execute scripts</td></tr><tr><td 
id="name">Script File</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Path to script file to execute. 
Only one of Script File or Script Body may be used<br/><strong>Supports 
Expression Language: true</strong></td></tr><tr><td id="name">Script 
Body</td><td id="default-value"></td><td id="allowable-values">
 </td><td id="description">Body of script to execute. Only one of Script File 
or Script Body may be used</td></tr><tr><td id="name">Module Directory</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Comma-separated list of paths to files and/or directories 
which contain modules required by the script.<br/><strong>Supports Expression 
Language: true</strong></td></tr></table><h3>Dynamic Properties: 
</h3><p>Dynamic Properties allow the user to specify both the name and value of 
a property.<table 
id="dynamic-properties"><tr><th>Name</th><th>Value</th><th>Description</th></tr><tr><td
 id="name">A script engine property to update</td><td id="value">The value to 
set it to</td><td>Updates a script engine property specified by the Dynamic 
Property's key with the value specified by the Dynamic Property's 
value<br/><strong>Supports Expression Language: 
true</strong></td></tr></table></p><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Descr
 iption</th></tr><tr><td>success</td><td>FlowFiles that were successfully 
processed</td></tr><tr><td>failure</td><td>FlowFiles that failed to be 
processed</td></tr></table><h3>Reads Attributes: </h3>None specified.<h3>Writes 
Attributes: </h3>None specified.<h3>State management: </h3><table 
id="stateful"><tr><th>Scope</th><th>Description</th></tr><tr><td>LOCAL, 
CLUSTER</td><td>Scripts can store and retrieve state using the State Management 
APIs. Consult the State Manager section of the Developer's Guide for more 
details.</td></tr></table><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>System Resource Considerations:</h3>None 
specified.<h3>See Also:</h3><p><a 
href="../org.apache.nifi.processors.script.InvokeScriptedProcessor/index.html">InvokeScriptedProcessor</a></p></body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-scripting-nar/1.6.0/org.apache.nifi.processors.script.InvokeScriptedProcessor/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-scripting-nar/1.6.0/org.apache.nifi.processors.script.InvokeScriptedProcessor/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-scripting-nar/1.6.0/org.apache.nifi.processors.script.InvokeScriptedProcessor/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-scripting-nar/1.6.0/org.apache.nifi.processors.script.InvokeScriptedProcessor/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>InvokeScriptedProcessor</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;">InvokeScriptedProcessor</h1><h2>Description: </h2><p>Experimental - 
Invokes a script engine for a Processor defined in the given script. The script 
must define a valid class that implements the Processor interface, and it must 
set a variable 'processor' to an instance of the class. Processor methods such 
as onTrigger() will be delegated to the scripted Processor instance. Also any 
Relationships or PropertyDescriptors defined by the scripted processor will be 
added to the configuration dialog.  Experimental: Impact of sustained usage not 
yet verified.</p><h3>Tags: </h3><p>script, invoke, 
 groovy, python, jython, jruby, ruby, javascript, js, lua, 
luaj</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>Script Engine</strong></td><td 
id="default-value">Clojure</td><td 
id="allowable-values"><ul><li>Clojure</li><li>ECMAScript</li><li>Groovy</li><li>lua</li><li>python</li><li>ruby</li></ul></td><td
 id="description">The engine to execute scripts</td></tr><tr><td 
id="name">Script File</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Path to script file to execute. 
Only one of Script File or Script Body may be used<
 br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
id="name">Script Body</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Body of script to execute. Only 
one of Script File or Script Body may be used</td></tr><tr><td id="name">Module 
Directory</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">Comma-separated list of paths to files and/or directories 
which contain modules required by the script.<br/><strong>Supports Expression 
Language: true</strong></td></tr></table><h3>Dynamic Properties: 
</h3><p>Dynamic Properties allow the user to specify both the name and value of 
a property.<table 
id="dynamic-properties"><tr><th>Name</th><th>Value</th><th>Description</th></tr><tr><td
 id="name">A script engine property to update</td><td id="value">The value to 
set it to</td><td>Updates a script engine property specified by the Dynamic 
Property's key with the value specified by the Dynamic Property's value<
 br/><strong>Supports Expression Language: 
true</strong></td></tr></table></p><h3>Relationships: </h3>This processor has 
no relationships.<h3>Reads Attributes: </h3>None specified.<h3>Writes 
Attributes: </h3>None specified.<h3>State management: </h3><table 
id="stateful"><tr><th>Scope</th><th>Description</th></tr><tr><td>LOCAL, 
CLUSTER</td><td>Scripts can store and retrieve state using the State Management 
APIs. Consult the State Manager section of the Developer's Guide for more 
details.</td></tr></table><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>System Resource Considerations:</h3>None 
specified.<h3>See Also:</h3><p><a 
href="../org.apache.nifi.processors.script.ExecuteScript/index.html">ExecuteScript</a></p></body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-scripting-nar/1.6.0/org.apache.nifi.record.script.ScriptedReader/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-scripting-nar/1.6.0/org.apache.nifi.record.script.ScriptedReader/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-scripting-nar/1.6.0/org.apache.nifi.record.script.ScriptedReader/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-scripting-nar/1.6.0/org.apache.nifi.record.script.ScriptedReader/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ScriptedReader</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;">ScriptedReader</h1><h2>Description: </h2><p>Allows the user to provide a 
scripted RecordReaderFactory instance in order to read/parse/generate records 
from an incoming flow file.</p><h3>Tags: </h3><p>record, recordFactory, script, 
invoke, groovy, python, jython, jruby, ruby, javascript, js, lua, 
luaj</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>Script 
Engine</strong></td><td id="default-value">Clojure</td><td 
id="allowable-values"><ul><li>Clojure</li><li>ECMAScript</li><li>Groovy</li><li>lua</li><li>python</li><li>ruby</li></ul></td><td
 id="description">The engine to execute scripts</td></tr><tr><td 
id="name">Script File</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Path to script file to execute. 
Only one of Script File or Script Body may be used<br/><strong>Supports 
Expression Language: true</strong></td></tr><tr><td id="name">Script 
Body</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">Body of script to execute. Only one of Script File or Script 
Body may be used</td></tr><tr><td id="name">Module Directory</td><td 
id="default-value"></td><td id="allowable-values"></td>
 <td id="description">Comma-separated list of paths to files and/or directories 
which contain modules required by the script.<br/><strong>Supports Expression 
Language: true</strong></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>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-scripting-nar/1.6.0/org.apache.nifi.record.script.ScriptedRecordSetWriter/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-scripting-nar/1.6.0/org.apache.nifi.record.script.ScriptedRecordSetWriter/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-scripting-nar/1.6.0/org.apache.nifi.record.script.ScriptedRecordSetWriter/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-scripting-nar/1.6.0/org.apache.nifi.record.script.ScriptedRecordSetWriter/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ScriptedRecordSetWriter</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;">ScriptedRecordSetWriter</h1><h2>Description: </h2><p>Allows the user to 
provide a scripted RecordSetWriterFactory instance in order to write records to 
an outgoing flow file.</p><h3>Tags: </h3><p>record, writer, script, invoke, 
groovy, python, jython, jruby, ruby, javascript, js, lua, 
luaj</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-g
 uide.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>Script 
Engine</strong></td><td id="default-value">Clojure</td><td 
id="allowable-values"><ul><li>Clojure</li><li>ECMAScript</li><li>Groovy</li><li>lua</li><li>python</li><li>ruby</li></ul></td><td
 id="description">The engine to execute scripts</td></tr><tr><td 
id="name">Script File</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Path to script file to execute. 
Only one of Script File or Script Body may be used<br/><strong>Supports 
Expression Language: true</strong></td></tr><tr><td id="name">Script 
Body</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">Body of script to execute. Only one of Script File or Script 
Body may be used</td></tr><tr><td id="name">Module Directory</td><td 
id="default-value"></td><td id="allowable-values"></td><t
 d id="description">Comma-separated list of paths to files and/or directories 
which contain modules required by the script.<br/><strong>Supports Expression 
Language: true</strong></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>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-scripting-nar/1.6.0/org.apache.nifi.reporting.script.ScriptedReportingTask/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-scripting-nar/1.6.0/org.apache.nifi.reporting.script.ScriptedReportingTask/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-scripting-nar/1.6.0/org.apache.nifi.reporting.script.ScriptedReportingTask/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-scripting-nar/1.6.0/org.apache.nifi.reporting.script.ScriptedReportingTask/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ScriptedReportingTask</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;">ScriptedReportingTask</h1><h2>Description: </h2><p>Provides reporting 
and status information to a script. ReportingContext, ComponentLog, and 
VirtualMachineMetrics objects are made available as variables (context, log, 
and vmMetrics, respectively) to the script for further processing. The context 
makes various information available such as events, provenance, bulletins, 
controller services, process groups, Java Virtual Machine metrics, 
etc.</p><h3>Tags: </h3><p>reporting, script, execute, groovy, python, jython, 
jruby, ruby, javascript, js, lua, luaj</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>Script Engine</strong></td><td 
id="default-value">Clojure</td><td 
id="allowable-values"><ul><li>Clojure</li><li>ECMAScript</li><li>Groovy</li><li>lua</li><li>python</li><li>ruby</li></ul></td><td
 id="description">The engine to execute scripts</td></tr><tr><td 
id="name">Script File</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Path to script file to execute. 
Only one of Script File or Script Body may be used<br/><strong>Supports 
Expression Language: true</strong></td></tr><tr><td id="name">Script 
Body</td><td
  id="default-value"></td><td id="allowable-values"></td><td 
id="description">Body of script to execute. Only one of Script File or Script 
Body may be used</td></tr><tr><td id="name">Module Directory</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Comma-separated list of paths to files and/or directories 
which contain modules required by the script.<br/><strong>Supports Expression 
Language: true</strong></td></tr></table><h3>Dynamic Properties: 
</h3><p>Dynamic Properties allow the user to specify both the name and value of 
a property.<table 
id="dynamic-properties"><tr><th>Name</th><th>Value</th><th>Description</th></tr><tr><td
 id="name">A script engine property to update</td><td id="value">The value to 
set it to</td><td>Updates a script engine property specified by the Dynamic 
Property's key with the value specified by the Dynamic Property's 
value<br/><strong>Supports Expression Language: 
true</strong></td></tr></table></p><h3>State management: </h
 3>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>System Resource Considerations:</h3>None 
specified.</body></html>
\ No newline at end of file


Reply via email to