Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hive-nar/1.6.0/org.apache.nifi.processors.hive.SelectHiveQL/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hive-nar/1.6.0/org.apache.nifi.processors.hive.SelectHiveQL/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hive-nar/1.6.0/org.apache.nifi.processors.hive.SelectHiveQL/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hive-nar/1.6.0/org.apache.nifi.processors.hive.SelectHiveQL/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>SelectHiveQL</title><link rel="stylesheet" 
href="../../../../../css/component-usage.css" 
type="text/css"></link></head><script type="text/javascript">window.onload = 
function(){if(self==top) { document.getElementById('nameHeader').style.display 
= "inherit"; } }</script><body><h1 id="nameHeader" style="display: 
none;">SelectHiveQL</h1><h2>Description: </h2><p>Execute provided HiveQL SELECT 
query against a Hive database connection. Query result will be converted to 
Avro or CSV format. Streaming is used so arbitrarily large result sets are 
supported. This processor can be scheduled to run on a timer, or cron 
expression, using the standard scheduling methods, or it can be triggered by an 
incoming FlowFile. If it is triggered by an incoming FlowFile, then attributes 
of that FlowFile will be available when evaluating the select query. FlowFile 
attribute 'selecthiveql.row.count' indicates how many rows were selected.<
 /p><h3>Tags: </h3><p>hive, sql, select, jdbc, query, 
database</p><h3>Properties: </h3><p>In the list below, the names of required 
properties appear in <strong>bold</strong>. Any other properties (not in bold) 
are considered optional. The table also indicates any default values, and 
whether a property supports the <a 
href="../../../../../html/expression-language-guide.html">NiFi Expression 
Language</a>.</p><table id="properties"><tr><th>Name</th><th>Default 
Value</th><th>Allowable Values</th><th>Description</th></tr><tr><td 
id="name"><strong>Hive Database Connection Pooling Service</strong></td><td 
id="default-value"></td><td id="allowable-values"><strong>Controller Service 
API: </strong><br/>HiveDBCPService<br/><strong>Implementation: </strong><a 
href="../org.apache.nifi.dbcp.hive.HiveConnectionPool/index.html">HiveConnectionPool</a></td><td
 id="description">The Hive Controller Service that is used to obtain 
connection(s) to the Hive database</td></tr><tr><td id="name">HiveQL Select
  Query</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">HiveQL SELECT query to execute. If this is not set, the query 
is assumed to be in the content of an incoming FlowFile.<br/><strong>Supports 
Expression Language: true</strong></td></tr><tr><td id="name"><strong>Fetch 
Size</strong></td><td id="default-value">0</td><td 
id="allowable-values"></td><td id="description">The number of result rows to be 
fetched from the result set at a time. This is a hint to the driver and may not 
be honored and/or exact. If the value specified is zero, then the hint is 
ignored.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Max Rows Per Flow 
File</strong></td><td id="default-value">0</td><td 
id="allowable-values"></td><td id="description">The maximum number of result 
rows that will be included in a single FlowFile. This will allow you to break 
up very large result sets into multiple FlowFiles. If the value specified is 
zero
 , then all rows are returned in a single FlowFile.<br/><strong>Supports 
Expression Language: true</strong></td></tr><tr><td id="name"><strong>Maximum 
Number of Fragments</strong></td><td id="default-value">0</td><td 
id="allowable-values"></td><td id="description">The maximum number of 
fragments. If the value specified is zero, then all fragments are returned. 
This prevents OutOfMemoryError when this processor ingests huge 
table.<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
id="name"><strong>Output Format</strong></td><td 
id="default-value">Avro</td><td 
id="allowable-values"><ul><li>Avro</li><li>CSV</li></ul></td><td 
id="description">How to represent the records coming from Hive (Avro, CSV, 
e.g.)</td></tr><tr><td id="name"><strong>Normalize Table/Column 
Names</strong></td><td id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Whether to change non-Avro-compatible characters in column 
names t
 o Avro-compatible characters. For example, colons and periods will be changed 
to underscores in order to build a valid Avro record.</td></tr><tr><td 
id="name"><strong>CSV Header</strong></td><td id="default-value">true</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Include Header in Output</td></tr><tr><td id="name">Alternate 
CSV Header</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">Comma separated list of header fields<br/><strong>Supports 
Expression Language: true</strong></td></tr><tr><td id="name"><strong>CSV 
Delimiter</strong></td><td id="default-value">,</td><td 
id="allowable-values"></td><td id="description">CSV Delimiter used to separate 
fields<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
id="name"><strong>CSV Quote</strong></td><td id="default-value">true</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Whether to force quo
 ting of CSV fields. Note that this might conflict with the setting for CSV 
Escape.</td></tr><tr><td id="name"><strong>CSV Escape</strong></td><td 
id="default-value">true</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Whether to escape CSV strings in output. Note that this might 
conflict with the setting for CSV Quote.</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 record 
data.</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>Successfully
 created FlowFile from HiveQL query result 
set.</td></tr><tr><td>failure</td><td>HiveQL query execution failed. Incoming 
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-attribu
 tes"><tr><th>Name</th><th>Description</th></tr><tr><td>mime.type</td><td>Sets 
the MIME type for the outgoing flowfile to application/avro-binary for Avro or 
text/csv for CSV.</td></tr><tr><td>filename</td><td>Adds .avro or .csv to the 
filename attribute depending on which output format is 
selected.</td></tr><tr><td>selecthiveql.row.count</td><td>Indicates how many 
rows were selected/returned by the 
query.</td></tr><tr><td>fragment.identifier</td><td>If 'Max Rows Per Flow File' 
is set then all FlowFiles from the same query result set 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>If 'Max Rows Per Flow 
File' is set then this is the total number of  FlowFiles produced by a single 
ResultSet. This can be used in conjunction with the fragment.identifier 
attribute in order to know how many FlowFiles belonged to the same incoming 
ResultSet.</td></tr><tr><td>fragment.index</td><td>If 'Max
  Rows Per Flow File' is set then the position of this FlowFile in the list of 
outgoing FlowFiles that were all derived from the same result set FlowFile. 
This can be used in conjunction with the fragment.identifier attribute to know 
which FlowFiles originated from the same query result set and in what order  
FlowFiles were produced</td></tr><tr><td>query.input.tables</td><td>Contains 
input table names in comma delimited 'databaseName.tableName' 
format.</td></tr></table><h3>State management: </h3>This component does not 
store state.<h3>Restricted: </h3>This component is not restricted.<h3>Input 
requirement: </h3>This component allows an incoming relationship.<h3>System 
Resource Considerations:</h3>None specified.</body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hl7-nar/1.6.0/org.apache.nifi.processors.hl7.ExtractHL7Attributes/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hl7-nar/1.6.0/org.apache.nifi.processors.hl7.ExtractHL7Attributes/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hl7-nar/1.6.0/org.apache.nifi.processors.hl7.ExtractHL7Attributes/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hl7-nar/1.6.0/org.apache.nifi.processors.hl7.ExtractHL7Attributes/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ExtractHL7Attributes</title><link 
rel="stylesheet" href="../../../../../css/component-usage.css" 
type="text/css"></link></head><script type="text/javascript">window.onload = 
function(){if(self==top) { document.getElementById('nameHeader').style.display 
= "inherit"; } }</script><body><h1 id="nameHeader" style="display: 
none;">ExtractHL7Attributes</h1><h2>Description: </h2><p>Extracts information 
from an HL7 (Health Level 7) formatted FlowFile and adds the information as 
FlowFile Attributes. The attributes are named as &lt;Segment Name&gt; 
&lt;dot&gt; &lt;Field Index&gt;. If the segment is repeating, the naming will 
be &lt;Segment Name&gt; &lt;underscore&gt; &lt;Segment Index&gt; &lt;dot&gt; 
&lt;Field Index&gt;. For example, we may have an attribute named "MHS.12" with 
a value of "2.1" and an attribute named "OBX_11.3" with a value of 
"93000^CPT4".</p><h3>Tags: </h3><p>HL7, health level 7, healthcare, extract, at
 tributes</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>Character Encoding</strong></td><td 
id="default-value">UTF-8</td><td id="allowable-values"></td><td 
id="description">The Character Encoding that is used to encode the HL7 
data<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
id="name"><strong>Use Segment Names</strong></td><td 
id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Whether or not to use HL7 segment names in 
attributes</td></tr><tr><td id="name"><st
 rong>Parse Segment Fields</strong></td><td id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Whether or not to parse HL7 segment fields into 
