Modified: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ListFile/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ListFile/index.html?rev=1730777&r1=1730776&r2=1730777&view=diff
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ListFile/index.html
 (original)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ListFile/index.html
 Wed Feb 17 02:20:53 2016
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ListFile</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 the local filesystem. For each file that is listed, 
creates a FlowFile that represents the file so that it can be fetched in 
conjunction with ListFile. 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 
GetFile, this Processor does not delete any data from the local 
filesystem.</p><h3>Tags: </h3><p>file, 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, and 
whether a property supports th
 e <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>Input Directory</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The input directory from which 
files to pull files<br/><strong>Supports Expression Language: 
true</strong></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 
directory</td></tr><tr><td id="name"><strong>File Filter</strong></td><td 
id="default-value">[^\.].*</td><td id="allowable-values"></td><td 
id="description">Only files whose names match the given regular expression will 
be picked up</td></tr><tr><td id="name">Path Filter</td><td 
id="default-value"></td><t
 d id="allowable-values"></td><td id="description">When Recurse Subdirectories 
is true, then only subdirectories whose path matches the given regular 
expression will be scanned</td></tr><tr><td id="name"><strong>Minimum File 
Age</strong></td><td id="default-value">0 sec</td><td 
id="allowable-values"></td><td id="description">The minimum age that a file 
must be in order to be pulled; any file younger than this amount of time 
(according to last modification date) will be ignored</td></tr><tr><td 
id="name">Maximum File Age</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The maximum age that a file 
must be in order to be pulled; any file older than this amount of time 
(according to last modification date) will be ignored</td></tr><tr><td 
id="name"><strong>Minimum File Size</strong></td><td id="default-value">0 
B</td><td id="allowable-values"></td><td id="description">The minimum size that 
a file must be in order to be pulled</td></tr><tr><td id="name">
 Maximum File Size</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The maximum size that a file 
can be in order to be pulled</td></tr><tr><td id="name"><strong>Ignore Hidden 
Files</strong></td><td id="default-value">true</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Indicates whether or not hidden files should be 
ignored</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>All
 FlowFiles that are received are routed to success</td></tr></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 
filesystem.</td></tr><tr><td>path</td><td>The path is set to the relative path 
of the file's directory on filesystem compared to the Input Directory property. 
 For example, if Input 
 Directory 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 
"abc/1/2/3/".</td></tr><tr><td>absolute.path</td><td>The absolute.path is set 
to the absolute path of the file's directory on filesystem. For example, if the 
Input Directory property is set to /tmp, then files picked up from /tmp will 
have the path attribute set to "/tmp/". 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>fs.owner</td><td>The user that owns the 
file in filesystem</td></tr><tr><td>fs.group</td><td>The group that owns the 
file in filesystem</td></tr><tr><td>fs.lastModified</td><td>The timestamp of 
when the file in filesystem was last modified, as milliseconds since midnight 
Jan 1, 1970 UTC</td></tr><tr><td>fs.leng
 th</td><td>The number of bytes in the file in 
filesystem</td></tr><tr><td>fs.permissions</td><td>The permissions for the file 
in filesystem. 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.standard.GetFile/index.html">GetFile</a>, 
<a 
href="../org.apache.nifi.processors.standard.PutFile/index.html">PutFile</a>, 
<a 
href="../org.apache.nifi.processors.standard.FetchFile/index.html">FetchFile</a></p></body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ListFile</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 the local filesystem. For each file that is listed, 
creates a FlowFile that represents the file so that it can be fetched in 
conjunction with ListFile. 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 
GetFile, this Processor does not delete any data from the local 
filesystem.</p><h3>Tags: </h3><p>file, 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, and 
whether a property supports th
 e <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>Input Directory</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The input directory from which 
files to pull files<br/><strong>Supports Expression Language: 
true</strong></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 
directory</td></tr><tr><td id="name"><strong>Input Directory 
Location</strong></td><td id="default-value">Local</td><td 
id="allowable-values"><ul><li>Local <img src="../../html/images/iconInfo.png" 
alt="Input Directory is located on a local disk. State will be stored locally 
on each node in the cluster." 
 title="Input Directory is located on a local disk. State will be stored 
locally on each node in the cluster."></img></li><li>Remote <img 
src="../../html/images/iconInfo.png" alt="Input Directory is located on a 
remote system. State will be stored across the cluster so that the listing can 
be performed on Primary Node Only and another node can pick up where the last 
node left off, if the Primary Node changes" title="Input Directory is located 
on a remote system. State will be stored across the cluster so that the listing 
can be performed on Primary Node Only and another node can pick up where the 
last node left off, if the Primary Node changes"></img></li></ul></td><td 
id="description">Specifies where the Input Directory is located. This is used 
to determine whether state should be stored locally or across the 
cluster.</td></tr><tr><td id="name"><strong>File Filter</strong></td><td 
id="default-value">[^\.].*</td><td id="allowable-values"></td><td 
id="description">Only files whose nam
 es match the given regular expression will be picked up</td></tr><tr><td 
id="name">Path Filter</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">When Recurse Subdirectories is 
true, then only subdirectories whose path matches the given regular expression 
will be scanned</td></tr><tr><td id="name"><strong>Minimum File 
Age</strong></td><td id="default-value">0 sec</td><td 
id="allowable-values"></td><td id="description">The minimum age that a file 
must be in order to be pulled; any file younger than this amount of time 
(according to last modification date) will be ignored</td></tr><tr><td 
id="name">Maximum File Age</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The maximum age that a file 
must be in order to be pulled; any file older than this amount of time 
(according to last modification date) will be ignored</td></tr><tr><td 
id="name"><strong>Minimum File Size</strong></td><td id="default-value">0 
B</td><td id="a
 llowable-values"></td><td id="description">The minimum size that a file must 
be in order to be pulled</td></tr><tr><td id="name">Maximum File Size</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
maximum size that a file can be in order to be pulled</td></tr><tr><td 
id="name"><strong>Ignore Hidden Files</strong></td><td 
id="default-value">true</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Indicates whether or not hidden files should be 
ignored</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>All
 FlowFiles that are received are routed to success</td></tr></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 
filesystem.</td></tr><tr><td>path</td><td>The path is
  set to the relative path of the file's directory on filesystem compared to 
the Input Directory property.  For example, if Input Directory 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 
"abc/1/2/3/".</td></tr><tr><td>absolute.path</td><td>The absolute.path is set 
to the absolute path of the file's directory on filesystem. For example, if the 
Input Directory property is set to /tmp, then files picked up from /tmp will 
have the path attribute set to "/tmp/". 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>fs.owner</td><td>The user that owns the 
file in filesystem</td></tr><tr><td>fs.group</td><td>The group that owns the 
file in filesystem</td></tr><tr><td>fs.lastModified</td><td>The ti
 mestamp of when the file in filesystem was last modified, as milliseconds 
since midnight Jan 1, 1970 UTC</td></tr><tr><td>fs.length</td><td>The number of 
bytes in the file in filesystem</td></tr><tr><td>fs.permissions</td><td>The 
permissions for the file in filesystem. 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.standard.GetFile/index.html">GetFile</a>, 
<a 
href="../org.apache.nifi.processors.standard.PutFile/index.html">PutFile</a>, 
<a 
href="../org.apache.nifi.processors.standard.FetchFile/index.html">FetchFile</a></p></body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ListenRELP/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ListenRELP/index.html?rev=1730777&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ListenRELP/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ListenRELP/index.html
 Wed Feb 17 02:20:53 2016
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ListenRELP</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Listens for RELP 
messages being sent to a given port over TCP. Each message will be acknowledged 
after successfully writing the message to a FlowFile. Each FlowFile will 
contain data portion of one or more RELP frames. In the case where the RELP 
frames contain syslog messages, the output of this processor can be sent to a 
ParseSyslog processor for further processing.</p><h3>Tags: </h3><p>listen, 
relp, tcp, logs</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>Port</strong
 ></td><td id="default-value"></td><td id="allowable-values"></td><td 
 >id="description">The port to listen on for communication.</td></tr><tr><td 
 >id="name"><strong>Receive Buffer Size</strong></td><td 
 >id="default-value">65507 B</td><td id="allowable-values"></td><td 
 >id="description">The size of each buffer used to receive messages. Adjust 
 >this value appropriately based on the expected size of the incoming 
 >messages.</td></tr><tr><td id="name"><strong>Max Size of Socket 
 >Buffer</strong></td><td id="default-value">1 MB</td><td 
 >id="allowable-values"></td><td id="description">The maximum size of the 
 >socket buffer that should be used. This is a suggestion to the Operating 
 >System to indicate how big the socket buffer should be. If this value is set 
 >too low, the buffer may fill up before the data can be read, and incoming 
 >data will be dropped.</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">Speci
 fies the character set of the received data.</td></tr><tr><td 
