Modified: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.hadoop.ListHDFS/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.hadoop.ListHDFS/index.html?rev=1730777&r1=1730776&r2=1730777&view=diff
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.hadoop.ListHDFS/index.html
 (original)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.hadoop.ListHDFS/index.html
 Wed Feb 17 02:20:53 2016
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ListHDFS</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Retrieves a 
listing of files from HDFS. For each file that is listed in HDFS, creates a 
FlowFile that represents the HDFS file so that it can be fetched in conjunction 
with ListHDFS. This Processor is designed to run on Primary Node only in a 
cluster. If the primary node changes, the new Primary Node will pick up where 
the previous node left off without duplicating all of the data. Unlike GetHDFS, 
this Processor does not delete any data from HDFS.</p><h3>Tags: </h3><p>hadoop, 
HDFS, get, list, ingest, source, filesystem</p><h3>Properties: </h3><p>In the 
list below, the names of required properties appear in <strong>bold</strong>. 
Any other properties (not in bold) are considered optional. The table also 
indicates any default values.</p><table id="properties"><tr><th>Name</th><t
 h>Default Value</th><th>Allowable Values</th><th>Description</th></tr><tr><td 
id="name">Hadoop Configuration Resources</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">A file or comma separated list 
of files which contains the Hadoop file system configuration. Without this, 
Hadoop will search the classpath for a 'core-site.xml' and 'hdfs-site.xml' file 
or will revert to a default configuration.</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="../org.apache.nifi.distributed.cache.client.DistributedMapCacheClientService/index.html">DistributedMapCacheClientService</a></td><td
 id="description">Specifies the Controller Service that should be used to 
maintain state about what has been pulled from HDFS so that if a new node 
begins pulling data, it won't dup
 licate all of the work that has been done.</td></tr><tr><td 
id="name"><strong>Directory</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The HDFS directory from which 
files should be read</td></tr><tr><td id="name"><strong>Recurse 
Subdirectories</strong></td><td id="default-value">true</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Indicates whether to list files from subdirectories of the 
HDFS directory</td></tr><tr><td id="name">Kerberos Principal</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Kerberos principal to authenticate as. Requires 
nifi.kerberos.krb5.file to be set in your nifi.properties</td></tr><tr><td 
id="name">Kerberos Keytab</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Kerberos keytab associated with 
the principal. Requires nifi.kerberos.krb5.file to be set in your 
nifi.properties</td></tr><tr><td id="na
 me">Kerberos Relogin Period</td><td id="default-value">4 hours</td><td 
id="allowable-values"></td><td id="description">Period of time which should 
pass before attempting a kerberos relogin</td></tr></table><h3>Relationships: 
</h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>All
 FlowFiles are transferred to this relationship</td></tr></table><h3>Reads 
Attributes: </h3>None specified.<h3>Writes Attributes: </h3><table 
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>filename</td><td>The
 name of the file that was read from HDFS.</td></tr><tr><td>path</td><td>The 
path is set to the absolute path of the file's directory on HDFS. For example, 
if the Directory property is set to /tmp, then files picked up from /tmp will 
have the path attribute set to "./". If the Recurse Subdirectories property is 
set to true and a file is picked up from /tmp/abc/1/2/3, then the path 
attribute will be set to "/tmp/abc/1/2/3".</td></tr><
 tr><td>hdfs.owner</td><td>The user that owns the file in 
HDFS</td></tr><tr><td>hdfs.group</td><td>The group that owns the file in 
HDFS</td></tr><tr><td>hdfs.lastModified</td><td>The timestamp of when the file 
in HDFS was last modified, as milliseconds since midnight Jan 1, 1970 
UTC</td></tr><tr><td>hdfs.length</td><td>The number of bytes in the file in 
HDFS</td></tr><tr><td>hdfs.replication</td><td>The number of HDFS replicas for 
hte file</td></tr><tr><td>hdfs.permissions</td><td>The permissions for the file 
in HDFS. This is formatted as 3 characters for the owner, 3 for the group, and 
3 for other users. For example rw-rw-r--</td></tr></table><h3>See 
Also:</h3><p><a 
href="../org.apache.nifi.processors.hadoop.GetHDFS/index.html">GetHDFS</a>, <a 
href="../org.apache.nifi.processors.hadoop.FetchHDFS/index.html">FetchHDFS</a>, 
<a 
href="../org.apache.nifi.processors.hadoop.PutHDFS/index.html">PutHDFS</a></p></body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ListHDFS</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Retrieves a 
listing of files from HDFS. For each file that is listed in HDFS, creates a 
FlowFile that represents the HDFS file so that it can be fetched in conjunction 
with ListHDFS. This Processor is designed to run on Primary Node only in a 
cluster. If the primary node changes, the new Primary Node will pick up where 
the previous node left off without duplicating all of the data. Unlike GetHDFS, 
this Processor does not delete any data from HDFS.</p><h3>Tags: </h3><p>hadoop, 
HDFS, get, list, ingest, source, filesystem</p><h3>Properties: </h3><p>In the 
list below, the names of required properties appear in <strong>bold</strong>. 
Any other properties (not in bold) are considered optional. The table also 
indicates any default values.</p><table id="properties"><tr><th>Name</th><t
 h>Default Value</th><th>Allowable Values</th><th>Description</th></tr><tr><td 
id="name">Hadoop Configuration Resources</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">A file or comma separated list 
of files which contains the Hadoop file system configuration. Without this, 
Hadoop will search the classpath for a 'core-site.xml' and 'hdfs-site.xml' file 
or will revert to a default configuration.</td></tr><tr><td 
id="name">Distributed Cache Service</td><td id="default-value"></td><td 
id="allowable-values"><strong>Controller Service API: 
</strong><br/>DistributedMapCacheClient<br/><strong>Implementation:</strong><br/><a
 