attributes</td></tr><tr><td id="name"><strong>Skip Validation</strong></td><td 
id="default-value">true</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Whether or not to validate HL7 message values</td></tr><tr><td 
id="name"><strong>HL7 Input Version</strong></td><td 
id="default-value">autodetect</td><td 
id="allowable-values"><ul><li>autodetect</li><li>2.2</li><li>2.3</li><li>2.3.1</li><li>2.4</li><li>2.5</li><li>2.5.1</li><li>2.6</li></ul></td><td
 id="description">The HL7 version to use for parsing and 
validation</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>A
 FlowFile is routed to this relationship if it is properly parsed as HL7 and 
its attributes 
 extracted</td></tr><tr><td>failure</td><td>A FlowFile is routed to this 
relationship if it cannot be mapped to FlowFile Attributes. This would happen 
if the FlowFile does not contain valid HL7 data</td></tr></table><h3>Reads 
Attributes: </h3>None specified.<h3>Writes Attributes: </h3>None 
specified.<h3>State management: </h3>This component does not store 
state.<h3>Restricted: </h3>This component is not restricted.<h3>Input 
requirement: </h3>This component requires an incoming relationship.<h3>System 
Resource Considerations:</h3>None specified.</body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hl7-nar/1.6.0/org.apache.nifi.processors.hl7.RouteHL7/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hl7-nar/1.6.0/org.apache.nifi.processors.hl7.RouteHL7/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hl7-nar/1.6.0/org.apache.nifi.processors.hl7.RouteHL7/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hl7-nar/1.6.0/org.apache.nifi.processors.hl7.RouteHL7/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>RouteHL7</title><link rel="stylesheet" 
href="../../../../../css/component-usage.css" 
type="text/css"></link></head><script type="text/javascript">window.onload = 
function(){if(self==top) { document.getElementById('nameHeader').style.display 
= "inherit"; } }</script><body><h1 id="nameHeader" style="display: 
none;">RouteHL7</h1><h2>Description: </h2><p>Routes incoming HL7 data according 
to user-defined queries. To add a query, add a new property to the processor. 
The name of the property will become a new relationship for the processor, and 
the value is an HL7 Query Language query. If a FlowFile matches the query, a 
copy of the FlowFile will be routed to the associated 
relationship.</p><h3>Tags: </h3><p>HL7, healthcare, route, Health Level 
7</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. Th
 e 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>Character Encoding</strong></td><td 
id="default-value">UTF-8</td><td id="allowable-values"></td><td 
id="description">The Character Encoding that is used to encode the HL7 
data<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">Name of a Relationship</td><td id="value">An HL7 Query Language 
query</td><td>If a FlowFile matches the query, it will be routed to a 
relationship with the name of the 
property</td></tr></table></p><h3>Relationships: 
 </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>failure</td><td>Any
 FlowFile that cannot be parsed as HL7 will be routed to this 
relationship</td></tr><tr><td>original</td><td>The original FlowFile that comes 
into this processor will be routed to this relationship, unless it is routed to 
'failure'</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>RouteHL7.Route</td><td>The
 name of the relationship to which the FlowFile was 
routed</td></tr></table><h3>State management: </h3>This component does not 
store state.<h3>Restricted: </h3>This component is not restricted.<h3>Input 
requirement: </h3>This component requires an incoming relationship.<h3>System 
Resource Considerations:</h3>None specified.</body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-html-nar/1.6.0/org.apache.nifi.GetHTMLElement/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-html-nar/1.6.0/org.apache.nifi.GetHTMLElement/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-html-nar/1.6.0/org.apache.nifi.GetHTMLElement/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-html-nar/1.6.0/org.apache.nifi.GetHTMLElement/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>GetHTMLElement</title><link rel="stylesheet" 
href="../../../../../css/component-usage.css" 
type="text/css"></link></head><script type="text/javascript">window.onload = 
function(){if(self==top) { document.getElementById('nameHeader').style.display 
= "inherit"; } }</script><body><h1 id="nameHeader" style="display: 
none;">GetHTMLElement</h1><h2>Description: </h2><p>Extracts HTML element values 
from the incoming flowfile's content using a CSS selector. The incoming HTML is 
first converted into a HTML Document Object Model so that HTML elements may be 
selected in the similar manner that CSS selectors are used to apply styles to 
HTML. The resulting HTML DOM is then "queried" using the user defined CSS 
selector string. The result of "querying" the HTML DOM may produce 0-N results. 
If no results are found the flowfile will be transferred to the "element not 
found" relationship to indicate so to the end user. If N resul
 ts are found a new flowfile will be created and emitted for each result. The 
query result will either be placed in the content of the new flowfile or as an 
attribute of the new flowfile. By default the result is written to an 
attribute. This can be controlled by the "Destination" property. Resulting 
query values may also have data prepended or appended to them by setting the 
value of property "Prepend Element Value" or "Append Element Value". Prepended 
and appended values are treated as string values and concatenated to the result 
retrieved from the HTML DOM query operation. A more thorough reference for the 
CSS selector syntax can be found at 
"http://jsoup.org/apidocs/org/jsoup/select/Selector.html";</p><h3>Tags: 
</h3><p>get, html, dom, css, element</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 proper
 ty 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>URL</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Base URL for the HTML page 
being parsed. This URL will be used to resolve an absolute URL when an 
attribute value is extracted from a HTML element.<br/><strong>Supports 
Expression Language: true</strong></td></tr><tr><td id="name"><strong>CSS 
Selector</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">CSS selector syntax string used 
to extract the desired HTML element(s).<br/><strong>Supports Expression 
Language: true</strong></td></tr><tr><td id="name"><strong>HTML Character 
Encoding</strong></td><td id="default-value">UTF-8</td><td 
id="allowable-values"></td><td id="description">Character encoding of 
 the input HTML</td></tr><tr><td id="name"><strong>Output Type</strong></td><td 
id="default-value">HTML</td><td 
id="allowable-values"><ul><li>HTML</li><li>Text</li><li>Attribute</li><li>Data</li></ul></td><td
 id="description">Controls the type of DOM value that is retrieved from the 
HTML element.</td></tr><tr><td id="name"><strong>Destination</strong></td><td 
id="default-value">flowfile-attribute</td><td 
id="allowable-values"><ul><li>flowfile-attribute</li><li>flowfile-content</li></ul></td><td
 id="description">Control if element extracted is written as a flowfile 
attribute or as flowfile content.</td></tr><tr><td id="name">Prepend Element 
Value</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">Prepends the specified value to the resulting 
Element<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Append Element Value</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Appends the specif
 ied value to the resulting Element<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Attribute Name</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">When getting the value of a HTML element attribute this value 
is used as the key to determine which attribute on the selected element should 
be retrieved. This value is used when the "Output Type" is set to "Attribute". 
If this value is prefixed with 'abs:', then the extracted attribute value will 
be converted into an absolute URL form using the specified base 
URL.<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>element 
not found</td><td>Element could not be found in the HTML document. The original 
HTML input will remain in the FlowFile content unchanged. Relationship 
'original' will not be invoked in this scenario.</td></tr><tr><td>success</td><t
 d>Successfully parsed HTML element</td></tr><tr><td>original</td><td>The 
original HTML input</td></tr><tr><td>invalid html</td><td>The input HTML syntax 
is invalid</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>HTMLElement</td><td>Flowfile
 attribute where the element result parsed from the HTML using the CSS selector 
syntax are placed if the destination is a flowfile 
attribute.</td></tr></table><h3>State management: </h3>This component does not 
store state.<h3>Restricted: </h3>This component is not restricted.<h3>Input 
requirement: </h3>This component requires an incoming relationship.<h3>System 
Resource Considerations:</h3>None specified.<h3>See Also:</h3><p><a 
href="../org.apache.nifi.ModifyHTMLElement/index.html">ModifyHTMLElement</a>, 
<a 
href="../org.apache.nifi.PutHTMLElement/index.html">PutHTMLElement</a></p></body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-html-nar/1.6.0/org.apache.nifi.ModifyHTMLElement/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-html-nar/1.6.0/org.apache.nifi.ModifyHTMLElement/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-html-nar/1.6.0/org.apache.nifi.ModifyHTMLElement/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-html-nar/1.6.0/org.apache.nifi.ModifyHTMLElement/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ModifyHTMLElement</title><link rel="stylesheet" 
href="../../../../../css/component-usage.css" 
type="text/css"></link></head><script type="text/javascript">window.onload = 
function(){if(self==top) { document.getElementById('nameHeader').style.display 
= "inherit"; } }</script><body><h1 id="nameHeader" style="display: 
none;">ModifyHTMLElement</h1><h2>Description: </h2><p>Modifies the value of an 
existing HTML element. The desired element to be modified is located by using 
CSS selector syntax. The incoming HTML is first converted into a HTML Document 
Object Model so that HTML elements may be selected in the similar manner that 
CSS selectors are used to apply styles to HTML. The resulting HTML DOM is then 
"queried" using the user defined CSS selector string to find the element the 
user desires to modify. If the HTML element is found the element's value is 
updated in the DOM using the value specified "Modified Value"
  property. All DOM elements that match the CSS selector will be updated. Once 