id="name"><strong>Max Number of TCP Connections</strong></td><td 
id="default-value">2</td><td id="allowable-values"></td><td 
id="description">The maximum number of concurrent TCP connections to 
accept.</td></tr><tr><td id="name"><strong>Max Batch Size</strong></td><td 
id="default-value">1</td><td id="allowable-values"></td><td 
id="description">The maximum number of messages to add to a single FlowFile. If 
multiple messages are available, they will be concatenated along with the 
&lt;Message Delimiter&gt; up to this configured maximum number of 
messages</td></tr><tr><td id="name"><strong>Message Delimiter</strong></td><td 
id="default-value">\n</td><td id="allowable-values"></td><td 
id="description">Specifies the delimiter to place between messages when 
multiple messages are bundled together (see &lt;Max Batch Size&gt; 
property).</td></tr><tr><td id="name">SSL Context Service</td><td 
id="default-value"></td><td id="allowable
 -values"><strong>Controller Service API: 
</strong><br/>SSLContextService<br/><strong>Implementation:</strong><br/><a 
href="../org.apache.nifi.ssl.StandardSSLContextService/index.html">StandardSSLContextService</a></td><td
 id="description">The Controller Service to use in order to obtain an SSL 
Context. If this property is set, messages will be received over a secure 
connection.</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>Messages
 received successfully will be sent out 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>relp.command</td><td>The
 command of the RELP frames.</td></tr><tr><td>relp.sender</td><td>The sending 
host of the messages.</td></tr><tr><td>relp.port</td><td>The sending port the 
messages were received over.</td></tr><tr><td>relp.txnr</td><td>The t
 ransaction number of the message. Only included if &lt;Batch Size&gt; is 
1.</td></tr><tr><td>mime.type</td><td>The mime.type of the content which is 
text/plain</td></tr></table><h3>See Also:</h3><p><a 
href="../org.apache.nifi.processors.standard.ParseSyslog/index.html">ParseSyslog</a></p></body></html>
\ No newline at end of file

Modified: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ListenSyslog/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ListenSyslog/index.html?rev=1730777&r1=1730776&r2=1730777&view=diff
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ListenSyslog/index.html
 (original)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ListenSyslog/index.html
 Wed Feb 17 02:20:53 2016
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ListenSyslog</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Listens for Syslog 
messages being sent to a given port over TCP or UDP. Incoming messages are 
checked against regular expressions for RFC5424 and RFC3164 formatted messages. 
The format of each message is: (&lt;PRIORITY&gt;)(VERSION )(TIMESTAMP) 
(HOSTNAME) (BODY) where version is optional. The timestamp can be an RFC5424 
timestamp with a format of "yyyy-MM-dd'T'HH:mm:ss.SZ" or 
"yyyy-MM-dd'T'HH:mm:ss.S+hh:mm", or it can be an RFC3164 timestamp with a 
format of "MMM d HH:mm:ss". If an incoming messages matches one of these 
patterns, the message will be parsed and the individual pieces will be placed 
in FlowFile attributes, with the original message in the content of the 
FlowFile. If an incoming message does not match one of these patterns it will 
not be parsed and the syslog.
 valid attribute will be set to false with the original message in the content 
of the FlowFile. Valid messages will be transferred on the success 
relationship, and invalid messages will be transferred on the invalid 
relationship.</p><h3>Tags: </h3><p>syslog, listen, udp, tcp, 
logs</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>Protocol</strong></td><td id="default-value">UDP</td><td 
id="allowable-values"><ul><li>TCP</li><li>UDP</li></ul></td><td 
id="description">The protocol for Syslog communication, either TCP or 
UDP.</td></tr><tr><td id="name"><strong>Port</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
port for Syslog communica
 tion.</td></tr><tr><td id="name">SSL Context Service</td><td 
id="default-value"></td><td id="allowable-values"><strong>Controller Service 
API: 
</strong><br/>SSLContextService<br/><strong>Implementation:</strong><br/><a 
href="../org.apache.nifi.ssl.StandardSSLContextService/index.html">StandardSSLContextService</a></td><td
 id="description">The Controller Service to use in order to obtain an SSL 
Context. If this property is set, syslog messages will be received over a 
secure connection.</td></tr><tr><td id="name"><strong>Receive Buffer 
Size</strong></td><td id="default-value">65507 B</td><td 
id="allowable-values"></td><td id="description">The size of each buffer used to 
receive Syslog messages. Adjust this value appropriately based on the expected 
size of the incoming Syslog messages. When UDP is selected each buffer will 
hold one Syslog message. When TCP is selected messages are read from an 
incoming connection until the buffer is full, or the connection is closed. 
</td></tr><tr><td 
 id="name"><strong>Max Size of Socket Buffer</strong></td><td 
id="default-value">1 MB</td><td id="allowable-values"></td><td 
id="description">The maximum size of the socket buffer that should be used. 
This is a suggestion to the Operating System to indicate how big the socket 
buffer should be. If this value is set too low, the buffer may fill up before 
the data can be read, and incoming data will be dropped.</td></tr><tr><td 
id="name"><strong>Max Number of TCP Connections</strong></td><td 
id="default-value">2</td><td id="allowable-values"></td><td 
id="description">The maximum number of concurrent connections to accept Syslog 
messages in TCP mode.</td></tr><tr><td id="name"><strong>Max Batch 
Size</strong></td><td id="default-value">1</td><td 
id="allowable-values"></td><td id="description">The maximum number of Syslog 
events to add to a single FlowFile. If multiple events are available, they will 
be concatenated along with the &lt;Message Delimiter&gt; up to this configured 
maximum num
 ber of messages</td></tr><tr><td id="name"><strong>Message 
Delimiter</strong></td><td id="default-value">\n</td><td 
id="allowable-values"></td><td id="description">Specifies the delimiter to 
place between Syslog messages when multiple messages are bundled together (see 
&lt;Max Batch Size&gt; property).</td></tr><tr><td id="name"><strong>Parse 
Messages</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 if the processor should parse the Syslog messages. 
If set to false, each outgoing FlowFile will only contain the sender, protocol, 
and port, and no additional attributes.</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 which character set of the Syslog 
messages</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td>
 <td>Syslog messages that match one of the expected formats will be sent out 
this relationship as a FlowFile per 
message.</td></tr><tr><td>invalid</td><td>Syslog messages that do not match one 
of the expected formats will be sent out this relationship as a FlowFile per 
message.</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>syslog.priority</td><td>The
 priority of the Syslog message.</td></tr><tr><td>syslog.severity</td><td>The 
severity of the Syslog message derived from the 
priority.</td></tr><tr><td>syslog.facility</td><td>The facility of the Syslog 
message derived from the priority.</td></tr><tr><td>syslog.version</td><td>The 
optional version from the Syslog 
message.</td></tr><tr><td>syslog.timestamp</td><td>The timestamp of the Syslog 
message.</td></tr><tr><td>syslog.hostname</td><td>The hostname of the Syslog 
message.</td></tr><tr><td>syslog.sender</td><td>The h
 ostname of the Syslog server that sent the 