href="../org.apache.nifi.distributed.cache.client.DistributedMapCacheClientService/index.html">DistributedMapCacheClientService</a></td><td
 id="description">Specifies the Controller Service that should be used to 
maintain state about what has been pulled from HDFS so that if a new node 
begins pulling data, it won't duplicate all of the
  work that has been done.</td></tr><tr><td 
id="name"><strong>Directory</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The HDFS directory from which 
files should be read</td></tr><tr><td id="name"><strong>Recurse 
Subdirectories</strong></td><td id="default-value">true</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Indicates whether to list files from subdirectories of the 
HDFS directory</td></tr><tr><td id="name">Kerberos Principal</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Kerberos principal to authenticate as. Requires 
nifi.kerberos.krb5.file to be set in your nifi.properties</td></tr><tr><td 
id="name">Kerberos Keytab</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Kerberos keytab associated with 
the principal. Requires nifi.kerberos.krb5.file to be set in your 
nifi.properties</td></tr><tr><td id="name">Kerberos Relo
 gin Period</td><td id="default-value">4 hours</td><td 
id="allowable-values"></td><td id="description">Period of time which should 
pass before attempting a kerberos relogin</td></tr></table><h3>Relationships: 
</h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>All
 FlowFiles are transferred to this relationship</td></tr></table><h3>Reads 
Attributes: </h3>None specified.<h3>Writes Attributes: </h3><table 
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>filename</td><td>The
 name of the file that was read from HDFS.</td></tr><tr><td>path</td><td>The 
path is set to the absolute path of the file's directory on HDFS. For example, 
if the Directory property is set to /tmp, then files picked up from /tmp will 
have the path attribute set to "./". If the Recurse Subdirectories property is 
set to true and a file is picked up from /tmp/abc/1/2/3, then the path 
attribute will be set to "/tmp/abc/1/2/3".</td></tr><tr><td>hdfs.owner
 </td><td>The user that owns the file in 
HDFS</td></tr><tr><td>hdfs.group</td><td>The group that owns the file in 
HDFS</td></tr><tr><td>hdfs.lastModified</td><td>The timestamp of when the file 
in HDFS was last modified, as milliseconds since midnight Jan 1, 1970 
UTC</td></tr><tr><td>hdfs.length</td><td>The number of bytes in the file in 
HDFS</td></tr><tr><td>hdfs.replication</td><td>The number of HDFS replicas for 
hte file</td></tr><tr><td>hdfs.permissions</td><td>The permissions for the file 
in HDFS. This is formatted as 3 characters for the owner, 3 for the group, and 
3 for other users. For example rw-rw-r--</td></tr></table><h3>See 
Also:</h3><p><a 
href="../org.apache.nifi.processors.hadoop.GetHDFS/index.html">GetHDFS</a>, <a 
href="../org.apache.nifi.processors.hadoop.FetchHDFS/index.html">FetchHDFS</a>, 
<a 
href="../org.apache.nifi.processors.hadoop.PutHDFS/index.html">PutHDFS</a></p></body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.kite.InferAvroSchema/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.kite.InferAvroSchema/index.html?rev=1730777&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.kite.InferAvroSchema/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.kite.InferAvroSchema/index.html
 Wed Feb 17 02:20:53 2016
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>InferAvroSchema</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Examines the 
contents of the incoming FlowFile to infer an Avro schema. The processor will 
use the Kite SDK to make an attempt to automatically generate an Avro schema 
from the incoming content. When inferring the schema from JSON data the key 
names will be used in the resulting Avro schema definition. When inferring from 
CSV data a "header definition" must be present either as the first line of the 
incoming data or the "header definition" must be explicitly set in the property 
"CSV Header Definition". A "header definition" is simply a single comma 
separated line defining the names of each column. The "header definition" is 
required in order to determine the names that should be given to each field in 
the resulting Avro definition. When inferring data types the higher o
 rder data type is always used if there is ambiguity. For example when 
examining numerical values the type may be set to "long" instead of "integer" 
since a long can safely hold the value of any "integer". Only CSV and JSON 
content is currently supported for automatically inferring an Avro schema. The 
type of content present in the incoming FlowFile is set by using the property 
"Input Content Type". The property can either be explicitly set to CSV, JSON, 
or "use mime.type value" which will examine the value of the mime.type 
attribute on the incoming FlowFile to determine the type of content 
present.</p><h3>Tags: </h3><p>kite, avro, infer, schema, csv, 
json</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 Output Destination</strong></td><td 
id="default-value">flowfile-content</td><td 
id="allowable-values"><ul><li>flowfile-attribute</li><li>flowfile-content</li></ul></td><td
 id="description">Control if Avro schema is written as a new flowfile attribute 
'inferred.avro.schema' or written in the flowfile content. Writing to flowfile 
content will overwrite any existing flowfile content.</td></tr><tr><td 
id="name"><strong>Input Content Type</strong></td><td id="default-value">use 
mime.type value</td><td id="allowable-values"><ul><li>use mime.type 
value</li><li>json</li><li>csv</li></ul></td><td id="description">Content Type 
of data present in the incoming FlowFile's content. Only "json" or "csv" are 
supported. If this value is set to "use mime.type value" the incoming 
Flowfile's attribute "MIME_TYPE" will be used to determine the Content Type
 .</td></tr><tr><td id="name">CSV Header Definition</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">This property only applies to CSV content type. Comma 
separated string defining the column names expected in the CSV data. EX: 
"fname,lname,zip,address". The elements present in this string should be in the 
same order as the underlying data. Setting this property will cause the value 
of "Get CSV Header Definition From Data" to be ignored instead using this 
value.<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
id="name"><strong>Get CSV Header Definition From Data</strong></td><td 
id="default-value">true</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">This property only applies to CSV content type. If "true" the 
processor will attempt to read the CSV header definition from the first line of 
the input data.</td></tr><tr><td id="name"><strong>CSV Header Line Skip 
Count</strong></td><td
  id="default-value">0</td><td id="allowable-values"></td><td 