all of the DOM elements have been updated the DOM is rendered to HTML and the 
result replaces the flowfile content with the updated HTML. A more thorough 
reference for the CSS selector syntax can be found at 
"http://jsoup.org/apidocs/org/jsoup/select/Selector.html";</p><h3>Tags: 
</h3><p>modify, html, dom, css, element</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>CSS Selector</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">CSS selec
 tor syntax string used to extract the desired HTML 
element(s).<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>HTML Character 
Encoding</strong></td><td id="default-value">UTF-8</td><td 
id="allowable-values"></td><td id="description">Character encoding of the input 
HTML</td></tr><tr><td id="name"><strong>Output Type</strong></td><td 
id="default-value">HTML</td><td 
id="allowable-values"><ul><li>HTML</li><li>Text</li><li>Attribute</li></ul></td><td
 id="description">Controls whether the HTML element is output as HTML,Text or 
Data</td></tr><tr><td id="name"><strong>Modified Value</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Value to update the found HTML elements 
with<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
id="name">Attribute Name</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">When modifying the value of an 
element attribute thi
 s value is used as the key to determine which attribute on the selected 
element will be modified with the new value.<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>element 
not found</td><td>Element could not be found in the HTML document. The original 
HTML input will remain in the FlowFile content unchanged. Relationship 
'original' will not be invoked in this 
scenario.</td></tr><tr><td>success</td><td>Successfully parsed HTML 
element</td></tr><tr><td>original</td><td>The original HTML 
input</td></tr><tr><td>invalid html</td><td>The input HTML syntax is 
invalid</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>NumElementsModified</td><td>Total
 number of HTML element modifications made</td></tr></table><h3>State 
management: </h3>This component do
 es not store state.<h3>Restricted: </h3>This component is not 
restricted.<h3>Input requirement: </h3>This component requires an incoming 
relationship.<h3>System Resource Considerations:</h3>None specified.<h3>See 
Also:</h3><p><a 
href="../org.apache.nifi.GetHTMLElement/index.html">GetHTMLElement</a>, <a 
href="../org.apache.nifi.PutHTMLElement/index.html">PutHTMLElement</a></p></body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-html-nar/1.6.0/org.apache.nifi.PutHTMLElement/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-html-nar/1.6.0/org.apache.nifi.PutHTMLElement/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-html-nar/1.6.0/org.apache.nifi.PutHTMLElement/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-html-nar/1.6.0/org.apache.nifi.PutHTMLElement/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>PutHTMLElement</title><link rel="stylesheet" 
href="../../../../../css/component-usage.css" 
type="text/css"></link></head><script type="text/javascript">window.onload = 
function(){if(self==top) { document.getElementById('nameHeader').style.display 
= "inherit"; } }</script><body><h1 id="nameHeader" style="display: 
none;">PutHTMLElement</h1><h2>Description: </h2><p>Places a new HTML element in 
the existing HTML DOM. The desired position for the new HTML element is 
specified by using CSS selector syntax. The incoming HTML is first converted 
into a HTML Document Object Model so that HTML DOM location may be located in a 
similar manner that CSS selectors are used to apply styles to HTML. The 
resulting HTML DOM is then "queried" using the user defined CSS selector string 
to find the position where the user desires to add the new HTML element. Once 
the new HTML element is added to the DOM it is rendered to HTML and the
  result replaces the flowfile content with the updated HTML. A more thorough 
reference for the CSS selector syntax can be found at 
"http://jsoup.org/apidocs/org/jsoup/select/Selector.html";</p><h3>Tags: 
</h3><p>put, html, dom, css, element</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>CSS Selector</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">CSS selector syntax string used 
to extract the desired HTML element(s).<br/><strong>Supports Expression 
Language: true</strong></td></tr><tr><td id="name"><strong>HTML
  Character Encoding</strong></td><td id="default-value">UTF-8</td><td 
id="allowable-values"></td><td id="description">Character encoding of the input 
HTML</td></tr><tr><td id="name"><strong>Element Insert Location 
Type</strong></td><td id="default-value">append-html</td><td 
id="allowable-values"><ul><li>append-html</li><li>prepend-html</li></ul></td><td
 id="description">Controls whether the new element is prepended or appended to 
the children of the Element located by the CSS selector. EX: prepended value 
'&lt;b&gt;Hi&lt;/b&gt;' inside of Element (using CSS Selector 'p') 
'&lt;p&gt;There&lt;/p&gt;' would result in 
'&lt;p&gt;&lt;b&gt;Hi&lt;/b&gt;There&lt;/p&gt;'. Appending the value would 
result in '&lt;p&gt;There&lt;b&gt;Hi&lt;/b&gt;&lt;/p&gt;'</td></tr><tr><td 
id="name"><strong>Put Value</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Value used when creating the 
new Element. Value should be a valid HTML element. The text should be suppli
 ed unencoded: characters like '&lt;', '&gt;', etc will be properly HTML 
encoded in the resulting output.<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>element 
not found</td><td>Element could not be found in the HTML document. The original 
HTML input will remain in the FlowFile content unchanged. Relationship 
'original' will not be invoked in this 
scenario.</td></tr><tr><td>success</td><td>Successfully parsed HTML 
element</td></tr><tr><td>original</td><td>The original HTML 
input</td></tr><tr><td>invalid html</td><td>The input HTML syntax is 
invalid</td></tr></table><h3>Reads Attributes: </h3>None specified.<h3>Writes 
Attributes: </h3>None specified.<h3>State management: </h3>This component does 
not store state.<h3>Restricted: </h3>This component is not restricted.<h3>Input 
requirement: </h3>This component requires an incoming relationship.<h3>System 
Resource 
 Considerations:</h3>None specified.<h3>See Also:</h3><p><a 
href="../org.apache.nifi.GetHTMLElement/index.html">GetHTMLElement</a>, <a 
href="../org.apache.nifi.ModifyHTMLElement/index.html">ModifyHTMLElement</a></p></body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-http-context-map-nar/1.6.0/org.apache.nifi.http.StandardHttpContextMap/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-http-context-map-nar/1.6.0/org.apache.nifi.http.StandardHttpContextMap/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-http-context-map-nar/1.6.0/org.apache.nifi.http.StandardHttpContextMap/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-http-context-map-nar/1.6.0/org.apache.nifi.http.StandardHttpContextMap/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>StandardHttpContextMap</title><link 
rel="stylesheet" href="../../../../../css/component-usage.css" 
type="text/css"></link></head><script type="text/javascript">window.onload = 
function(){if(self==top) { document.getElementById('nameHeader').style.display 
= "inherit"; } }</script><body><h1 id="nameHeader" style="display: 
none;">StandardHttpContextMap</h1><h2>Description: </h2><p>Provides the ability 
to store and retrieve HTTP requests and responses external to a Processor, so 
that multiple Processors can interact with the same HTTP request.</p><h3>Tags: 
</h3><p>http, request, response</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>Maximum Outstanding Requests</strong></td><td 
id="default-value">5000</td><td id="allowable-values"></td><td 
id="description">The maximum number of HTTP requests that can be outstanding at 
any one time. Any attempt to register an additional HTTP Request will cause an 
error</td></tr><tr><td id="name"><strong>Request Expiration</strong></td><td 
id="default-value">1 min</td><td id="allowable-values"></td><td 
id="description">Specifies how long an HTTP Request should be left unanswered 
before being evicted from the cache and being responded to with a Service 
Unavailable status code</td></tr></table><h3>State management: </h3>This 
component does not store state.<h3>Restricted: </h3>This component is not 
restricted.<h3>System Resource Considerations:</h3>None specified.<h3>See 
Also:</h3><p><a 
href="../../../nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.HandleHttpRequest/index.html">HandleHttpRequest</a>,
 <a href="../../../nifi-standard-nar/1.6.0/org.
 