message.</td></tr><tr><td>syslog.body</td><td>The body of the Syslog message, 
everything after the hostname.</td></tr><tr><td>syslog.valid</td><td>An 
indicator of whether this message matched the expected formats. If this value 
is false, the other attributes will be empty and only the original message will 
be available in the content.</td></tr><tr><td>syslog.protocol</td><td>The 
protocol over which the Syslog message was 
received.</td></tr><tr><td>syslog.port</td><td>The port over which the Syslog 
message was received.</td></tr><tr><td>mime.type</td><td>The mime.type of the 
FlowFile which will be text/plain for Syslog messages.</td></tr></table><h3>See 
Also:</h3><p><a 
href="../org.apache.nifi.processors.standard.PutSyslog/index.html">PutSyslog</a>,
 <a 
href="../org.apache.nifi.processors.standard.ParseSyslog/index.html">ParseSyslog</a></p></body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ListenSyslog</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Listens for Syslog 
messages being sent to a given port over TCP or UDP. Incoming messages are 
checked against regular expressions for RFC5424 and RFC3164 formatted messages. 
The format of each message is: (&lt;PRIORITY&gt;)(VERSION )(TIMESTAMP) 
(HOSTNAME) (BODY) where version is optional. The timestamp can be an RFC5424 
timestamp with a format of "yyyy-MM-dd'T'HH:mm:ss.SZ" or 
"yyyy-MM-dd'T'HH:mm:ss.S+hh:mm", or it can be an RFC3164 timestamp with a 
format of "MMM d HH:mm:ss". If an incoming messages matches one of these 
patterns, the message will be parsed and the individual pieces will be placed 
in FlowFile attributes, with the original message in the content of the 
FlowFile. If an incoming message does not match one of these patterns it will 
not be parsed and the syslog.
 valid attribute will be set to false with the original message in the content 
of the FlowFile. Valid messages will be transferred on the success 
relationship, and invalid messages will be transferred on the invalid 
relationship.</p><h3>Tags: </h3><p>syslog, listen, udp, tcp, 
logs</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>Protocol</strong></td><td id="default-value">UDP</td><td 
id="allowable-values"><ul><li>TCP</li><li>UDP</li></ul></td><td 
id="description">The protocol for Syslog communication.</td></tr><tr><td 
id="name"><strong>Port</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The port for Syslog 
communication.</td></tr><tr>
 <td id="name">SSL Context Service</td><td id="default-value"></td><td 
id="allowable-values"><strong>Controller Service API: 
</strong><br/>SSLContextService<br/><strong>Implementation:</strong><br/><a 
href="../org.apache.nifi.ssl.StandardSSLContextService/index.html">StandardSSLContextService</a></td><td
 id="description">The Controller Service to use in order to obtain an SSL 
Context. If this property is set, syslog messages will be received over a 
secure connection.</td></tr><tr><td id="name"><strong>Receive Buffer 
Size</strong></td><td id="default-value">65507 B</td><td 
id="allowable-values"></td><td id="description">The size of each buffer used to 
receive Syslog messages. Adjust this value appropriately based on the expected 
size of the incoming Syslog messages. When UDP is selected each buffer will 
hold one Syslog message. When TCP is selected messages are read from an 
incoming connection until the buffer is full, or the connection is closed. 
</td></tr><tr><td id="name"><strong>M
 ax Size of Socket Buffer</strong></td><td id="default-value">1 MB</td><td 
id="allowable-values"></td><td id="description">The maximum size of the socket 
buffer that should be used. This is a suggestion to the Operating System to 
indicate how big the socket buffer should be. If this value is set too low, the 
buffer may fill up before the data can be read, and incoming data will be 
dropped.</td></tr><tr><td id="name"><strong>Max Number of TCP 
Connections</strong></td><td id="default-value">2</td><td 
id="allowable-values"></td><td id="description">The maximum number of 
concurrent connections to accept Syslog messages in TCP mode.</td></tr><tr><td 
id="name"><strong>Max Batch Size</strong></td><td id="default-value">1</td><td 
id="allowable-values"></td><td id="description">The maximum number of Syslog 
events to add to a single FlowFile. If multiple events are available, they will 
be concatenated along with the &lt;Message Delimiter&gt; up to this configured 
maximum number of messages</td
 ></tr><tr><td id="name"><strong>Message Delimiter</strong></td><td 
 >id="default-value">\n</td><td id="allowable-values"></td><td 
 >id="description">Specifies the delimiter to place between Syslog messages 
 >when multiple messages are bundled together (see &lt;Max Batch Size&gt; 
 >property).</td></tr><tr><td id="name"><strong>Parse Messages</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 if the processor should parse the Syslog messages. 
 >If set to false, each outgoing FlowFile will only contain the sender, 
 >protocol, and port, and no additional attributes.</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 Syslog 
 >messages</td></tr></table><h3>Relationships: </h3><table 
 >id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>Syslog
 > messages t
 hat match one of the expected formats will be sent out this relationship as a 
FlowFile per message.</td></tr><tr><td>invalid</td><td>Syslog messages that do 
not match one of the expected formats will be sent out this relationship as a 
FlowFile per message.</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>syslog.priority</td><td>The
 priority of the Syslog message.</td></tr><tr><td>syslog.severity</td><td>The 
severity of the Syslog message derived from the 
priority.</td></tr><tr><td>syslog.facility</td><td>The facility of the Syslog 
message derived from the priority.</td></tr><tr><td>syslog.version</td><td>The 
optional version from the Syslog 
message.</td></tr><tr><td>syslog.timestamp</td><td>The timestamp of the Syslog 
message.</td></tr><tr><td>syslog.hostname</td><td>The hostname of the Syslog 
message.</td></tr><tr><td>syslog.sender</td><td>The hostname of the Syslog
  server that sent the message.</td></tr><tr><td>syslog.body</td><td>The body 
of the Syslog message, everything after the 
hostname.</td></tr><tr><td>syslog.valid</td><td>An indicator of whether this 
message matched the expected formats. If this value is false, the other 
attributes will be empty and only the original message will be available in the 
content.</td></tr><tr><td>syslog.protocol</td><td>The protocol over which the 
Syslog message was received.</td></tr><tr><td>syslog.port</td><td>The port over 
which the Syslog message was received.</td></tr><tr><td>mime.type</td><td>The 
mime.type of the FlowFile which will be text/plain for Syslog 
messages.</td></tr></table><h3>See Also:</h3><p><a 
href="../org.apache.nifi.processors.standard.PutSyslog/index.html">PutSyslog</a>,
 <a 
href="../org.apache.nifi.processors.standard.ParseSyslog/index.html">ParseSyslog</a></p></body></html>
\ No newline at end of file

Modified: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.MergeContent/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.MergeContent/index.html?rev=1730777&r1=1730776&r2=1730777&view=diff
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.MergeContent/index.html
 (original)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.MergeContent/index.html
 Wed Feb 17 02:20:53 2016
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>MergeContent</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Merges a Group of 
FlowFiles together based on a user-defined strategy and packages them into a 
single FlowFile. It is recommended that the Processor be configured with only a 
single incoming connection, as Group of FlowFiles will not be created from 
FlowFiles in different connections. This processor updates the mime.type 
attribute as appropriate.</p><h3>Tags: </h3><p>merge, content, correlation, 
tar, zip, stream, concatenation, archive, flowfile-stream, 
flowfile-stream-v3</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">N
 iFi 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>Merge 
Strategy</strong></td><td id="default-value">Bin-Packing Algorithm</td><td 
id="allowable-values"><ul><li>Bin-Packing Algorithm <img 
src="../../html/images/iconInfo.png" alt="Generates 'bins' of FlowFiles and 
fills each bin as full as possible. FlowFiles are placed into a bin based on 
their size and optionally their attributes (if the &lt;Correlation 
Attribute&gt; property is set)" title="Generates 'bins' of FlowFiles and fills 
each bin as full as possible. FlowFiles are placed into a bin based on their 
size and optionally their attributes (if the &lt;Correlation Attribute&gt; 
property is set)"></img></li><li>Defragment <img 
src="../../html/images/iconInfo.png" alt="Combines fragments that are 
associated by attributes back into a single cohesive FlowFile. If using this 
strategy, all FlowFiles must have the attr
 ibutes &lt;fragment.identifier&gt;, &lt;fragment.count&gt;, and 