id="description">This property only applies to CSV content type. Specifies the 
number of lines that should be skipped when reading the CSV data. Setting this 
value to 0 is equivalent to saying "the entire contents of the file should be 
read". If the property "Get CSV Header Definition From Data" is set then the 
first line of the CSV  file will be read in and treated as the CSV header 
definition. Since this will remove the header line from the data care should be 
taken to make sure the value of "CSV header Line Skip Count" is set to 0 to 
ensure no data is skipped.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>CSV Escape 
String</strong></td><td id="default-value">\</td><td 
id="allowable-values"></td><td id="description">This property only applies to 
CSV content type. String that represents an escape sequence in the CSV FlowFile 
content data.<br/><strong>Supports Expression Languag
 e: true</strong></td></tr><tr><td id="name"><strong>CSV Quote 
String</strong></td><td id="default-value">'</td><td 
id="allowable-values"></td><td id="description">This property only applies to 
CSV content type. String that represents a literal quote character in the CSV 
FlowFile content data.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Pretty Avro 
Output</strong></td><td id="default-value">true</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">If true the Avro output will be formatted.</td></tr><tr><td 
id="name"><strong>Avro Record Name</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Value to be placed in the Avro 
record schema "name" field.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Number Of Records To 
Analyze</strong></td><td id="default-value">10</td><td 
id="allowable-values"></td><td id="description
 ">This property only applies to JSON content type. The number of JSON records 
that should be examined to determine the Avro schema. The higher the value the 
better chance kite has of detecting the appropriate type. However the default 
value of 10 is almost always enough.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Charset</strong></td><td 
id="default-value">UTF-8</td><td id="allowable-values"></td><td 
id="description">Character encoding of CSV 
data.</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>unsupported
 content</td><td>The content found in the flowfile content is not of the 
required format.</td></tr><tr><td>success</td><td>Successfully created Avro 
schema from data.</td></tr><tr><td>failure</td><td>Failed to create Avro schema 
from data.</td></tr><tr><td>original</td><td>Original incoming FlowFile 
data</td></tr></table><h3>Reads Attributes: </h3><table id="reads-a
 
ttributes"><tr><th>Name</th><th>Description</th></tr><tr><td>mime.type</td><td>If
 configured by property "Input Content Type" will use this value to determine 
what sort of content should be inferred from the incoming FlowFile 
content.</td></tr></table><h3>Writes Attributes: </h3><table 
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>inferred.avro.schema</td><td>If
 configured by "Schema output destination" to write to an attribute this will 
hold the resulting Avro schema from inferring the incoming FlowFile 
content.</td></tr></table></body></html>
\ No newline at end of file

Modified: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.mongodb.GetMongo/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.mongodb.GetMongo/index.html?rev=1730777&r1=1730776&r2=1730777&view=diff
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.mongodb.GetMongo/index.html
 (original)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.mongodb.GetMongo/index.html
 Wed Feb 17 02:20:53 2016
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>GetMongo</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Creates FlowFiles 
from documents in MongoDB</p><h3>Tags: </h3><p>mongodb, read, 
get</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>Mongo 
URI</strong></td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">MongoURI, typically of the form: 
mongodb://host1[:port1][,host2[:port2],...]</td></tr><tr><td 
id="name"><strong>Mongo Database Name</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
name of the d
 atabase to use</td></tr><tr><td id="name"><strong>Mongo Collection 
Name</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The name of the collection to 
use</td></tr><tr><td id="name">Query</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The selection criteria; must be 
a valid BSON document; if omitted the entire collection will be 
queried</td></tr><tr><td id="name">Projection</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
fields to be returned from the documents in the result set; must be a valid 
BSON document</td></tr><tr><td id="name">Sort</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
fields by which to sort; must be a valid BSON document</td></tr><tr><td 
id="name">Limit</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The maximum number of elements 
to return</td></tr><tr><td id="name">B
 atch Size</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">The number of elements returned from the server 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>All
 files are routed to success</td></tr></table><h3>Reads Attributes: </h3>None 
specified.<h3>Writes Attributes: </h3>None specified.</body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>GetMongo</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Creates FlowFiles 
from documents in MongoDB</p><h3>Tags: </h3><p>mongodb, read, 
get</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>Mongo 
URI</strong></td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">MongoURI, typically of the form: 
mongodb://host1[:port1][,host2[:port2],...]</td></tr><tr><td 
id="name"><strong>Mongo Database Name</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
name of the d
 atabase to use</td></tr><tr><td id="name"><strong>Mongo Collection 
Name</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The name of the collection to 
use</td></tr><tr><td id="name">Query</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The selection criteria; must be 
a valid MongoDB Extended JSON format; if omitted the entire collection will be 
queried</td></tr><tr><td id="name">Projection</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
fields to be returned from the documents in the result set; must be a valid 
BSON document</td></tr><tr><td id="name">Sort</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
fields by which to sort; must be a valid BSON document</td></tr><tr><td 
id="name">Limit</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The maximum number of elements 
to return</td></tr><tr>
 <td id="name">Batch Size</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The number of elements returned 
from the server 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>All
 files are routed to success</td></tr></table><h3>Reads Attributes: </h3>None 
specified.<h3>Writes Attributes: </h3>None specified.</body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.riemann.PutRiemann/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.riemann.PutRiemann/index.html?rev=1730777&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.riemann.PutRiemann/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.riemann.PutRiemann/index.html
 Wed Feb 17 02:20:53 2016
@@ -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><body><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 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>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 milliseconds 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">Des
 cription</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 i
 
d="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.</body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.script.ExecuteScript/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.script.ExecuteScript/index.html?rev=1730777&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.script.ExecuteScript/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.script.ExecuteScript/index.html
 Wed Feb 17 02:20:53 2016