apache.nifi.processors.standard.HandleHttpResponse/index.html">HandleHttpResponse</a></p></body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hwx-schema-registry-nar/1.6.0/org.apache.nifi.schemaregistry.hortonworks.HortonworksSchemaRegistry/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hwx-schema-registry-nar/1.6.0/org.apache.nifi.schemaregistry.hortonworks.HortonworksSchemaRegistry/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hwx-schema-registry-nar/1.6.0/org.apache.nifi.schemaregistry.hortonworks.HortonworksSchemaRegistry/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hwx-schema-registry-nar/1.6.0/org.apache.nifi.schemaregistry.hortonworks.HortonworksSchemaRegistry/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>HortonworksSchemaRegistry</title><link 
rel="stylesheet" href="../../../../../css/component-usage.css" 
type="text/css"></link></head><script type="text/javascript">window.onload = 
function(){if(self==top) { document.getElementById('nameHeader').style.display 
= "inherit"; } }</script><body><h1 id="nameHeader" style="display: 
none;">HortonworksSchemaRegistry</h1><h2>Description: </h2><p>Provides a Schema 
Registry Service that interacts with a Hortonworks Schema Registry, available 
at https://github.com/hortonworks/registry</p><h3>Tags: </h3><p>schema, 
registry, avro, hortonworks, hwx</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 Langua
 ge</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 Registry URL</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">URL 
of the schema registry that this Controller Service should connect to, 
including version. For example, 
http://localhost:9090/api/v1<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Cache Size</strong></td><td 
id="default-value">1000</td><td id="allowable-values"></td><td 
id="description">Specifies how many Schemas should be cached from the 
Hortonworks Schema Registry</td></tr><tr><td id="name"><strong>Cache 
Expiration</strong></td><td id="default-value">1 hour</td><td 
id="allowable-values"></td><td id="description">Specifies how long a Schema 
that is cached should remain in the cache. Once this time period elapses, a 
cached version of a schema will no longer be used, and the servi
 ce will have to communicate with the Hortonworks Schema Registry again in 
order to obtain the schema.</td></tr></table><h3>State management: </h3>This 
component does not store state.<h3>Restricted: </h3>This component is not 
restricted.<h3>System Resource Considerations:</h3>None specified.</body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-ignite-nar/1.6.0/org.apache.nifi.processors.ignite.cache.GetIgniteCache/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-ignite-nar/1.6.0/org.apache.nifi.processors.ignite.cache.GetIgniteCache/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-ignite-nar/1.6.0/org.apache.nifi.processors.ignite.cache.GetIgniteCache/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-ignite-nar/1.6.0/org.apache.nifi.processors.ignite.cache.GetIgniteCache/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>GetIgniteCache</title><link rel="stylesheet" 
href="../../../../../css/component-usage.css" 
type="text/css"></link></head><script type="text/javascript">window.onload = 
function(){if(self==top) { document.getElementById('nameHeader').style.display 
= "inherit"; } }</script><body><h1 id="nameHeader" style="display: 
none;">GetIgniteCache</h1><h2>Description: </h2><p>Get the byte array from 
Ignite Cache and adds it as the content of a FlowFile.The processor uses the 
value of FlowFile attribute (Ignite cache entry key) as the cache key lookup. 
If the entry corresponding to the key is not found in the cache an error 
message is associated with the FlowFile Note - The Ignite Kernel periodically 
outputs node performance statistics to the logs. This message  can be turned 
off by setting the log level for logger 'org.apache.ignite' to WARN in the 
logback.xml configuration file.</p><h3>Tags: </h3><p>Ignite, get, read, cache
 , key</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">Ignite Spring Properties Xml File</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Ignite spring configuration 
file, &lt;path&gt;/&lt;ignite-configuration&gt;.xml. If the configuration file 
is not provided, default Ignite configuration configuration is used which binds 
to 127.0.0.1:47500..47509</td></tr><tr><td id="name">Ignite Cache Name</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
name of the ignite cache</td></tr><tr><td id="name
 "><strong>Ignite Cache Entry Identifier</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">A 
FlowFile attribute, or attribute expression used for determining Ignite cache 
key for the Flow File content<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>All
 FlowFiles that are written to Ignite cache are routed to this 
relationship</td></tr><tr><td>failure</td><td>All FlowFiles that cannot be 
written to Ignite cache are routed to this 
relationship</td></tr></table><h3>Reads Attributes: </h3>None 
specified.<h3>Writes Attributes: </h3><table 
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>ignite.cache.get.failed.reason</td><td>The
 reason for getting entry from cache</td></tr></table><h3>State management: 
</h3>This component does not store state.<h3>Restricted: </h3>This component is 
not
  restricted.<h3>Input requirement: </h3>This component requires an incoming 
relationship.<h3>System Resource Considerations:</h3>None specified.<h3>See 
Also:</h3><p><a 
href="../org.apache.nifi.processors.ignite.cache.PutIgniteCache/index.html">PutIgniteCache</a></p></body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-ignite-nar/1.6.0/org.apache.nifi.processors.ignite.cache.PutIgniteCache/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-ignite-nar/1.6.0/org.apache.nifi.processors.ignite.cache.PutIgniteCache/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-ignite-nar/1.6.0/org.apache.nifi.processors.ignite.cache.PutIgniteCache/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-ignite-nar/1.6.0/org.apache.nifi.processors.ignite.cache.PutIgniteCache/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>PutIgniteCache</title><link rel="stylesheet" 
href="../../../../../css/component-usage.css" 
type="text/css"></link></head><script type="text/javascript">window.onload = 
function(){if(self==top) { document.getElementById('nameHeader').style.display 
= "inherit"; } }</script><body><h1 id="nameHeader" style="display: 
none;">PutIgniteCache</h1><h2>Description: </h2><p>Stream the contents of a 
FlowFile to Ignite Cache using DataStreamer. The processor uses the value of 
FlowFile attribute (Ignite cache entry key) as the cache key and the byte array 
of the FlowFile as the value of the cache entry value.  Both the string key and 
a  non-empty byte array value are required otherwise the FlowFile is 
transferred to the failure relation. Note - The Ignite Kernel periodically 
outputs node performance statistics to the logs. This message  can be turned 
off by setting the log level for logger 'org.apache.ignite' to WARN in the l
 ogback.xml configuration file.</p><h3>Tags: </h3><p>Ignite, insert, update, 
stream, write, put, cache, key</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">Ignite Spring Properties Xml File</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Ignite spring configuration 
file, &lt;path&gt;/&lt;ignite-configuration&gt;.xml. If the configuration file 
is not provided, default Ignite configuration configuration is used which binds 
to 127.0.0.1:47500..47509</td></tr><tr><td id="name">Ignite Cache Name</td><td 
id="default-value"></td><td i
 d="allowable-values"></td><td id="description">The name of the ignite 
cache</td></tr><tr><td id="name"><strong>Batch Size For 
Entries</strong></td><td id="default-value">250</td><td 
id="allowable-values"></td><td id="description">Batch size for entries 
(1-500).</td></tr><tr><td id="name"><strong>Ignite Cache Entry 
Identifier</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">A FlowFile attribute, or 
attribute expression used for determining Ignite cache key for the Flow File 
content<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Data Streamer Per Node 
Parallel Operations</strong></td><td id="default-value">5</td><td 
id="allowable-values"></td><td id="description">Data streamer per node 
parallelism</td></tr><tr><td id="name"><strong>Data Streamer Per Node Buffer 
Size</strong></td><td id="default-value">250</td><td 
id="allowable-values"></td><td id="description">Data streamer per node buffer 
size (1-
 500).</td></tr><tr><td id="name"><strong>Data Streamer Auto Flush Frequency in 
millis</strong></td><td id="default-value">10</td><td 
id="allowable-values"></td><td id="description">Data streamer flush interval in 
millis seconds</td></tr><tr><td id="name"><strong>Data Streamer Allow 
Override</strong></td><td id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Whether to override values already in the 
cache</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 written to Ignite cache are routed to this 
relationship</td></tr><tr><td>failure</td><td>All FlowFiles that cannot be 
written to Ignite cache are routed to this 
relationship</td></tr></table><h3>Reads Attributes: </h3>None 
specified.<h3>Writes Attributes: </h3><table 
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>ignite.cache.batch.flow.fi
 le.total.count</td><td>The total number of FlowFile in the 
batch</td></tr><tr><td>ignite.cache.batch.flow.file.item.number</td><td>The 
item number of FlowFile in the 
batch</td></tr><tr><td>ignite.cache.batch.flow.file.successful.number</td><td>The
 successful FlowFile item 
number</td></tr><tr><td>ignite.cache.batch.flow.file.successful.count</td><td>The
 number of successful 
FlowFiles</td></tr><tr><td>ignite.cache.batch.flow.file.failed.number</td><td>The
 failed FlowFile item 
number</td></tr><tr><td>ignite.cache.batch.flow.file.failed.count</td><td>The 
total number of failed FlowFiles in the 
batch</td></tr><tr><td>ignite.cache.batch.flow.file.failed.reason</td><td>The 
failed reason attribute key</td></tr></table><h3>State management: </h3>This 
component does not store state.<h3>Restricted: </h3>This component is not 
restricted.<h3>Input requirement: </h3>This component requires an incoming 
relationship.<h3>System Resource Considerations:</h3><table 
id="system-resource-considerations">
 <tr><th>Resource</th><th>Description</th></tr><tr><td>MEMORY</td><td>An 