&lt;fragment.index&gt; or alternatively (for backward compatibility purposes) 
&lt;segment.identifier&gt;, &lt;segment.count&gt;, and &lt;segment.index&gt;. 
All FlowFiles with the same value for &quot;fragment.identifier&quot; will be 
grouped together. All FlowFiles in this group must have the same value for the 
&quot;fragment.count&quot; attribute. All FlowFiles in this group must have a 
unique value for the &quot;fragment.index&quot; attribute between 0 and the 
value of the &quot;fragment.count&quot; attribute." title="Combines fragments 
that are associated by attributes back into a single cohesive FlowFile. If 
using this strategy, all FlowFiles must have the attributes 
&lt;fragment.identifier&gt;, &lt;fragment.count&gt;, and &lt;fragment.index&gt; 
or alternatively (for backward compatibility purposes) 
&lt;segment.identifier&gt;, &lt;segment.count&gt;, and &lt;segment.index&gt;. 
All FlowFiles with the same value for &q
 uot;fragment.identifier&quot; will be grouped together. All FlowFiles in this 
group must have the same value for the &quot;fragment.count&quot; attribute. 
All FlowFiles in this group must have a unique value for the 
&quot;fragment.index&quot; attribute between 0 and the value of the 
&quot;fragment.count&quot; attribute."></img></li></ul></td><td 
id="description">Specifies the algorithm used to merge content. The 
'Defragment' algorithm combines fragments that are associated by attributes 
back into a single cohesive FlowFile. The 'Bin-Packing Algorithm' generates a 
FlowFile populated by arbitrarily chosen FlowFiles</td></tr><tr><td 
id="name"><strong>Merge Format</strong></td><td id="default-value">Binary 
Concatenation</td><td id="allowable-values"><ul><li>TAR <img 
src="../../html/images/iconInfo.png" alt="A bin of FlowFiles will be combined 
into a single TAR file. The FlowFiles' &lt;path&gt; attribute will be used to 
create a directory in the TAR file if the &lt;Keep Paths&gt; propert
 y is set to true; otherwise, all FlowFiles will be added at the root of the 
TAR file. If a FlowFile has an attribute named &lt;tar.permissions&gt; that is 
3 characters, each between 0-7, that attribute will be used as the TAR entry's 
'mode'." title="A bin of FlowFiles will be combined into a single TAR file. The 
FlowFiles' &lt;path&gt; attribute will be used to create a directory in the TAR 
file if the &lt;Keep Paths&gt; property is set to true; otherwise, all 
FlowFiles will be added at the root of the TAR file. If a FlowFile has an 
attribute named &lt;tar.permissions&gt; that is 3 characters, each between 0-7, 
that attribute will be used as the TAR entry's 'mode'."></img></li><li>ZIP <img 
src="../../html/images/iconInfo.png" alt="A bin of FlowFiles will be combined 
into a single ZIP file. The FlowFiles' &lt;path&gt; attribute will be used to 
create a directory in the ZIP file if the &lt;Keep Paths&gt; property is set to 
true; otherwise, all FlowFiles will be added at the root of th
 e ZIP file. The &lt;Compression Level&gt; property indicates the ZIP 
compression to use." title="A bin of FlowFiles will be combined into a single 
ZIP file. The FlowFiles' &lt;path&gt; attribute will be used to create a 
directory in the ZIP file if the &lt;Keep Paths&gt; property is set to true; 
otherwise, all FlowFiles will be added at the root of the ZIP file. The 
&lt;Compression Level&gt; property indicates the ZIP compression to 
use."></img></li><li>FlowFile Stream, v3 <img 
src="../../html/images/iconInfo.png" alt="A bin of FlowFiles will be combined 
into a single Version 3 FlowFile Stream" title="A bin of FlowFiles will be 
combined into a single Version 3 FlowFile Stream"></img></li><li>FlowFile 
Stream, v2 <img src="../../html/images/iconInfo.png" alt="A bin of FlowFiles 
will be combined into a single Version 2 FlowFile Stream" title="A bin of 
FlowFiles will be combined into a single Version 2 FlowFile 
Stream"></img></li><li>FlowFile Tar, v1 <img src="../../html/images/iconInfo
 .png" alt="A bin of FlowFiles will be combined into a single Version 1 
FlowFile Package" title="A bin of FlowFiles will be combined into a single 
Version 1 FlowFile Package"></img></li><li>Binary Concatenation <img 
src="../../html/images/iconInfo.png" alt="The contents of all FlowFiles will be 
concatenated together into a single FlowFile" title="The contents of all 
FlowFiles will be concatenated together into a single 
FlowFile"></img></li><li>Avro <img src="../../html/images/iconInfo.png" 
alt="The Avro contents of all FlowFiles will be concatenated together into a 
single FlowFile" title="The Avro contents of all FlowFiles will be concatenated 
together into a single FlowFile"></img></li></ul></td><td 
id="description">Determines the format that will be used to merge the 
content.</td></tr><tr><td id="name"><strong>Attribute Strategy</strong></td><td 
id="default-value">Keep Only Common Attributes</td><td 
id="allowable-values"><ul><li>Keep Only Common Attributes</li><li>Keep All 
Unique A
 ttributes</li></ul></td><td id="description">Determines which FlowFile 
attributes should be added to the bundle. If 'Keep All Unique Attributes' is 
selected, any attribute on any FlowFile that gets bundled will be kept unless 
its value conflicts with the value from another FlowFile. If 'Keep Only Common 
Attributes' is selected, only the attributes that exist on all FlowFiles in the 
bundle, with the same value, will be preserved.</td></tr><tr><td 
id="name">Correlation Attribute Name</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">If specified, like FlowFiles 
will be binned together, where 'like FlowFiles' means FlowFiles that have the 
same value for this Attribute. If not specified, FlowFiles are bundled by the 
order in which they are pulled from the queue.</td></tr><tr><td 
id="name"><strong>Minimum Number of Entries</strong></td><td 
id="default-value">1</td><td id="allowable-values"></td><td 
id="description">The minimum number of files to include 
 in a bundle</td></tr><tr><td id="name">Maximum Number of Entries</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
maximum number of files to include in a bundle. If not specified, there is no 
maximum.</td></tr><tr><td id="name"><strong>Minimum Group Size</strong></td><td 
id="default-value">0 B</td><td id="allowable-values"></td><td 
id="description">The minimum size of for the bundle</td></tr><tr><td 
id="name">Maximum Group Size</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The maximum size for the 
bundle. If not specified, there is no maximum.</td></tr><tr><td id="name">Max 
Bin Age</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">The maximum age of a Bin that will trigger a Bin to be 
complete. Expected format is &lt;duration&gt; &lt;time unit&gt; where 
&lt;duration&gt; is a positive integer and time unit is one of seconds, 
minutes, hours</td></tr><tr><td id="name"><strong>
 Maximum number of Bins</strong></td><td id="default-value">100</td><td 
id="allowable-values"></td><td id="description">Specifies the maximum number of 
bins that can be held in memory at any one time</td></tr><tr><td 
id="name"><strong>Delimiter Strategy</strong></td><td 
id="default-value">Filename</td><td id="allowable-values"><ul><li>Filename <img 
src="../../html/images/iconInfo.png" alt="The values of Header, Footer, and 
Demarcator will be retrieved from the contents of a file" title="The values of 
Header, Footer, and Demarcator will be retrieved from the contents of a 
file"></img></li><li>Text <img src="../../html/images/iconInfo.png" alt="The 
values of Header, Footer, and Demarcator will be specified as property values" 
title="The values of Header, Footer, and Demarcator will be specified as 
property values"></img></li></ul></td><td id="description">Determines if 
Header, Footer, and Demarcator should point to files containing the respective 
content, or if the values of the proper
 ties should be used as the content.</td></tr><tr><td id="name">Header</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Filename specifying the header to use. If not specified, no 