@@ -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><body><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</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">ECMAScript</td><td 
id="allowable-values"><ul><li>ECMAScript</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 mod
 ules required by the script.</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>Description</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.</body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.script.InvokeScriptedProcessor/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.script.InvokeScriptedProcessor/index.html?rev=1730777&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.script.InvokeScriptedProcessor/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.script.InvokeScriptedProcessor/index.html
 Wed Feb 17 02:20:53 2016
@@ -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><body><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 option
 al. 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">ECMAScript</td><td 
id="allowable-values"><ul><li>ECMAScript</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.</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>Description</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 
specifie
 d.<h3>Writes Attributes: </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

Modified: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.solr.GetSolr/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.solr.GetSolr/index.html?rev=1730777&r1=1730776&r2=1730777&view=diff
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.solr.GetSolr/index.html
 (original)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.solr.GetSolr/index.html
 Wed Feb 17 02:20:53 2016
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>GetSolr</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Queries Solr and 
outputs the results as a FlowFile</p><h3>Tags: </h3><p>Apache, Solr, Get, 
Pull</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>Solr Type</strong></td><td 
id="default-value">Standard</td><td id="allowable-values"><ul><li>Cloud <img 
src="../../html/images/iconInfo.png" alt="A SolrCloud instance." title="A 
SolrCloud instance."></img></li><li>St
 andard <img src="../../html/images/iconInfo.png" alt="A stand-alone Solr 