instance of this component can cause high usage of this system resource.  
Multiple instances or high concurrency settings may result a degradation of 
performance.</td></tr></table><h3>See Also:</h3><p><a 
href="../org.apache.nifi.processors.ignite.cache.GetIgniteCache/index.html">GetIgniteCache</a></p></body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-influxdb-nar/1.6.0/org.apache.nifi.processors.influxdb.PutInfluxDB/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-influxdb-nar/1.6.0/org.apache.nifi.processors.influxdb.PutInfluxDB/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-influxdb-nar/1.6.0/org.apache.nifi.processors.influxdb.PutInfluxDB/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-influxdb-nar/1.6.0/org.apache.nifi.processors.influxdb.PutInfluxDB/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>PutInfluxDB</title><link rel="stylesheet" 
href="../../../../../css/component-usage.css" 
type="text/css"></link></head><script type="text/javascript">window.onload = 
function(){if(self==top) { document.getElementById('nameHeader').style.display 
= "inherit"; } }</script><body><h1 id="nameHeader" style="display: 
none;">PutInfluxDB</h1><h2>Description: </h2><p>Processor to write the content 
of a FlowFile in 'line protocol'.  Please check details of the 'line protocol' 
in InfluxDB documentation (https://www.influxdb.com/).   The flow file can 
contain single measurement point or multiple measurement points separated by 
line seperator.  The timestamp (last field) should be in nano-seconds 
resolution.</p><h3>Tags: </h3><p>influxdb, measurement, insert, write, put, 
timeseries</p><h3>Properties: </h3><p>In the list below, the names of required 
properties appear in <strong>bold</strong>. Any other properties (not in bold)
  are considered optional. The table also indicates any default values, whether 
a property supports the <a 
href="../../../../../html/expression-language-guide.html">NiFi Expression 
Language</a>, and whether a property is considered "sensitive", meaning that 
its value will be encrypted. Before entering a value in a sensitive property, 
ensure that the <strong>nifi.properties</strong> file has an entry for the 
property <strong>nifi.sensitive.props.key</strong>.</p><table 
id="properties"><tr><th>Name</th><th>Default Value</th><th>Allowable 
Values</th><th>Description</th></tr><tr><td id="name"><strong>Database 
Name</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">InfluxDB database to connect 
to<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
id="name"><strong>InfluxDB connection URL</strong></td><td 
id="default-value">http://localhost:8086</td><td id="allowable-values"></td><td 
id="description">InfluxDB URL to connect to
 . Eg: http://influxdb:8086<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>InfluxDB Max Connection Time 
Out (seconds)</strong></td><td id="default-value">0 seconds</td><td 
id="allowable-values"></td><td id="description">The maximum time for 
establishing connection to the InfluxDB</td></tr><tr><td 
id="name">Username</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Username for accessing 
InfluxDB<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Password</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Password for user<br/><strong>Sensitive Property: 
true</strong><br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Character Set</strong></td><td 
id="default-value">UTF-8</td><td id="allowable-values"></td><td 
id="description">Specifies the character set of the document 
data.<br/><strong>Supports Express
 ion Language: true</strong></td></tr><tr><td id="name"><strong>Consistency 
Level</strong></td><td id="default-value">ONE</td><td 
id="allowable-values"><ul><li>One <img 
src="../../../../../html/images/iconInfo.png" alt="Return success when one node 
has responded with write success" title="Return success when one node has 
responded with write success"></img></li><li>Any <img 
src="../../../../../html/images/iconInfo.png" alt="Return success when any 
nodes have responded with write success" title="Return success when any nodes 
have responded with write success"></img></li><li>All <img 
src="../../../../../html/images/iconInfo.png" alt="Return success when all 
nodes have responded with write success" title="Return success when all nodes 
have responded with write success"></img></li><li>Quorum <img 
src="../../../../../html/images/iconInfo.png" alt="Return success when a 
majority of nodes have responded with write success" title="Return success when 
a majority of nodes have responded with w
 rite success"></img></li></ul></td><td id="description">InfluxDB consistency 
level<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
id="name"><strong>Retention Policy</strong></td><td 
id="default-value">autogen</td><td id="allowable-values"></td><td 
id="description">Retention policy for the saving the 
records<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Max size of 
records</strong></td><td id="default-value">1 MB</td><td 
id="allowable-values"></td><td id="description">Maximum size of records allowed 
to be posted in one batch<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>failure-max-size</td><td>FlowFiles
 exceeding max records size are routed to this 
relationship</td></tr><tr><td>retry</td><td>FlowFiles were not saved to 
InfluxDB due to retryable exception are routed to this relationship</t
 d></tr><tr><td>success</td><td>Successful FlowFiles that are saved to InfluxDB 
are routed to this relationship</td></tr><tr><td>failure</td><td>FlowFiles were 
not saved to InfluxDB are routed to this 
relationship</td></tr></table><h3>Reads Attributes: </h3>None 
specified.<h3>Writes Attributes: </h3><table 
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>influxdb.error.message</td><td>InfluxDB
 error message</td></tr></table><h3>State management: </h3>This component does 
not store state.<h3>Restricted: </h3>This component is not restricted.<h3>Input 
requirement: </h3>This component requires an incoming relationship.<h3>System 
Resource Considerations:</h3>None specified.</body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-jms-processors-nar/1.6.0/org.apache.nifi.jms.cf.JMSConnectionFactoryProvider/additionalDetails.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-jms-processors-nar/1.6.0/org.apache.nifi.jms.cf.JMSConnectionFactoryProvider/additionalDetails.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-jms-processors-nar/1.6.0/org.apache.nifi.jms.cf.JMSConnectionFactoryProvider/additionalDetails.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-jms-processors-nar/1.6.0/org.apache.nifi.jms.cf.JMSConnectionFactoryProvider/additionalDetails.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1,56 @@
+<!DOCTYPE html>
+<html lang="en">
+    <!--
+      Licensed to the Apache Software Foundation (ASF) under one or more
+      contributor license agreements.  See the NOTICE file distributed with
+      this work for additional information regarding copyright ownership.
+      The ASF licenses this file to You under the Apache License, Version 2.0
+      (the "License"); you may not use this file except in compliance with
+      the License.  You may obtain a copy of the License at
+          http://www.apache.org/licenses/LICENSE-2.0
+      Unless required by applicable law or agreed to in writing, software
+      distributed under the License is distributed on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+      See the License for the specific language governing permissions and
+      limitations under the License.
+    -->
+    <head>
+        <meta charset="utf-8" />
+        <title>JMSConnectionFactoryProvider</title>
+        <link rel="stylesheet" href="../../../../../css/component-usage.css" 
type="text/css" />
+    </head>
+
+    <body>
+        <h2>Description:</h2>
+        <p>
+            This ControllerService serves as a general factory service to 
serving vendor specific 
+            instances of the <i>javax.jms.ConnectionFactory</i>. It does so by 
allowing user to 
+            configure vendor specific properties as well as point to the 
location of the vendor 
+            provided JMS client libraries so the correct implementation of the 
<i>javax.jms.ConnectionFactory</i>
+            can be found, loaded, instantiated and served to the dependent 
Processors (see PublishJMS, ConsumeJMS).
+        </p>
+        <p>
+            To accommodate variety of JMS vendors and their implementation of 
the <i>ConnectionFactory</i> 
+            this ControllerService exposes only 3 static configuration 
properties that are common across many implementations 
+            of the <i>ConnectionFactory</i>. The rest of the configuration 
properties are set following 
+            <a 
href="http://docstore.mik.ua/orelly/java-ent/jnut/ch06_02.htm";>Java Beans</a> 
convention (see below).
+           </p>
+           <p>
+        The 3 static configuration properties are:
+        <ul>
+                 <li><b>MQ ConnectionFactory Implementation</b> - A fully 
qualified name of the JMS ConnectionFactory implementation 
+                        class (i.e., 
org.apache.activemq.ActiveMQConnectionFactory)</li>
+          <li><b>MQ Client Libraries path</b> - Path to the directory with 
additional resources (i.e., JARs, configuration files etc.) to be added 
+                                                       to the classpath. Such 
resources typically represent target MQ client libraries for the 
ConnectionFactory 
+                                                       implementation. It is 
optional if you are using Apache ActiveMQ since its libraries are distributed 
with this component.</li>
+          <li><b>Broker URI</b> - URI pointing to the network location of the 
JMS Message broker. For example, 'tcp://myhost:61616' for ActiveMQ or simply 
'myhost:1414'.</li>
+        </ul>
+        The rest of the properties are set as Dynamic Properties following <a 
href="http://docstore.mik.ua/orelly/java-ent/jnut/ch06_02.htm";>Java Beans</a> 
+        convention where a property name is derived from the <i>set*</i> 
method of the vendor specific ConnectionFactory's implementation.
+        For example, 
<i>com.ibm.mq.jms.MQConnectionFactory.setChannel(String)</i> would imply 
'channel' property and 
+        <i>com.ibm.mq.jms.MQConnectionFactory.setTransportType(int)</i> would 
imply 'transportType' property.
+        For the list of available properties please consult vendor provided 
documentation. Here is an example for 
+        <a 
href="https://www-01.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.javadoc.doc/WMQJMSClasses/com/ibm/mq/jms/MQQueueConnectionFactory.html";>IBM's
 com.ibm.mq.jms.MQConnectionFactory</a>
+        </p>
+    </body>
+</html>

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-jms-processors-nar/1.6.0/org.apache.nifi.jms.cf.JMSConnectionFactoryProvider/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-jms-processors-nar/1.6.0/org.apache.nifi.jms.cf.JMSConnectionFactoryProvider/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-jms-processors-nar/1.6.0/org.apache.nifi.jms.cf.JMSConnectionFactoryProvider/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-jms-processors-nar/1.6.0/org.apache.nifi.jms.cf.JMSConnectionFactoryProvider/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>JMSConnectionFactoryProvider</title><link 
rel="stylesheet" href="../../../../../css/component-usage.css" 
type="text/css"></link></head><script type="text/javascript">window.onload = 
function(){if(self==top) { document.getElementById('nameHeader').style.display 
= "inherit"; } }</script><body><h1 id="nameHeader" style="display: 
none;">JMSConnectionFactoryProvider</h1><h2>Description: </h2><p>Provides a 
generic service to create vendor specific javax.jms.ConnectionFactory 
implementations. ConnectionFactory can be served once this service is 
configured successfully</p><p><a href="additionalDetails.html">Additional 
Details...</a></p><h3>Tags: </h3><p>jms, messaging, integration, queue, topic, 
publish, subscribe</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>MQ ConnectionFactory Implementation</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">A 
fully qualified name of the JMS ConnectionFactory implementation class (i.e., 
org.apache.activemq.ActiveMQConnectionFactory)<br/><strong>Supports Expression 
Language: true</strong></td></tr><tr><td id="name"><strong>MQ Client Libraries 
path (i.e., /usr/jms/lib)</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Path to the directory with 
additional resources (i.e., JARs, configuration files etc.) to be added to the 
classpath. Such resources typically represent target MQ client libraries for 
the ConnectionFactory implementation.<br/><strong>S
 upports Expression Language: true</strong></td></tr><tr><td 
id="name"><strong>Broker URI</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">URI pointing to the network 
location of the JMS Message broker. For example, 'tcp://myhost:61616' for 
ActiveMQ or 'myhost:1414' for IBM MQ<br/><strong>Supports Expression Language: 
true</strong></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>Implementations: </strong><a 
href="../../../nifi-ssl-context-service-nar/1.6.0/org.apache.nifi.ssl.StandardSSLContextService/index.html">StandardSSLContextService</a><br/><a
 
href="../../../nifi-ssl-context-service-nar/1.6.0/org.apache.nifi.ssl.StandardRestrictedSSLContextService/index.html">StandardRestrictedSSLContextService</a></td><td
 id="description">The SSL Context Service used to provide client certificate 
information for TLS/SSL
  connections.</td></tr></table><h3>Dynamic Properties: </h3><p>Dynamic 
Properties allow the user to specify both the name and value of a 
property.<table 
id="dynamic-properties"><tr><th>Name</th><th>Value</th><th>Description</th></tr><tr><td
 id="name">The name of a Connection Factory configuration property.</td><td 
id="value">The value of a given Connection Factory configuration 
property.</td><td>The properties that are set following Java Beans convention 
where a property name is derived from the 'set*' method of the vendor specific 
ConnectionFactory's implementation. For example, 
'com.ibm.mq.jms.MQConnectionFactory.setChannel(String)' would imply 'channel' 
property and 'com.ibm.mq.jms.MQConnectionFactory.setTransportType(int)' would 
imply 'transportType' property.</td></tr></table></p><h3>State management: 
</h3>This component does not store state.<h3>Restricted: </h3>This component is 
not restricted.<h3>System Resource Considerations:</h3>None specified.<h3>See 
Also:</h3><p><a href=
 "../org.apache.nifi.jms.processors.ConsumeJMS/index.html">ConsumeJMS</a>, <a 
href="../org.apache.nifi.jms.processors.PublishJMS/index.html">PublishJMS</a></p></body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-jms-processors-nar/1.6.0/org.apache.nifi.jms.processors.ConsumeJMS/additionalDetails.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-jms-processors-nar/1.6.0/org.apache.nifi.jms.processors.ConsumeJMS/additionalDetails.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-jms-processors-nar/1.6.0/org.apache.nifi.jms.processors.ConsumeJMS/additionalDetails.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-jms-processors-nar/1.6.0/org.apache.nifi.jms.processors.ConsumeJMS/additionalDetails.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1,57 @@
+<!DOCTYPE html>
+<html lang="en">
+<!--
+  Licensed to the Apache Software Foundation (ASF) under one or more
+  contributor license agreements.  See the NOTICE file distributed with
+  this work for additional information regarding copyright ownership.
+  The ASF licenses this file to You under the Apache License, Version 2.0
+  (the "License"); you may not use this file except in compliance with
+  the License.  You may obtain a copy of the License at
+      http://www.apache.org/licenses/LICENSE-2.0
+  Unless required by applicable law or agreed to in writing, software
+  distributed under the License is distributed on an "AS IS" BASIS,
+  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+  See the License for the specific language governing permissions and
+  limitations under the License.
+-->
+<head>
+    <meta charset="utf-8" />
+    <title>ConsumeJMS</title>
+    <link rel="stylesheet" href="../../../../../css/component-usage.css" 
type="text/css" />
+</head>
+
+<body>
+<h2>Summary</h2>
+<p>
+    This processor consumes messages from JMS compliant messaging system and 
converts them to a FlowFile to be routed to the next component in the flow.
+</p>
+<p>
+    This processor does two things. It constructs FlowFile by extracting 
information from the consumed JMS message including body, standard 
+    <a 
href="http://docs.spring.io/spring-integration/docs/4.2.0.RELEASE/api/org/springframework/integration/jms/JmsHeaders.html";>JMS
 Headers</a> and Properties.
+    The message body is written to a FlowFile while standard JMS Headers and 
Properties are set as FlowFile attributes.
+</p>
+
+<h2>Configuration Details</h2>
+<p>
+    At the time of writing this document it only defines the essential 
configuration properties which are suitable for most cases. 
+    Other properties will be defined later as this component progresses.
+    Configuring ConsumeJMS:
+</p>
+<ol>
+    <li><b>User Name</b> - [OPTIONAL] User Name used for authentication and 
authorization when this processor obtains <i>javax.jms.Connection</i> 
+    from the pre-configured <i>javax.jms.ConnectionFactory</i> (see below).
+    </li>
+    <li><b>Password</b> - [OPTIONAL] Password used in conjunction with <b>User 
Name</b>.
+    </li>
+    <li><b>Destination Name</b> - [REQUIRED] the name of the 
<i>javax.jms.Destination</i>. 
+    Usually provided by administrator (e.g., 'topic://myTopic'). 
+    </li>
+    <li><b>Destination Type</b> - [OPTIONAL] the type of the 
<i>javax.jms.Destination</i>. Could be one of 'QUEUE' or 'TOPIC'
+    Usually provided by the administrator. Defaults to 'TOPIC'. 
+    </li>
+    <li><b>Connection Factory Service</b> - [REQUIRED] link to a 
pre-configured instance of org.apache.nifi.jms.cf.JMSConnectionFactoryProvider.
+    </li>
+</ol>
+
+</body>
+</html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-jms-processors-nar/1.6.0/org.apache.nifi.jms.processors.ConsumeJMS/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-jms-processors-nar/1.6.0/org.apache.nifi.jms.processors.ConsumeJMS/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-jms-processors-nar/1.6.0/org.apache.nifi.jms.processors.ConsumeJMS/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-jms-processors-nar/1.6.0/org.apache.nifi.jms.processors.ConsumeJMS/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ConsumeJMS</title><link rel="stylesheet" 
href="../../../../../css/component-usage.css" 
type="text/css"></link></head><script type="text/javascript">window.onload = 
function(){if(self==top) { document.getElementById('nameHeader').style.display 
= "inherit"; } }</script><body><h1 id="nameHeader" style="display: 
none;">ConsumeJMS</h1><h2>Description: </h2><p>Consumes JMS Message of type 
BytesMessage or TextMessage transforming its content to a FlowFile and 
transitioning it to 'success' relationship. JMS attributes such as headers and 
properties will be copied as FlowFile attributes.</p><p><a 
href="additionalDetails.html">Additional Details...</a></p><h3>Tags: 
</h3><p>jms, get, message, receive, consume</p><h3>Properties: </h3><p>In the 
list below, the names of required properties appear in <strong>bold</strong>. 
Any other properties (not in bold) are considered optional. The table also 
indicates any default values,
  whether a property supports the <a 
href="../../../../../html/expression-language-guide.html">NiFi Expression 
Language</a>, and whether a property is considered "sensitive", meaning that 
its value will be encrypted. Before entering a value in a sensitive property, 
ensure that the <strong>nifi.properties</strong> file has an entry for the 
property <strong>nifi.sensitive.props.key</strong>.</p><table 
id="properties"><tr><th>Name</th><th>Default Value</th><th>Allowable 
Values</th><th>Description</th></tr><tr><td id="name"><strong>Connection 
Factory Service</strong></td><td id="default-value"></td><td 
id="allowable-values"><strong>Controller Service API: 
</strong><br/>JMSConnectionFactoryProviderDefinition<br/><strong>Implementation:
 </strong><a 
href="../org.apache.nifi.jms.cf.JMSConnectionFactoryProvider/index.html">JMSConnectionFactoryProvider</a></td><td
 id="description">The Controller Service that is used to obtain 
ConnectionFactory</td></tr><tr><td id="name"><strong>Destination Nam
 e</strong></td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">The name of the JMS Destination. Usually provided by the 
administrator (e.g., 'topic://myTopic' or 'myTopic').<br/><strong>Supports 
Expression Language: true</strong></td></tr><tr><td 
id="name"><strong>Destination Type</strong></td><td 
id="default-value">QUEUE</td><td 
id="allowable-values"><ul><li>QUEUE</li><li>TOPIC</li></ul></td><td 
id="description">The type of the JMS Destination. Could be one of 'QUEUE' or 
'TOPIC'. Usually provided by the administrator. Defaults to 
'TOPIC</td></tr><tr><td id="name">User Name</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">User Name used for 
authentication and authorization.</td></tr><tr><td id="name">Password</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Password used for authentication and 
authorization.<br/><strong>Sensitive Property: true</strong></td></tr><tr><td 
id="name">Co
 nnection Client ID</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The client id to be set on the 
connection, if set. For durable non shared consumer this is mandatory, for all 
others it is optional, typically with shared consumers it is undesirable to be 
set. Please see JMS spec for further details<br/><strong>Supports Expression 
Language: true</strong></td></tr><tr><td id="name">Session Cache size</td><td 
id="default-value">1</td><td id="allowable-values"></td><td 
id="description">This property is deprecated and no longer has any effect on 
the Processor. It will be removed in a later version.</td></tr><tr><td 
id="name"><strong>Character Set</strong></td><td 
id="default-value">UTF-8</td><td id="allowable-values"></td><td 
id="description">The name of the character set to use to construct or interpret 
TextMessages<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Acknowledgement 
Mode</strong></td><td id="def
 ault-value">2</td><td id="allowable-values"><ul><li>AUTO_ACKNOWLEDGE (1) <img 
src="../../../../../html/images/iconInfo.png" alt="Automatically acknowledges a 
client's receipt of a message, regardless if NiFi session has been commited. 
Can result in data loss in the event where NiFi abruptly stopped before session 
was commited." title="Automatically acknowledges a client's receipt of a 
message, regardless if NiFi session has been commited. Can result in data loss 
in the event where NiFi abruptly stopped before session was 
commited."></img></li><li>CLIENT_ACKNOWLEDGE (2) <img 
src="../../../../../html/images/iconInfo.png" alt="(DEFAULT) Manually 
acknowledges a client's receipt of a message after NiFi Session was commited, 
thus ensuring no data loss" title="(DEFAULT) Manually acknowledges a client's 
receipt of a message after NiFi Session was commited, thus ensuring no data 
loss"></img></li><li>DUPS_OK_ACKNOWLEDGE (3) <img 
src="../../../../../html/images/iconInfo.png" alt="This acknowle
 dgment mode instructs the session to lazily acknowledge the delivery of 
messages. May result in both data duplication and data loss while achieving the 
best throughput." title="This acknowledgment mode instructs the session to 
lazily acknowledge the delivery of messages. May result in both data 
duplication and data loss while achieving the best 
throughput."></img></li></ul></td><td id="description">The JMS Acknowledgement 
Mode. Using Auto Acknowledge can cause messages to be lost on restart of NiFi 
but may provide better performance than Client Acknowledge.</td></tr><tr><td 
id="name">Durable subscription</td><td id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">If destination is Topic if present then make it the consumer 
durable. @see 
https://docs.oracle.com/javaee/7/api/javax/jms/Session.html#createDurableConsumer-javax.jms.Topic-java.lang.String-<br/><strong>Supports
 Expression Language: true</strong></td></tr><tr>
 <td id="name">Shared subscription</td><td id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">If destination is Topic if present then make it the consumer 
shared. @see 
https://docs.oracle.com/javaee/7/api/javax/jms/Session.html#createSharedConsumer-javax.jms.Topic-java.lang.String-<br/><strong>Supports
 Expression Language: true</strong></td></tr><tr><td id="name">Subscription 
Name</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">The name of the subscription to use if destination is Topic 
and is shared or durable.<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>All
 FlowFiles that are received from the JMS Destination are routed to this 
relationship</td></tr></table><h3>Reads Attributes: </h3>None 
specified.<h3>Writes Attributes: </h3><table id="wr
 
ites-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>jms_deliveryMode</td><td>The
 JMSDeliveryMode from the message 
header.</td></tr><tr><td>jms_expiration</td><td>The JMSExpiration from the 
message header.</td></tr><tr><td>jms_priority</td><td>The JMSPriority from the 
message header.</td></tr><tr><td>jms_redelivered</td><td>The JMSRedelivered 
from the message header.</td></tr><tr><td>jms_timestamp</td><td>The 
JMSTimestamp from the message 
header.</td></tr><tr><td>jms_correlationId</td><td>The JMSCorrelationID from 
the message header.</td></tr><tr><td>jms_messageId</td><td>The JMSMessageID 
from the message header.</td></tr><tr><td>jms_type</td><td>The JMSType from the 
message header.</td></tr><tr><td>jms_replyTo</td><td>The JMSReplyTo from the 
message header.</td></tr><tr><td>jms_destination</td><td>The JMSDestination 
from the message header.</td></tr><tr><td>other attributes</td><td>Each message 
property is written to an attribute.</td></tr></table><h3>State management
 : </h3>This component does not store state.<h3>Restricted: </h3>This component 
is not restricted.<h3>Input requirement: </h3>This component does not allow an 
incoming relationship.<h3>System Resource Considerations:</h3>None 
specified.<h3>See Also:</h3><p><a 
href="../org.apache.nifi.jms.processors.PublishJMS/index.html">PublishJMS</a>, 
<a 
href="../org.apache.nifi.jms.cf.JMSConnectionFactoryProvider/index.html">JMSConnectionFactoryProvider</a></p></body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-jms-processors-nar/1.6.0/org.apache.nifi.jms.processors.PublishJMS/additionalDetails.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-jms-processors-nar/1.6.0/org.apache.nifi.jms.processors.PublishJMS/additionalDetails.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-jms-processors-nar/1.6.0/org.apache.nifi.jms.processors.PublishJMS/additionalDetails.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-jms-processors-nar/1.6.0/org.apache.nifi.jms.processors.PublishJMS/additionalDetails.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1,60 @@
+<!DOCTYPE html>
+<html lang="en">
+<!--
+  Licensed to the Apache Software Foundation (ASF) under one or more
+  contributor license agreements.  See the NOTICE file distributed with
+  this work for additional information regarding copyright ownership.
+  The ASF licenses this file to You under the Apache License, Version 2.0
+  (the "License"); you may not use this file except in compliance with
+  the License.  You may obtain a copy of the License at
+      http://www.apache.org/licenses/LICENSE-2.0
+  Unless required by applicable law or agreed to in writing, software
+  distributed under the License is distributed on an "AS IS" BASIS,
+  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+  See the License for the specific language governing permissions and
+  limitations under the License.
+-->
+<head>
+    <meta charset="utf-8" />
+    <title>PublishJMS</title>
+    <link rel="stylesheet" href="../../../../../css/component-usage.css" 
type="text/css" />
+</head>
+
+<body>
+<h2>Summary</h2>
+<p>
+    This processor publishes the contents of the incoming FlowFile to a JMS 
compliant messaging system.
+</p>
+<p>
+    This processor does two things. It constructs JMS Message by extracting 
FlowFile contents (both body and attributes). 
+    Once message is constructed it is sent to a pre-configured JMS Destination.
+    Standard <a 
href="http://docs.spring.io/spring-integration/docs/4.2.0.RELEASE/api/org/springframework/integration/jms/JmsHeaders.html";>JMS
 Headers</a>
+    will be extracted from the FlowFile and set on <i>javax.jms.Message</i> as 
JMS headers while other 
+    FlowFile attributes will be set as properties of <i>javax.jms.Message</i>. 
Upon success the incoming FlowFile is transferred
+    to the <i>success</i> Relationship and upon failure FlowFile is
+    penalized and transferred to the <i>failure</i> Relationship.
+</p>
+<h2>Configuration Details</h2>
+<p>
+    At the time of writing this document it only defines the essential 
configuration properties which are suitable for most cases. 
+    Other properties will be defined later as this component progresses.
+    Configuring PublishJMS:
+</p>
+<ol>
+    <li><b>User Name</b> - [OPTIONAL] User Name used for authentication and 
authorization when this processor obtains <i>javax.jms.Connection</i> 
+    from the pre-configured <i>javax.jms.ConnectionFactory</i> (see below).
+    </li>
+    <li><b>Password</b> - [OPTIONAL] Password used in conjunction with <b>User 
Name</b>.
+    </li>
+    <li><b>Destination Name</b> - [REQUIRED] the name of the 
<i>javax.jms.Destination</i>. 
+    Usually provided by administrator (e.g., 'topic://myTopic'). 
+    </li>
+    <li><b>Destination Type</b> - [OPTIONAL] the type of the 
<i>javax.jms.Destination</i>. Could be one of 'QUEUE' or 'TOPIC'
+    Usually provided by the administrator. Defaults to 'TOPIC'. 
+    </li>
+    <li><b>Connection Factory Service</b> - [REQUIRED] link to a 
pre-configured instance of org.apache.nifi.jms.cf.JMSConnectionFactoryProvider.
+    </li>
+</ol>
+
+</body>
+</html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-jms-processors-nar/1.6.0/org.apache.nifi.jms.processors.PublishJMS/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-jms-processors-nar/1.6.0/org.apache.nifi.jms.processors.PublishJMS/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-jms-processors-nar/1.6.0/org.apache.nifi.jms.processors.PublishJMS/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-jms-processors-nar/1.6.0/org.apache.nifi.jms.processors.PublishJMS/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>PublishJMS</title><link rel="stylesheet" 
href="../../../../../css/component-usage.css" 
type="text/css"></link></head><script type="text/javascript">window.onload = 
function(){if(self==top) { document.getElementById('nameHeader').style.display 
= "inherit"; } }</script><body><h1 id="nameHeader" style="display: 
none;">PublishJMS</h1><h2>Description: </h2><p>Creates a JMS Message from the 
contents of a FlowFile and sends it to a JMS Destination (queue or topic) as 
JMS BytesMessage or TextMessage. FlowFile attributes will be added as JMS 
headers and/or properties to the outgoing JMS message.</p><p><a 
href="additionalDetails.html">Additional Details...</a></p><h3>Tags: 
</h3><p>jms, put, message, send, publish</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 va
 lues, whether a property supports the <a 
href="../../../../../html/expression-language-guide.html">NiFi Expression 
Language</a>, and whether a property is considered "sensitive", meaning that 
its value will be encrypted. Before entering a value in a sensitive property, 
ensure that the <strong>nifi.properties</strong> file has an entry for the 
property <strong>nifi.sensitive.props.key</strong>.</p><table 
id="properties"><tr><th>Name</th><th>Default Value</th><th>Allowable 
Values</th><th>Description</th></tr><tr><td id="name"><strong>Connection 
Factory Service</strong></td><td id="default-value"></td><td 
id="allowable-values"><strong>Controller Service API: 
</strong><br/>JMSConnectionFactoryProviderDefinition<br/><strong>Implementation:
 </strong><a 
href="../org.apache.nifi.jms.cf.JMSConnectionFactoryProvider/index.html">JMSConnectionFactoryProvider</a></td><td
 id="description">The Controller Service that is used to obtain 
ConnectionFactory</td></tr><tr><td id="name"><strong>Destinatio
 n Name</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The name of the JMS 
Destination. Usually provided by the administrator (e.g., 'topic://myTopic' or 
'myTopic').<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Destination 
Type</strong></td><td id="default-value">QUEUE</td><td 
id="allowable-values"><ul><li>QUEUE</li><li>TOPIC</li></ul></td><td 
id="description">The type of the JMS Destination. Could be one of 'QUEUE' or 
'TOPIC'. Usually provided by the administrator. Defaults to 
'TOPIC</td></tr><tr><td id="name">User Name</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">User Name used for 
authentication and authorization.</td></tr><tr><td id="name">Password</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Password used for authentication and 
authorization.<br/><strong>Sensitive Property: true</strong></td></tr><tr><td 
id="nam
 e">Connection Client ID</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The client id to be set on the 
connection, if set. For durable non shared consumer this is mandatory, for all 
others it is optional, typically with shared consumers it is undesirable to be 
set. Please see JMS spec for further details<br/><strong>Supports Expression 
Language: true</strong></td></tr><tr><td id="name">Session Cache size</td><td 
id="default-value">1</td><td id="allowable-values"></td><td 
id="description">This property is deprecated and no longer has any effect on 
the Processor. It will be removed in a later version.</td></tr><tr><td 
id="name"><strong>Message Body Type</strong></td><td 
id="default-value">bytes</td><td 
id="allowable-values"><ul><li>bytes</li><li>text</li></ul></td><td 
id="description">The type of JMS message body to construct.</td></tr><tr><td 
id="name"><strong>Character Set</strong></td><td 
id="default-value">UTF-8</td><td id="allowable-values"></t
 d><td id="description">The name of the character set to use to construct or 
interpret TextMessages<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>All
 FlowFiles that are sent to the JMS destination are routed to this 
relationship</td></tr><tr><td>failure</td><td>All FlowFiles that cannot be sent 
to JMS destination are routed to this relationship</td></tr></table><h3>Reads 
Attributes: </h3><table 
id="reads-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>jms_deliveryMode</td><td>This
 attribute becomes the JMSDeliveryMode message header. Must be an 
integer.</td></tr><tr><td>jms_expiration</td><td>This attribute becomes the 
JMSExpiration message header. Must be an 
integer.</td></tr><tr><td>jms_priority</td><td>This attribute becomes the 
JMSPriority message header. Must be an 
integer.</td></tr><tr><td>jms_redelivered</td><td>This attri
 bute becomes the JMSRedelivered message 
header.</td></tr><tr><td>jms_timestamp</td><td>This attribute becomes the 
JMSTimestamp message header. Must be a 
long.</td></tr><tr><td>jms_correlationId</td><td>This attribute becomes the 
JMSCorrelationID message header.</td></tr><tr><td>jms_type</td><td>This 
attribute becomes the JMSType message header. Must be an 
integer.</td></tr><tr><td>jms_replyTo</td><td>This attribute becomes the 
JMSReplyTo message header. Must be an 
integer.</td></tr><tr><td>jms_destination</td><td>This attribute becomes the 
JMSDestination message header. Must be an integer.</td></tr><tr><td>other 
attributes</td><td>All other attributes that do not start with jms_ are added 
as message properties.</td></tr></table><h3>Writes Attributes: </h3>None 
specified.<h3>State management: </h3>This component does not store 
state.<h3>Restricted: </h3>This component is not restricted.<h3>Input 
requirement: </h3>This component requires an incoming relationship.<h3>System 
Resource Co
 nsiderations:</h3><table 
id="system-resource-considerations"><tr><th>Resource</th><th>Description</th></tr><tr><td>MEMORY</td><td>An
 instance of this component can cause high usage of this system resource.  
Multiple instances or high concurrency settings may result a degradation of 
performance.</td></tr></table><h3>See Also:</h3><p><a 
href="../org.apache.nifi.jms.processors.ConsumeJMS/index.html">ConsumeJMS</a>, 
<a 
href="../org.apache.nifi.jms.cf.JMSConnectionFactoryProvider/index.html">JMSConnectionFactoryProvider</a></p></body></html>
\ No newline at end of file


Reply via email to