header is supplied. This property is valid only when using the 
binary-concatenation merge strategy; otherwise, it is 
ignored.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Footer</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Filename specifying the footer to use. If not specified, no 
footer is supplied. This property is valid only when using the 
binary-concatenation merge strategy; otherwise, it is 
ignored.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Demarcator</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Filename specifying the demarcator to use. If not specified, 
no demarcator is supplied. This property is valid only whe
 n using the binary-concatenation merge strategy; otherwise, it is 
ignored.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Compression 
Level</strong></td><td id="default-value">1</td><td 
id="allowable-values"><ul><li>0</li><li>1</li><li>2</li><li>3</li><li>4</li><li>5</li><li>6</li><li>7</li><li>8</li><li>9</li></ul></td><td
 id="description">Specifies the compression level to use when using the Zip 
Merge Format; if not using the Zip Merge Format, this value is 
ignored</td></tr><tr><td id="name"><strong>Keep Path</strong></td><td 
id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">If using the Zip or Tar Merge Format, specifies whether or not 
the FlowFiles' paths should be included in their entry names; if using other 
merge strategy, this value is ignored</td></tr></table><h3>Relationships: 
</h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>failure
 </td><td>If the bundle cannot be created, all FlowFiles that would have been 
used to created the bundle will be transferred to 
failure</td></tr><tr><td>original</td><td>The FlowFiles that were used to 
create the bundle</td></tr><tr><td>merged</td><td>The FlowFile containing the 
merged content</td></tr></table><h3>Reads Attributes: </h3><table 
id="reads-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>fragment.identifier</td><td>Applicable
 only if the &lt;Merge Strategy&gt; property is set to Defragment. All 
FlowFiles with the same value for this attribute will be bundled 
together.</td></tr><tr><td>fragment.index</td><td>Applicable only if the 
&lt;Merge Strategy&gt; property is set to Defragment. This attribute indicates 
the order in which the fragments should be assembled. This attribute must be 
present on all FlowFiles when using the Defragment Merge Strategy and must be a 
unique (i.e., unique across all FlowFiles that have the same value for the 
"fragment.identifier" 
 attribute) integer between 0 and the value of the fragment.count attribute. If 
two or more FlowFiles have the same value for the "fragment.identifier" 
attribute and the same value for the "fragment.index" attribute, the behavior 
of this Processor is 
undefined.</td></tr><tr><td>fragment.count</td><td>Applicable only if the 
&lt;Merge Strategy&gt; property is set to Defragment. This attribute must be 
present on all FlowFiles with the same value for the fragment.identifier 
attribute. All FlowFiles in the same bundle must have the same value for this 
attribute. The value of this attribute indicates how many FlowFiles should be 
expected in the given 
bundle.</td></tr><tr><td>segment.original.filename</td><td>Applicable only if 
the &lt;Merge Strategy&gt; property is set to Defragment. This attribute must 
be present on all FlowFiles with the same value for the fragment.identifier 
attribute. All FlowFiles in the same bundle must have the same value for this 
attribute. The value of this attrib
 ute will be used for the filename of the completed merged 
FlowFile.</td></tr><tr><td>tar.permissions</td><td>Applicable only if the 
&lt;Merge Format&gt; property is set to TAR. The value of this attribute must 
be 3 characters; each character must be in the range 0 to 7 (inclusive) and 
indicates the file permissions that should be used for the FlowFile's TAR 
entry. If this attribute is missing or has an invalid value, the default value 
of 644 will be used</td></tr></table><h3>Writes Attributes: </h3><table 
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>filename</td><td>When
 more than 1 file is merged, the filename comes from the 
segment.original.filename attribute. If that attribute does not exist in the 
source FlowFiles, then the filename is set to the number of nanoseconds 
matching system time. Then a filename extension may be applied:if Merge Format 
is TAR, then the filename will be appended with .tar, if Merge Format is ZIP, 
then the filename will be app
 ended with .zip, if Merge Format is FlowFileStream, then the filename will be 
appended with .pkg</td></tr><tr><td>merge.count</td><td>The number of FlowFiles 
that were merged into this bundle</td></tr><tr><td>merge.bin.age</td><td>The 
age of the bin, in milliseconds, when it was merged and output. Effectively 
this is the greatest amount of time that any FlowFile in this bundle remained 
waiting in this processor before it was output</td></tr></table><h3>See 
Also:</h3><p><a 
href="../org.apache.nifi.processors.standard.SegmentContent/index.html">SegmentContent</a></p></body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>MergeContent</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Merges a Group of 
FlowFiles together based on a user-defined strategy and packages them into a 
single FlowFile. It is recommended that the Processor be configured with only a 
single incoming connection, as Group of FlowFiles will not be created from 
FlowFiles in different connections. This processor updates the mime.type 
attribute as appropriate.</p><h3>Tags: </h3><p>merge, content, correlation, 
tar, zip, stream, concatenation, archive, flowfile-stream, 
flowfile-stream-v3</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">N
 iFi 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>Merge 
Strategy</strong></td><td id="default-value">Bin-Packing Algorithm</td><td 
id="allowable-values"><ul><li>Bin-Packing Algorithm <img 
src="../../html/images/iconInfo.png" alt="Generates 'bins' of FlowFiles and 
fills each bin as full as possible. FlowFiles are placed into a bin based on 
their size and optionally their attributes (if the &lt;Correlation 
Attribute&gt; property is set)" title="Generates 'bins' of FlowFiles and fills 
each bin as full as possible. FlowFiles are placed into a bin based on their 
size and optionally their attributes (if the &lt;Correlation Attribute&gt; 
property is set)"></img></li><li>Defragment <img 
src="../../html/images/iconInfo.png" alt="Combines fragments that are 
associated by attributes back into a single cohesive FlowFile. If using this 
strategy, all FlowFiles must have the attr
 ibutes &lt;fragment.identifier&gt;, &lt;fragment.count&gt;, and 
&lt;fragment.index&gt; or alternatively (for backward compatibility purposes) 
&lt;segment.identifier&gt;, &lt;segment.count&gt;, and &lt;segment.index&gt;. 
All FlowFiles with the same value for &quot;fragment.identifier&quot; will be 
grouped together. All FlowFiles in this group must have the same value for the 
&quot;fragment.count&quot; attribute. All FlowFiles in this group must have a 
unique value for the &quot;fragment.index&quot; attribute between 0 and the 
value of the &quot;fragment.count&quot; attribute." title="Combines fragments 
that are associated by attributes back into a single cohesive FlowFile. If 
using this strategy, all FlowFiles must have the attributes 
&lt;fragment.identifier&gt;, &lt;fragment.count&gt;, and &lt;fragment.index&gt; 
or alternatively (for backward compatibility purposes) 
&lt;segment.identifier&gt;, &lt;segment.count&gt;, and &lt;segment.index&gt;. 
All FlowFiles with the same value for &q
 uot;fragment.identifier&quot; will be grouped together. All FlowFiles in this 
group must have the same value for the &quot;fragment.count&quot; attribute. 
All FlowFiles in this group must have a unique value for the 
&quot;fragment.index&quot; attribute between 0 and the value of the 
&quot;fragment.count&quot; attribute."></img></li></ul></td><td 
id="description">Specifies the algorithm used to merge content. The 
'Defragment' algorithm combines fragments that are associated by attributes 
back into a single cohesive FlowFile. The 'Bin-Packing Algorithm' generates a 
FlowFile populated by arbitrarily chosen FlowFiles</td></tr><tr><td 
id="name"><strong>Merge Format</strong></td><td id="default-value">Binary 
Concatenation</td><td id="allowable-values"><ul><li>TAR <img 
src="../../html/images/iconInfo.png" alt="A bin of FlowFiles will be combined 
into a single TAR file. The FlowFiles' &lt;path&gt; attribute will be used to 
create a directory in the TAR file if the &lt;Keep Paths&gt; propert
 y is set to true; otherwise, all FlowFiles will be added at the root of the 