instance." title="A stand-alone Solr instance."></img></li></ul></td><td 
id="description">The type of Solr instance, Cloud or Standard.</td></tr><tr><td 
id="name"><strong>Solr Location</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The Solr url for a Solr Type of 
Standard (ex: http://localhost:8984/solr/gettingstarted), or the ZooKeeper 
hosts for a Solr Type of Cloud (ex: localhost:9983).</td></tr><tr><td 
id="name">Collection</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The Solr collection name, only 
used with a Solr Type of Cloud<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Solr Query</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">A 
query to execute against Solr</td></tr><tr><td id="name">Return Fields</td><td 
id="default-value"></td><t
 d id="allowable-values"></td><td id="description">Comma-separated list of 
fields names to return</td></tr><tr><td id="name">Sort Clause</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">A 
Solr sort clause, ex: field1 asc, field2 desc</td></tr><tr><td 
id="name"><strong>Date Field</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The name of a date field in 
Solr used to filter results</td></tr><tr><td id="name"><strong>Batch 
Size</strong></td><td id="default-value">100</td><td 
id="allowable-values"></td><td id="description">Number of rows per Solr 
query</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>The
 results of querying Solr</td></tr></table><h3>Reads Attributes: </h3>None 
specified.<h3>Writes Attributes: </h3>None specified.</body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>GetSolr</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Queries Solr and 
outputs the results as a FlowFile</p><h3>Tags: </h3><p>Apache, Solr, Get, 
Pull</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>Solr Type</strong></td><td 
id="default-value">Standard</td><td id="allowable-values"><ul><li>Cloud <img 
src="../../html/images/iconInfo.png" alt="A SolrCloud instance." title="A 
SolrCloud instance."></img></li><li>St
 andard <img src="../../html/images/iconInfo.png" alt="A stand-alone Solr 
instance." title="A stand-alone Solr instance."></img></li></ul></td><td 
id="description">The type of Solr instance, Cloud or Standard.</td></tr><tr><td 
id="name"><strong>Solr Location</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The Solr url for a Solr Type of 
Standard (ex: http://localhost:8984/solr/gettingstarted), or the ZooKeeper 
hosts for a Solr Type of Cloud (ex: localhost:9983).</td></tr><tr><td 
id="name">Collection</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The Solr collection name, only 
used with a Solr Type of Cloud<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Solr Query</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">A 
query to execute against Solr</td></tr><tr><td id="name">Return Fields</td><td 
id="default-value"></td><t
 d id="allowable-values"></td><td id="description">Comma-separated list of 
fields names to return</td></tr><tr><td id="name">Sort Clause</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">A 
Solr sort clause, ex: field1 asc, field2 desc</td></tr><tr><td 
id="name"><strong>Date Field</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The name of a date field in 
Solr used to filter results</td></tr><tr><td id="name"><strong>Batch 
Size</strong></td><td id="default-value">100</td><td 
id="allowable-values"></td><td id="description">Number of rows per Solr 
query</td></tr><tr><td id="name"><strong>Solr Socket Timeout</strong></td><td 
id="default-value">10 seconds</td><td id="allowable-values"></td><td 
id="description">The amount of time to wait for data on a socket connection to 
Solr. A value of 0 indicates an infinite timeout.</td></tr><tr><td 
id="name"><strong>Solr Connection Timeout</strong></td><td id="default-valu
 e">10 seconds</td><td id="allowable-values"></td><td id="description">The 
amount of time to wait when establishing a connection to Solr. A value of 0 
indicates an infinite timeout.</td></tr><tr><td id="name"><strong>Solr Maximum 
Connections</strong></td><td id="default-value">10</td><td 
id="allowable-values"></td><td id="description">The maximum number of total 
connections allowed from the Solr client to Solr.</td></tr><tr><td 
id="name"><strong>Solr Maximum Connections Per Host</strong></td><td 
id="default-value">5</td><td id="allowable-values"></td><td 
id="description">The maximum number of connections allowed from the Solr client 
to a single Solr host.</td></tr><tr><td id="name">ZooKeeper Client 
Timeout</td><td id="default-value">10 seconds</td><td 
id="allowable-values"></td><td id="description">The amount of time to wait for 
data on a connection to ZooKeeper, only used with a Solr Type of 
Cloud.</td></tr><tr><td id="name">ZooKeeper Connection Timeout</td><td 
id="default-value">10
  seconds</td><td id="allowable-values"></td><td id="description">The amount of 
time to wait when establishing a connection to ZooKeeper, only used with a Solr 
Type of Cloud.</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>The
 results of querying Solr</td></tr></table><h3>Reads Attributes: </h3>None 
specified.<h3>Writes Attributes: </h3>None specified.</body></html>
\ No newline at end of file

Modified: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.solr.PutSolrContentStream/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.solr.PutSolrContentStream/index.html?rev=1730777&r1=1730776&r2=1730777&view=diff
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.solr.PutSolrContentStream/index.html
 (original)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.solr.PutSolrContentStream/index.html
 Wed Feb 17 02:20:53 2016
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>PutSolrContentStream</title><link 
rel="stylesheet" href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Sends the contents 
of a FlowFile as a ContentStream to Solr</p><p><a 
href="additionalDetails.html">Additional Details...</a></p><h3>Tags: 
</h3><p>Apache, Solr, Put, Send</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>Solr Type</strong></td><td 
id="default-value">Standard</td><td id="allowable-values"><ul><li>Cloud <img 
src="../../html/images/ic
 onInfo.png" alt="A SolrCloud instance." title="A SolrCloud 
instance."></img></li><li>Standard <img src="../../html/images/iconInfo.png" 
alt="A stand-alone Solr instance." title="A stand-alone Solr 
instance."></img></li></ul></td><td id="description">The type of Solr instance, 
Cloud or Standard.</td></tr><tr><td id="name"><strong>Solr 
Location</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The Solr url for a Solr Type of 
Standard (ex: http://localhost:8984/solr/gettingstarted), or the ZooKeeper 
hosts for a Solr Type of Cloud (ex: localhost:9983).</td></tr><tr><td 
id="name">Collection</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The Solr collection name, only 
used with a Solr Type of Cloud<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Content Stream 
Path</strong></td><td id="default-value">/update/json/docs</td><td 
id="allowable-values"></td><td id="descrip
 tion">The path in Solr to post the ContentStream<br/><strong>Supports 
Expression Language: true</strong></td></tr><tr><td 
id="name"><strong>Content-Type</strong></td><td 
id="default-value">application/json</td><td id="allowable-values"></td><td 
id="description">Content-Type being sent to Solr<br/><strong>Supports 
Expression Language: true</strong></td></tr><tr><td id="name">Commit 
Within</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">The number of milliseconds before the given update is 
committed<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 Solr request parameter name</td><td id="value">A Solr request 
parameter value</td><td>These parameters will be passed to Solr on the 
request</td></tr></table></p><
 h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>The
 original FlowFile</td></tr><tr><td>failure</td><td>FlowFiles that failed for 
any reason other than Solr being 
unreachable</td></tr><tr><td>connection_failure</td><td>FlowFiles that failed 
because Solr is unreachable</td></tr></table><h3>Reads Attributes: </h3>None 
specified.<h3>Writes Attributes: </h3>None specified.</body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>PutSolrContentStream</title><link 
rel="stylesheet" href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Sends the contents 
of a FlowFile as a ContentStream to Solr</p><p><a 
href="additionalDetails.html">Additional Details...</a></p><h3>Tags: 
</h3><p>Apache, Solr, Put, Send</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>Solr Type</strong></td><td 
id="default-value">Standard</td><td id="allowable-values"><ul><li>Cloud <img 
src="../../html/images/ic
 onInfo.png" alt="A SolrCloud instance." title="A SolrCloud 
instance."></img></li><li>Standard <img src="../../html/images/iconInfo.png" 
alt="A stand-alone Solr instance." title="A stand-alone Solr 
instance."></img></li></ul></td><td id="description">The type of Solr instance, 
Cloud or Standard.</td></tr><tr><td id="name"><strong>Solr 
Location</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The Solr url for a Solr Type of 
Standard (ex: http://localhost:8984/solr/gettingstarted), or the ZooKeeper 
hosts for a Solr Type of Cloud (ex: localhost:9983).</td></tr><tr><td 
id="name">Collection</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The Solr collection name, only 
used with a Solr Type of Cloud<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Content Stream 
Path</strong></td><td id="default-value">/update/json/docs</td><td 
id="allowable-values"></td><td id="descrip
 tion">The path in Solr to post the ContentStream<br/><strong>Supports 
Expression Language: true</strong></td></tr><tr><td 
id="name"><strong>Content-Type</strong></td><td 
id="default-value">application/json</td><td id="allowable-values"></td><td 
id="description">Content-Type being sent to Solr<br/><strong>Supports 
Expression Language: true</strong></td></tr><tr><td id="name">Commit 
Within</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">The number of milliseconds before the given update is 
committed<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Solr Socket 
Timeout</strong></td><td id="default-value">10 seconds</td><td 
id="allowable-values"></td><td id="description">The amount of time to wait for 
data on a socket connection to Solr. A value of 0 indicates an infinite 
timeout.</td></tr><tr><td id="name"><strong>Solr Connection 
Timeout</strong></td><td id="default-value">10 seconds</td><td 
id="allowable-valu
 es"></td><td id="description">The amount of time to wait when establishing a 
connection to Solr. A value of 0 indicates an infinite 
timeout.</td></tr><tr><td id="name"><strong>Solr Maximum 
Connections</strong></td><td id="default-value">10</td><td 
id="allowable-values"></td><td id="description">The maximum number of total 
connections allowed from the Solr client to Solr.</td></tr><tr><td 
id="name"><strong>Solr Maximum Connections Per Host</strong></td><td 
id="default-value">5</td><td id="allowable-values"></td><td 
id="description">The maximum number of connections allowed from the Solr client 
to a single Solr host.</td></tr><tr><td id="name">ZooKeeper Client 
Timeout</td><td id="default-value">10 seconds</td><td 
id="allowable-values"></td><td id="description">The amount of time to wait for 
data on a connection to ZooKeeper, only used with a Solr Type of 
Cloud.</td></tr><tr><td id="name">ZooKeeper Connection Timeout</td><td 
id="default-value">10 seconds</td><td id="allowable-values"><
 /td><td id="description">The amount of time to wait when establishing a 
connection to ZooKeeper, only used with a Solr Type of 
Cloud.</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 Solr request parameter name</td><td id="value">A Solr request 
parameter value</td><td>These parameters will be passed to Solr on the 
request</td></tr></table></p><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>The
 original FlowFile</td></tr><tr><td>failure</td><td>FlowFiles that failed for 
any reason other than Solr being 
unreachable</td></tr><tr><td>connection_failure</td><td>FlowFiles that failed 
because Solr is unreachable</td></tr></table><h3>Reads Attributes: </h3>None 
specified.<h3>Writes Attributes: </h3>None specified.</body></html>
\ No newline at end of file

Modified: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ConvertJSONToSQL/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ConvertJSONToSQL/index.html?rev=1730777&r1=1730776&r2=1730777&view=diff
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ConvertJSONToSQL/index.html
 (original)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ConvertJSONToSQL/index.html
 Wed Feb 17 02:20:53 2016
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ConvertJSONToSQL</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Converts a 
JSON-formatted FlowFile into an UPDATE or INSERT SQL statement. The incoming 
FlowFile is expected to be "flat" JSON message, meaning that it consists of a 
single JSON element and each field maps to a simple type. If a field maps to a 
JSON object, that JSON object will be interpreted as Text. If the input is an 
array of JSON elements, each element in the array is output as a separate 
FlowFile to the 'sql' relationship. Upon successful conversion, the original 
FlowFile is routed to the 'original' relationship and the SQL is routed to the 
'sql' relationship.</p><h3>Tags: </h3><p>json, sql, database, rdbms, insert, 
update, relational, flat</p><h3>Properties: </h3><p>In the list below, the 
names of required properties appear in <strong>bold</strong>. Any other pr
 operties (not in bold) are considered optional. The table also indicates any 
default values, and whether a property supports the <a 
href="../../html/expression-language-guide.html">NiFi Expression 
Language</a>.</p><table id="properties"><tr><th>Name</th><th>Default 
Value</th><th>Allowable Values</th><th>Description</th></tr><tr><td 
id="name"><strong>JDBC Connection Pool</strong></td><td 
id="default-value"></td><td id="allowable-values"><strong>Controller Service 
API: </strong><br/>DBCPService<br/><strong>Implementation:</strong><br/><a 
href="../org.apache.nifi.dbcp.DBCPConnectionPool/index.html">DBCPConnectionPool</a></td><td
 id="description">Specifies the JDBC Connection Pool to use in order to convert 
the JSON message to a SQL statement. The Connection Pool is necessary in order 
to determine the appropriate database column types.</td></tr><tr><td 
id="name"><strong>Statement Type</strong></td><td id="default-value"></td><td 
id="allowable-values"><ul><li>UPDATE</li><li>INSERT</li></
 ul></td><td id="description">Specifies the type of SQL Statement to 
generate</td></tr><tr><td id="name"><strong>Table Name</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
name of the table that the statement should update<br/><strong>Supports 
Expression Language: true</strong></td></tr><tr><td id="name">Catalog 
Name</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">The name of the catalog that the statement should update. This 
may not apply for the database that you are updating. In this case, leave the 
field empty<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Schema Name</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
name of the schema that the table belongs to. This may not apply for the 
database that you are updating. In this case, leave the field 
empty<br/><strong>Supports Expression Language: true</strong></td></tr><tr>
 <td id="name">Translate Field Names</td><td id="default-value">true</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">If true, the Processor will attempt to translate JSON field 
names into the appropriate column names for the table specified. If false, the 
JSON field names must match the column names exactly, or the column will not be 
updated</td></tr><tr><td id="name">Unmatched Field Behavior</td><td 
id="default-value">Ignore Unmatched Fields</td><td 
id="allowable-values"><ul><li>Ignore Unmatched Fields <img 
src="../../html/images/iconInfo.png" alt="Any field in the JSON document that 
cannot be mapped to a column in the database is ignored" title="Any field in 
the JSON document that cannot be mapped to a column in the database is 
ignored"></img></li><li>Fail <img src="../../html/images/iconInfo.png" alt="If 
the JSON document has any field that cannot be mapped to a column in the 
database, the FlowFile will be routed to the failure relations
 hip" title="If the JSON document has any field that cannot be mapped to a 
column in the database, the FlowFile will be routed to the failure 
relationship"></img></li></ul></td><td id="description">If an incoming JSON 
element has a field that does not map to any of the database table's columns, 
this property specifies how to handle the situation</td></tr><tr><td 
id="name">Update Keys</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">A comma-separated list of 
column names that uniquely identifies a row in the database for UPDATE 
statements. If the Statement Type is UPDATE and this property is not set, the 
table's Primary Keys are used. In this case, if no Primary Key exists, the 
conversion to SQL will fail. This property is ignored if the Statement Type is 
INSERT<br/><strong>Supports Expression Language: 
true</strong></td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>sql</td><td>A
 Flow
 File is routed to this relationship when its contents have successfully been 
converted into a SQL statement</td></tr><tr><td>failure</td><td>A FlowFile is 
routed to this relationship if it cannot be converted into a SQL statement. 
Common causes include invalid JSON content or the JSON content missing a 
required field (if using an INSERT statement 
type).</td></tr><tr><td>original</td><td>When a FlowFile is converted to SQL, 
the original JSON FlowFile is routed to this 
relationship</td></tr></table><h3>Reads Attributes: </h3>None 
specified.<h3>Writes Attributes: </h3><table 
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>mime.type</td><td>Sets
 mime.type of FlowFile that is routed to 'sql' to 
'text/plain'.</td></tr><tr><td>sql.table</td><td>Sets the sql.table attribute 
of FlowFile that is routed to 'sql' to the name of the table that is updated by 
the SQL statement.</td></tr><tr><td>sql.catalog</td><td>If the Catalog name is 
set for this database, specifies the
  name of the catalog that the SQL statement will update. If no catalog is 
used, this attribute will not be 
added.</td></tr><tr><td>fragment.identifier</td><td>All FlowFiles routed to the 
'sql' relationship for the same incoming FlowFile (multiple will be output for 
the same incoming FlowFile if the incoming FlowFile is a JSON Array) will have 
the same value for the fragment.identifier attribute. This can then be used to 
correlate the results.</td></tr><tr><td>fragment.count</td><td>The number of 
SQL FlowFiles that were produced for same incoming FlowFile. This can be used 
in conjunction with the fragment.identifier attribute in order to know how many 
FlowFiles belonged to the same incoming 
FlowFile.</td></tr><tr><td>fragment.index</td><td>The position of this FlowFile 
in the list of outgoing FlowFiles that were all derived from the same incoming 
FlowFile. This can be used in conjunction with the fragment.identifier and 
fragment.count attributes to know which FlowFiles originated fro
 m the same incoming FlowFile and in what order the SQL FlowFiles were 
produced</td></tr><tr><td>sql.args.N.type</td><td>The output SQL statements are 
parameterized in order to avoid SQL Injection Attacks. The types of the 
Parameters to use are stored in attributes named sql.args.1.type, 
sql.args.2.type, sql.args.3.type, and so on. The type is a number representing 
a JDBC Type constant. Generally, this is useful only for software to read and 
interpret but is added so that a processor such as PutSQL can understand how to 
interpret the values.</td></tr><tr><td>sql.args.N.value</td><td>The output SQL 
statements are parameterized in order to avoid SQL Injection Attacks. The 
values of the Parameters to use are stored in the attributes named 
sql.args.1.value, sql.args.2.value, sql.args.3.value, and so on. Each of these 
attributes has a corresponding sql.args.N.type attribute that indicates how the 
value should be interpreted when inserting it into the 
database.</td></tr></table><h3>See Als
 o:</h3><p><a 
href="../org.apache.nifi.processors.standard.PutSQL/index.html">PutSQL</a></p></body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ConvertJSONToSQL</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Converts a 
JSON-formatted FlowFile into an UPDATE or INSERT SQL statement. The incoming 
FlowFile is expected to be "flat" JSON message, meaning that it consists of a 
single JSON element and each field maps to a simple type. If a field maps to a 
JSON object, that JSON object will be interpreted as Text. If the input is an 
array of JSON elements, each element in the array is output as a separate 
FlowFile to the 'sql' relationship. Upon successful conversion, the original 
FlowFile is routed to the 'original' relationship and the SQL is routed to the 
'sql' relationship.</p><h3>Tags: </h3><p>json, sql, database, rdbms, insert, 
update, relational, flat</p><h3>Properties: </h3><p>In the list below, the 
names of required properties appear in <strong>bold</strong>. Any other pr
 operties (not in bold) are considered optional. The table also indicates any 
default values, and whether a property supports the <a 
href="../../html/expression-language-guide.html">NiFi Expression 
Language</a>.</p><table id="properties"><tr><th>Name</th><th>Default 
Value</th><th>Allowable Values</th><th>Description</th></tr><tr><td 
id="name"><strong>JDBC Connection Pool</strong></td><td 
id="default-value"></td><td id="allowable-values"><strong>Controller Service 
API: </strong><br/>DBCPService<br/><strong>Implementation:</strong><br/><a 
href="../org.apache.nifi.dbcp.DBCPConnectionPool/index.html">DBCPConnectionPool</a></td><td
 id="description">Specifies the JDBC Connection Pool to use in order to convert 
the JSON message to a SQL statement. The Connection Pool is necessary in order 
to determine the appropriate database column types.</td></tr><tr><td 
id="name"><strong>Statement Type</strong></td><td id="default-value"></td><td 
id="allowable-values"><ul><li>UPDATE</li><li>INSERT</li></
 ul></td><td id="description">Specifies the type of SQL Statement to 
generate</td></tr><tr><td id="name"><strong>Table Name</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
name of the table that the statement should update<br/><strong>Supports 
Expression Language: true</strong></td></tr><tr><td id="name">Catalog 
Name</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">The name of the catalog that the statement should update. This 
may not apply for the database that you are updating. In this case, leave the 
field empty<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Schema Name</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
name of the schema that the table belongs to. This may not apply for the 
database that you are updating. In this case, leave the field 
empty<br/><strong>Supports Expression Language: true</strong></td></tr><tr>
 <td id="name">Translate Field Names</td><td id="default-value">true</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">If true, the Processor will attempt to translate JSON field 
names into the appropriate column names for the table specified. If false, the 
JSON field names must match the column names exactly, or the column will not be 
updated</td></tr><tr><td id="name">Unmatched Field Behavior</td><td 
id="default-value">Ignore Unmatched Fields</td><td 
id="allowable-values"><ul><li>Ignore Unmatched Fields <img 
src="../../html/images/iconInfo.png" alt="Any field in the JSON document that 
cannot be mapped to a column in the database is ignored" title="Any field in 
the JSON document that cannot be mapped to a column in the database is 
ignored"></img></li><li>Fail <img src="../../html/images/iconInfo.png" alt="If 
the JSON document has any field that cannot be mapped to a column in the 
database, the FlowFile will be routed to the failure relations
 hip" title="If the JSON document has any field that cannot be mapped to a 
column in the database, the FlowFile will be routed to the failure 
relationship"></img></li></ul></td><td id="description">If an incoming JSON 
element has a field that does not map to any of the database table's columns, 
this property specifies how to handle the situation</td></tr><tr><td 
id="name">Unmatched Column Behavior</td><td id="default-value">Fail on 
Unmatched Columns</td><td id="allowable-values"><ul><li>Ignore Unmatched 
Columns <img src="../../html/images/iconInfo.png" alt="Any column in the 
database that does not have a field in the JSON document will be assumed to not 
be required.  No notification will be logged" title="Any column in the database 
that does not have a field in the JSON document will be assumed to not be 
required.  No notification will be logged"></img></li><li>Warn on Unmatched 
Columns <img src="../../html/images/iconInfo.png" alt="Any column in the 
database that does not have a fie
 ld in the JSON document will be assumed to not be required.  A warning will be 
logged" title="Any column in the database that does not have a field in the 
JSON document will be assumed to not be required.  A warning will be 
logged"></img></li><li>Fail on Unmatched Columns <img 
src="../../html/images/iconInfo.png" alt="A flow will fail if any column in the 
database that does not have a field in the JSON document.  An error will be 
logged" title="A flow will fail if any column in the database that does not 
have a field in the JSON document.  An error will be 
logged"></img></li></ul></td><td id="description">If an incoming JSON element 
does not have a field mapping for all of the database table's columns, this 
property specifies how to handle the situation</td></tr><tr><td 
id="name">Update Keys</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">A comma-separated list of 
column names that uniquely identifies a row in the database for UPDATE 
statements. I
 f the Statement Type is UPDATE and this property is not set, the table's 
Primary Keys are used. In this case, if no Primary Key exists, the conversion 
to SQL will fail if Unmatched Column Behaviour is set to FAIL. This property is 
ignored if the Statement Type is INSERT<br/><strong>Supports Expression 
Language: true</strong></td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>sql</td><td>A
 FlowFile is routed to this relationship when its contents have successfully 
been converted into a SQL statement</td></tr><tr><td>failure</td><td>A FlowFile 
is routed to this relationship if it cannot be converted into a SQL statement. 
Common causes include invalid JSON content or the JSON content missing a 
required field (if using an INSERT statement 
type).</td></tr><tr><td>original</td><td>When a FlowFile is converted to SQL, 
the original JSON FlowFile is routed to this 
relationship</td></tr></table><h3>Reads Attributes: </h3>None s
 pecified.<h3>Writes Attributes: </h3><table 
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>mime.type</td><td>Sets
 mime.type of FlowFile that is routed to 'sql' to 
'text/plain'.</td></tr><tr><td>sql.table</td><td>Sets the sql.table attribute 
of FlowFile that is routed to 'sql' to the name of the table that is updated by 
the SQL statement.</td></tr><tr><td>sql.catalog</td><td>If the Catalog name is 
set for this database, specifies the name of the catalog that the SQL statement 
will update. If no catalog is used, this attribute will not be 
added.</td></tr><tr><td>fragment.identifier</td><td>All FlowFiles routed to the 
'sql' relationship for the same incoming FlowFile (multiple will be output for 
the same incoming FlowFile if the incoming FlowFile is a JSON Array) will have 
the same value for the fragment.identifier attribute. This can then be used to 
correlate the results.</td></tr><tr><td>fragment.count</td><td>The number of 
SQL FlowFiles that were produced f
 or same incoming FlowFile. This can be used in conjunction with the 
fragment.identifier attribute in order to know how many FlowFiles belonged to 
the same incoming FlowFile.</td></tr><tr><td>fragment.index</td><td>The 
position of this FlowFile in the list of outgoing FlowFiles that were all 
derived from the same incoming FlowFile. This can be used in conjunction with 
the fragment.identifier and fragment.count attributes to know which FlowFiles 
originated from the same incoming FlowFile and in what order the SQL FlowFiles 
were produced</td></tr><tr><td>sql.args.N.type</td><td>The output SQL 
statements are parameterized in order to avoid SQL Injection Attacks. The types 
of the Parameters to use are stored in attributes named sql.args.1.type, 
sql.args.2.type, sql.args.3.type, and so on. The type is a number representing 
a JDBC Type constant. Generally, this is useful only for software to read and 
interpret but is added so that a processor such as PutSQL can understand how to 
interpret 
 the values.</td></tr><tr><td>sql.args.N.value</td><td>The output SQL 
statements are parameterized in order to avoid SQL Injection Attacks. The 
values of the Parameters to use are stored in the attributes named 
sql.args.1.value, sql.args.2.value, sql.args.3.value, and so on. Each of these 
attributes has a corresponding sql.args.N.type attribute that indicates how the 
value should be interpreted when inserting it into the 
database.</td></tr></table><h3>See Also:</h3><p><a 
href="../org.apache.nifi.processors.standard.PutSQL/index.html">PutSQL</a></p></body></html>
\ No newline at end of file

Modified: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.DetectDuplicate/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.DetectDuplicate/index.html?rev=1730777&r1=1730776&r2=1730777&view=diff
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.DetectDuplicate/index.html
 (original)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.DetectDuplicate/index.html
 Wed Feb 17 02:20:53 2016
@@ -1 +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><body><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 
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/expressi
 on-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 Exp
 ression 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="../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></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 
Identifi
 er 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 Attributes: </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>See Also:</h3><p><a 
href="../org.apache.nifi.distributed.cache.client.DistributedMapCacheClientService/index.html">DistributedMapCacheClientService</a>,
 <a 
href="../org.apache.nifi.distributed.cache.server.map.DistributedMapCacheServer/index.html">DistributedMapCacheServer</a></p></body></html>
\ No newline at end of file
+<!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><body><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 
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/express
 ion-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 Ex
 pression 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="../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 woul
 d 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 Attributes: </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>See Also:</h3><p><a 
href="../org.apache.nifi.distributed.cache.client.DistributedMapCacheClientService/index.html">DistributedMapCacheClientService</a>,
 <a 
href="../org.apache.nifi.distributed.cache.server.map.DistributedMapCacheServer/index.html">DistributedMapCacheServer</a></p></body></html>
\ No newline at end of file


Reply via email to