TAR file. If a FlowFile has an attribute named &lt;tar.permissions&gt; that is 
3 characters, each between 0-7, that attribute will be used as the TAR entry's 
'mode'." title="A bin of FlowFiles will be combined into a single TAR file. The 
FlowFiles' &lt;path&gt; attribute will be used to create a directory in the TAR 
file if the &lt;Keep Paths&gt; property is set to true; otherwise, all 
FlowFiles will be added at the root of the TAR file. If a FlowFile has an 
attribute named &lt;tar.permissions&gt; that is 3 characters, each between 0-7, 
that attribute will be used as the TAR entry's 'mode'."></img></li><li>ZIP <img 
src="../../html/images/iconInfo.png" alt="A bin of FlowFiles will be combined 
into a single ZIP file. The FlowFiles' &lt;path&gt; attribute will be used to 
create a directory in the ZIP file if the &lt;Keep Paths&gt; property is set to 
true; otherwise, all FlowFiles will be added at the root of th
 e ZIP file. The &lt;Compression Level&gt; property indicates the ZIP 
compression to use." title="A bin of FlowFiles will be combined into a single 
ZIP file. The FlowFiles' &lt;path&gt; attribute will be used to create a 
directory in the ZIP file if the &lt;Keep Paths&gt; property is set to true; 
otherwise, all FlowFiles will be added at the root of the ZIP file. The 
&lt;Compression Level&gt; property indicates the ZIP compression to 
use."></img></li><li>FlowFile Stream, v3 <img 
src="../../html/images/iconInfo.png" alt="A bin of FlowFiles will be combined 
into a single Version 3 FlowFile Stream" title="A bin of FlowFiles will be 
combined into a single Version 3 FlowFile Stream"></img></li><li>FlowFile 
Stream, v2 <img src="../../html/images/iconInfo.png" alt="A bin of FlowFiles 
will be combined into a single Version 2 FlowFile Stream" title="A bin of 
FlowFiles will be combined into a single Version 2 FlowFile 
Stream"></img></li><li>FlowFile Tar, v1 <img src="../../html/images/iconInfo
 .png" alt="A bin of FlowFiles will be combined into a single Version 1 
FlowFile Package" title="A bin of FlowFiles will be combined into a single 
Version 1 FlowFile Package"></img></li><li>Binary Concatenation <img 
src="../../html/images/iconInfo.png" alt="The contents of all FlowFiles will be 
concatenated together into a single FlowFile" title="The contents of all 
FlowFiles will be concatenated together into a single 
FlowFile"></img></li><li>Avro <img src="../../html/images/iconInfo.png" 
alt="The Avro contents of all FlowFiles will be concatenated together into a 
single FlowFile" title="The Avro contents of all FlowFiles will be concatenated 
together into a single FlowFile"></img></li></ul></td><td 
id="description">Determines the format that will be used to merge the 
content.</td></tr><tr><td id="name"><strong>Attribute Strategy</strong></td><td 
id="default-value">Keep Only Common Attributes</td><td 
id="allowable-values"><ul><li>Keep Only Common Attributes</li><li>Keep All 
Unique A
 ttributes</li></ul></td><td id="description">Determines which FlowFile 
attributes should be added to the bundle. If 'Keep All Unique Attributes' is 
selected, any attribute on any FlowFile that gets bundled will be kept unless 
its value conflicts with the value from another FlowFile. If 'Keep Only Common 
Attributes' is selected, only the attributes that exist on all FlowFiles in the 
bundle, with the same value, will be preserved.</td></tr><tr><td 
id="name">Correlation Attribute Name</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">If specified, like FlowFiles 
will be binned together, where 'like FlowFiles' means FlowFiles that have the 
same value for this Attribute. If not specified, FlowFiles are bundled by the 
order in which they are pulled from the queue.<br/><strong>Supports Expression 
Language: true</strong></td></tr><tr><td id="name"><strong>Minimum Number of 
Entries</strong></td><td id="default-value">1</td><td 
id="allowable-values"></td><td 
 id="description">The minimum number of files to include in a 
bundle</td></tr><tr><td id="name">Maximum Number of Entries</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
maximum number of files to include in a bundle. If not specified, there is no 
maximum.</td></tr><tr><td id="name"><strong>Minimum Group Size</strong></td><td 
id="default-value">0 B</td><td id="allowable-values"></td><td 
id="description">The minimum size of for the bundle</td></tr><tr><td 
id="name">Maximum Group Size</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The maximum size for the 
bundle. If not specified, there is no maximum.</td></tr><tr><td id="name">Max 
Bin Age</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">The maximum age of a Bin that will trigger a Bin to be 
complete. Expected format is &lt;duration&gt; &lt;time unit&gt; where 
&lt;duration&gt; is a positive integer and time unit is one of sec
 onds, minutes, hours</td></tr><tr><td id="name"><strong>Maximum number of 
Bins</strong></td><td id="default-value">100</td><td 
id="allowable-values"></td><td id="description">Specifies the maximum number of 
bins that can be held in memory at any one time</td></tr><tr><td 
id="name"><strong>Delimiter Strategy</strong></td><td 
id="default-value">Filename</td><td id="allowable-values"><ul><li>Filename <img 
src="../../html/images/iconInfo.png" alt="The values of Header, Footer, and 
Demarcator will be retrieved from the contents of a file" title="The values of 
Header, Footer, and Demarcator will be retrieved from the contents of a 
file"></img></li><li>Text <img src="../../html/images/iconInfo.png" alt="The 
values of Header, Footer, and Demarcator will be specified as property values" 
title="The values of Header, Footer, and Demarcator will be specified as 
property values"></img></li></ul></td><td id="description">Determines if 
Header, Footer, and Demarcator should point to files containin
 g the respective content, or if the values of the properties should be used as 
the content.</td></tr><tr><td id="name">Header</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Filename specifying the header to use. If not specified, no 
header is supplied. This property is valid only when using the 
binary-concatenation merge strategy; otherwise, it is 
ignored.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Footer</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Filename specifying the footer to use. If not specified, no 
footer is supplied. This property is valid only when using the 
binary-concatenation merge strategy; otherwise, it is 
ignored.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Demarcator</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Filename specifying the demarcator to use. If not specified, no
  demarcator is supplied. This property is valid only when using the 
binary-concatenation merge strategy; otherwise, it is 
ignored.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Compression 
Level</strong></td><td id="default-value">1</td><td 
id="allowable-values"><ul><li>0</li><li>1</li><li>2</li><li>3</li><li>4</li><li>5</li><li>6</li><li>7</li><li>8</li><li>9</li></ul></td><td
 id="description">Specifies the compression level to use when using the Zip 
Merge Format; if not using the Zip Merge Format, this value is 
ignored</td></tr><tr><td id="name"><strong>Keep Path</strong></td><td 
id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">If using the Zip or Tar Merge Format, specifies whether or not 
the FlowFiles' paths should be included in their entry names; if using other 
merge strategy, this value is ignored</td></tr></table><h3>Relationships: 
</h3><table id="relationships"><
 tr><th>Name</th><th>Description</th></tr><tr><td>failure</td><td>If the bundle 
cannot be created, all FlowFiles that would have been used to created the 
bundle will be transferred to failure</td></tr><tr><td>original</td><td>The 
FlowFiles that were used to create the 
bundle</td></tr><tr><td>merged</td><td>The FlowFile containing the merged 
content</td></tr></table><h3>Reads Attributes: </h3><table 
id="reads-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>fragment.identifier</td><td>Applicable
 only if the &lt;Merge Strategy&gt; property is set to Defragment. All 
FlowFiles with the same value for this attribute will be bundled 
together.</td></tr><tr><td>fragment.index</td><td>Applicable only if the 
&lt;Merge Strategy&gt; property is set to Defragment. This attribute indicates 
the order in which the fragments should be assembled. This attribute must be 
present on all FlowFiles when using the Defragment Merge Strategy and must be a 
unique (i.e., unique across all FlowFiles
  that have the same value for the "fragment.identifier" attribute) integer 
between 0 and the value of the fragment.count attribute. If two or more 
FlowFiles have the same value for the "fragment.identifier" attribute and the 
same value for the "fragment.index" attribute, the behavior of this Processor 
is undefined.</td></tr><tr><td>fragment.count</td><td>Applicable only if the 
&lt;Merge Strategy&gt; property is set to Defragment. This attribute must be 
present on all FlowFiles with the same value for the fragment.identifier 
attribute. All FlowFiles in the same bundle must have the same value for this 
attribute. The value of this attribute indicates how many FlowFiles should be 
expected in the given 
bundle.</td></tr><tr><td>segment.original.filename</td><td>Applicable only if 
the &lt;Merge Strategy&gt; property is set to Defragment. This attribute must 
be present on all FlowFiles with the same value for the fragment.identifier 
attribute. All FlowFiles in the same bundle must have the
  same value for this attribute. The value of this attribute will be used for 
the filename of the completed merged 
FlowFile.</td></tr><tr><td>tar.permissions</td><td>Applicable only if the 
&lt;Merge Format&gt; property is set to TAR. The value of this attribute must 
be 3 characters; each character must be in the range 0 to 7 (inclusive) and 
indicates the file permissions that should be used for the FlowFile's TAR 
entry. If this attribute is missing or has an invalid value, the default value 
of 644 will be used</td></tr></table><h3>Writes Attributes: </h3><table 
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>filename</td><td>When
 more than 1 file is merged, the filename comes from the 
segment.original.filename attribute. If that attribute does not exist in the 
source FlowFiles, then the filename is set to the number of nanoseconds 
matching system time. Then a filename extension may be applied:if Merge Format 
is TAR, then the filename will be appended with .ta
 r, if Merge Format is ZIP, then the filename will be appended with .zip, if 
Merge Format is FlowFileStream, then the filename will be appended with 
.pkg</td></tr><tr><td>merge.count</td><td>The number of FlowFiles that were 
merged into this bundle</td></tr><tr><td>merge.bin.age</td><td>The age of the 
bin, in milliseconds, when it was merged and output. Effectively this is the 
greatest amount of time that any FlowFile in this bundle remained waiting in 
this processor before it was output</td></tr></table><h3>See Also:</h3><p><a 
href="../org.apache.nifi.processors.standard.SegmentContent/index.html">SegmentContent</a></p></body></html>
\ No newline at end of file

Modified: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.PostHTTP/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.PostHTTP/index.html?rev=1730777&r1=1730776&r2=1730777&view=diff
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.PostHTTP/index.html
 (original)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.PostHTTP/index.html
 Wed Feb 17 02:20:53 2016
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>PostHTTP</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Performs an HTTP 
Post with the content of the FlowFile</p><h3>Tags: </h3><p>http, https, remote, 
copy, archive</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>Allowabl
 e Values</th><th>Description</th></tr><tr><td 
id="name"><strong>URL</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The URL to POST to. The first 
part of the URL must be static. However, the path of the URL may be defined 
using the Attribute Expression Language. For example, https://${hostname} is 
not valid, but https://1.1.1.1:8080/files/${nf.file.name} is 
valid.<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
id="name">Max Batch Size</td><td id="default-value">100 MB</td><td 
id="allowable-values"></td><td id="description">If the Send as FlowFile 
property is true, specifies the max data size for a batch of FlowFiles to send 
in a single HTTP POST. If not specified, each FlowFile will be sent separately. 
If the Send as FlowFile property is false, this property is 
ignored</td></tr><tr><td id="name">Max Data to Post per Second</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
max
 imum amount of data to send per second; this allows the bandwidth to be 
throttled to a specified data rate; if not specified, the data rate is not 
throttled</td></tr><tr><td id="name">SSL Context Service</td><td 
id="default-value"></td><td id="allowable-values"><strong>Controller Service 
API: 
</strong><br/>SSLContextService<br/><strong>Implementation:</strong><br/><a 
href="../org.apache.nifi.ssl.StandardSSLContextService/index.html">StandardSSLContextService</a></td><td
 id="description">The Controller Service to use in order to obtain an SSL 
Context</td></tr><tr><td id="name">Username</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Username required to access the 
URL</td></tr><tr><td id="name">Password</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Password required to access the 
URL<br/><strong>Sensitive Property: true</strong></td></tr><tr><td 
id="name"><strong>Send as FlowFile</strong></td><td id="default-va
 lue">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">If true, will package the FlowFile's contents and attributes 
together and send the FlowFile Package; otherwise, will send only the 
FlowFile's content</td></tr><tr><td id="name"><strong>Use Chunked 
Encoding</strong></td><td id="default-value">true</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Specifies whether or not to use Chunked Encoding to send the 
data. If false, the entire content of the FlowFile will be buffered into 
memory.</td></tr><tr><td id="name"><strong>Compression Level</strong></td><td 
id="default-value">0</td><td id="allowable-values"></td><td 
id="description">Determines the GZIP Compression Level to use when sending the 
file; the value must be in the range of 0-9. A value of 0 indicates that the 
file will not be GZIP'ed</td></tr><tr><td id="name"><strong>Connection 
Timeout</strong></td><td id="default-value">30 sec</td><
 td id="allowable-values"></td><td id="description">How long to wait when 
attempting to connect to the remote server before giving up</td></tr><tr><td 
id="name"><strong>Data Timeout</strong></td><td id="default-value">30 
sec</td><td id="allowable-values"></td><td id="description">How long to wait 
between receiving segments of data from the remote server before giving up and 
discarding the partial file</td></tr><tr><td id="name">Attributes to Send as 
HTTP Headers (Regex)</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Specifies the Regular 
Expression that determines the names of FlowFile attributes that should be sent 
as HTTP Headers</td></tr><tr><td id="name">User Agent</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">What to report as the User Agent when we connect to the remote 
server</td></tr><tr><td id="name">Proxy Host</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
ful
 ly qualified hostname or IP address of the proxy server</td></tr><tr><td 
id="name">Proxy Port</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The port of the proxy 
server</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>Files
 that are successfully send will be transferred to 
success</td></tr><tr><td>failure</td><td>Files that fail to send will 
transferred to failure</td></tr></table><h3>Reads Attributes: </h3><table 
id="reads-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>mime.type</td><td>If
 not sending data as a FlowFile, the mime.type attribute will be used to set 
the HTTP Header for Content-Type</td></tr></table><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>PostHTTP</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Performs an HTTP 
Post with the content of the FlowFile</p><h3>Tags: </h3><p>http, https, remote, 
copy, archive</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>Allowabl
 e Values</th><th>Description</th></tr><tr><td 
id="name"><strong>URL</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The URL to POST to. The first 
part of the URL must be static. However, the path of the URL may be defined 
using the Attribute Expression Language. For example, https://${hostname} is 
not valid, but https://1.1.1.1:8080/files/${nf.file.name} is 
valid.<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
id="name">Max Batch Size</td><td id="default-value">100 MB</td><td 
id="allowable-values"></td><td id="description">If the Send as FlowFile 
property is true, specifies the max data size for a batch of FlowFiles to send 
in a single HTTP POST. If not specified, each FlowFile will be sent separately. 
If the Send as FlowFile property is false, this property is 
ignored</td></tr><tr><td id="name">Max Data to Post per Second</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
max
 imum amount of data to send per second; this allows the bandwidth to be 
throttled to a specified data rate; if not specified, the data rate is not 
throttled</td></tr><tr><td id="name">SSL Context Service</td><td 
id="default-value"></td><td id="allowable-values"><strong>Controller Service 
API: 
</strong><br/>SSLContextService<br/><strong>Implementation:</strong><br/><a 
href="../org.apache.nifi.ssl.StandardSSLContextService/index.html">StandardSSLContextService</a></td><td
 id="description">The Controller Service to use in order to obtain an SSL 
Context</td></tr><tr><td id="name">Username</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Username required to access the 
URL</td></tr><tr><td id="name">Password</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Password required to access the 
URL<br/><strong>Sensitive Property: true</strong></td></tr><tr><td 
id="name"><strong>Send as FlowFile</strong></td><td id="default-va
 lue">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">If true, will package the FlowFile's contents and attributes 
together and send the FlowFile Package; otherwise, will send only the 
FlowFile's content</td></tr><tr><td id="name">Use Chunked Encoding</td><td 
id="default-value"></td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Specifies whether or not to use Chunked Encoding to send the 
data. This property is ignored in the event the contents are compressed or sent 
as FlowFiles.</td></tr><tr><td id="name"><strong>Compression 
Level</strong></td><td id="default-value">0</td><td 
id="allowable-values"></td><td id="description">Determines the GZIP Compression 
Level to use when sending the file; the value must be in the range of 0-9. A 
value of 0 indicates that the file will not be GZIP'ed</td></tr><tr><td 
id="name"><strong>Connection Timeout</strong></td><td id="default-value">30 
sec</td><td id="a
 llowable-values"></td><td id="description">How long to wait when attempting to 
connect to the remote server before giving up</td></tr><tr><td 
id="name"><strong>Data Timeout</strong></td><td id="default-value">30 
sec</td><td id="allowable-values"></td><td id="description">How long to wait 
between receiving segments of data from the remote server before giving up and 
discarding the partial file</td></tr><tr><td id="name">Attributes to Send as 
HTTP Headers (Regex)</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Specifies the Regular 
Expression that determines the names of FlowFile attributes that should be sent 
as HTTP Headers</td></tr><tr><td id="name">User Agent</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">What to report as the User Agent when we connect to the remote 
server</td></tr><tr><td id="name">Proxy Host</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
fully quali
 fied hostname or IP address of the proxy server</td></tr><tr><td 
id="name">Proxy Port</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The port of the proxy 
server</td></tr><tr><td id="name"><strong>Content-Type</strong></td><td 
id="default-value">${mime.type}</td><td id="allowable-values"></td><td 
id="description">The Content-Type to specify for the content of the FlowFile 
being POSTed if Send as FlowFile is false. In the case of an empty value after 
evaluating an expression language expression, Content-Type defaults to 
application/octet-stream<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>Files
 that are successfully send will be transferred to 
success</td></tr><tr><td>failure</td><td>Files that fail to send will 
transferred to failure</td></tr></table><h3>Reads Attributes: </h3>None 
specified.<h3>Writes At
 tributes: </h3>None specified.</body></html>
\ No newline at end of file

Modified: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.PutDistributedMapCache/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.PutDistributedMapCache/index.html?rev=1730777&r1=1730776&r2=1730777&view=diff
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.PutDistributedMapCache/index.html
 (original)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.PutDistributedMapCache/index.html
 Wed Feb 17 02:20:53 2016
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>PutDistributedMapCache</title><link 
rel="stylesheet" href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Gets the content 
of a FlowFile and puts it to a distributed map cache, using a cache key 
computed from FlowFile attributes. If the cache already contains the entry and 
the cache update strategy is 'keep original' the entry is not 
replaced.'</p><h3>Tags: </h3><p>map, cache, put, distributed</p><h3>Properties: 
</h3><p>In the list below, the names of required properties appear in 
<strong>bold</strong>. Any other properties (not in bold) are considered 
optional. The table also indicates any default values, and whether a property 
supports the <a href="../../html/expression-language-guide.html">NiFi 
Expression Language</a>.</p><table id="properties"><tr><th>Name</th><th>Default 
Value</th><th>Allowable Values</th><th>Description</th></tr><tr><td 
id="name"><strong>Cache 
 Entry Identifier</strong></td><td id="default-value"></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 cache key<br/><strong>Supports 
Expression Language: true</strong></td></tr><tr><td 
id="name"><strong>Distributed Cache Service</strong></td><td 
id="default-value"></td><td id="allowable-values"><strong>Controller Service 
API: 
</strong><br/>DistributedMapCacheClient<br/><strong>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 flow 
files</td></tr><tr><td id="name"><strong>Cache update strategy</strong></td><td 
id="default-value">replace</td><td id="allowable-values"><ul><li>Replace if 
present <img src="../../html/images/iconInfo.png" alt="Adds t
 he specified entry to the cache, replacing any value that is currently set." 
title="Adds the specified entry to the cache, replacing any value that is 
currently set."></img></li><li>Keep original <img 
src="../../html/images/iconInfo.png" alt="Adds the specified entry to the 
cache, if the key does not exist." title="Adds the specified entry to the 
cache, if the key does not exist."></img></li></ul></td><td 
id="description">Determines how the cache is updated if the cache already 
contains the entry</td></tr><tr><td id="name">Max cache entry size</td><td 
id="default-value">1 MB</td><td id="allowable-values"></td><td 
id="description">The maximum amount of data to put into 
cache</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>Any
 FlowFile that is successfully inserted into cache will be routed to this 
relationship</td></tr><tr><td>failure</td><td>Any FlowFile that cannot be 
inserted into the cache will b
 e 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>cached</td><td>All
 FlowFiles will have an attribute 'cached'. The value of this attribute is 
true, is the FlowFile is cached, otherwise false.</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>PutDistributedMapCache</title><link 
rel="stylesheet" href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Gets the content 
of a FlowFile and puts it to a distributed map cache, using a cache key 
computed from FlowFile attributes. If the cache already contains the entry and 
the cache update strategy is 'keep original' the entry is not 
replaced.'</p><h3>Tags: </h3><p>map, cache, put, distributed</p><h3>Properties: 
</h3><p>In the list below, the names of required properties appear in 
<strong>bold</strong>. Any other properties (not in bold) are considered 
optional. The table also indicates any default values, and whether a property 
supports the <a href="../../html/expression-language-guide.html">NiFi 
Expression Language</a>.</p><table id="properties"><tr><th>Name</th><th>Default 
Value</th><th>Allowable Values</th><th>Description</th></tr><tr><td 
id="name"><strong>Cache 
 Entry Identifier</strong></td><td id="default-value"></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 cache key<br/><strong>Supports 
Expression Language: true</strong></td></tr><tr><td 
id="name"><strong>Distributed Cache Service</strong></td><td 
id="default-value"></td><td id="allowable-values"><strong>Controller Service 
API: 
</strong><br/>DistributedMapCacheClient<br/><strong>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 flow 
files</td></tr><tr><td id="name"><strong>Cache update strategy</strong></td><td 
id="default-value">replace</td><td id="allowable-values"><ul><li>Replace if 
present <img src="../../html/images/iconInfo.png" alt="Adds t
 he specified entry to the cache, replacing any value that is currently set." 
title="Adds the specified entry to the cache, replacing any value that is 
currently set."></img></li><li>Keep original <img 
src="../../html/images/iconInfo.png" alt="Adds the specified entry to the 
cache, if the key does not exist." title="Adds the specified entry to the 
cache, if the key does not exist."></img></li></ul></td><td 
id="description">Determines how the cache is updated if the cache already 
contains the entry</td></tr><tr><td id="name">Max cache entry size</td><td 
id="default-value">1 MB</td><td id="allowable-values"></td><td 
id="description">The maximum amount of data to put into 
cache</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>Any
 FlowFile that is successfully inserted into cache will be routed to this 
relationship</td></tr><tr><td>failure</td><td>Any FlowFile that cannot be 
inserted into the cache will b
 e 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>cached</td><td>All
 FlowFiles will have an attribute 'cached'. The value of this attribute is 
true, is the FlowFile is cached, otherwise false.</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>,
 <a 
href="../org.apache.nifi.processors.standard.FetchDistributedMapCache/index.html">FetchDistributedMapCache</a></p></body></html>
\ No newline at end of file


Reply via email to