Author: danbress
Date: Thu Aug 13 01:19:25 2015
New Revision: 1695640
URL: http://svn.apache.org/r1695640
Log:
NIFI-785 Generate Processor/ControllerService/ReportingTask documentation and
push to website for 0.2.1
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.dbcp.DBCPConnectionPool/
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.dbcp.DBCPConnectionPool/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.mongodb.GetMongo/
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.mongodb.GetMongo/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.mongodb.PutMongo/
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.mongodb.PutMongo/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ExecuteSQL/
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ExecuteSQL/index.html
Modified:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.controller.ControllerStatusReportingTask/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.controller.MonitorDiskUsage/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.controller.MonitorMemory/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.distributed.cache.client.DistributedMapCacheClientService/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.distributed.cache.client.DistributedSetCacheClientService/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.distributed.cache.server.DistributedSetCacheServer/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.distributed.cache.server.map.DistributedMapCacheServer/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.http.StandardHttpContextMap/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.GeoEnrichIP/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.attributes.UpdateAttribute/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.hadoop.CreateHadoopSequenceFile/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.hadoop.FetchHDFS/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.hadoop.GetHDFS/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.hadoop.GetHDFSSequenceFile/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.hadoop.ListHDFS/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.hadoop.PutHDFS/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.hl7.ExtractHL7Attributes/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.hl7.RouteHL7/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.kafka.GetKafka/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.kafka.PutKafka/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.kite.ConvertCSVToAvro/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.kite.ConvertJSONToAvro/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.kite.StoreInKiteDataset/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.solr.GetSolr/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.solr.PutSolrContentStream/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.Base64EncodeContent/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.CompressContent/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ControlRate/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ConvertCharacterSet/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.DetectDuplicate/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.DistributeLoad/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.DuplicateFlowFile/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.EncryptContent/additionalDetails.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.EncryptContent/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.EvaluateJsonPath/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.EvaluateRegularExpression/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.EvaluateXPath/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.EvaluateXQuery/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ExecuteProcess/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ExecuteStreamCommand/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ExtractText/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.GenerateFlowFile/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.GetFile/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.GetHTTP/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.GetJMSQueue/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.GetJMSTopic/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.HandleHttpRequest/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.HandleHttpResponse/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.HashAttribute/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.HashContent/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.IdentifyMimeType/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.InvokeHTTP/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ListenHTTP/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ListenUDP/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.LogAttribute/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.MergeContent/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ModifyBytes/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.MonitorActivity/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.PostHTTP/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.PutEmail/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.PutFTP/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.PutFile/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.PutJMS/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.PutSFTP/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ReplaceText/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ReplaceTextWithMapping/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.RouteOnAttribute/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.RouteOnContent/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ScanAttribute/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ScanContent/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.SegmentContent/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.SplitContent/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.SplitJson/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.SplitText/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.SplitXml/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.TransformXml/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.UnpackContent/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ValidateXml/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.twitter.GetTwitter/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.yandex.YandexTranslate/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.reporting.ganglia.StandardGangliaReporter/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.ssl.StandardSSLContextService/index.html
nifi/site/trunk/docs/nifi-docs/index.html
Modified:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.controller.ControllerStatusReportingTask/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.controller.ControllerStatusReportingTask/index.html?rev=1695640&r1=1695639&r2=1695640&view=diff
==============================================================================
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.controller.ControllerStatusReportingTask/index.html
(original)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.controller.ControllerStatusReportingTask/index.html
Thu Aug 13 01:19:25 2015
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta
charset="utf-8"></meta><title>ControllerStatusReportingTask</title><link
rel="stylesheet" href="../../css/component-usage.css"
type="text/css"></link></head><body><h2>Description: </h2><p>Logs the 5-minute
stats that are shown in the NiFi Summary Page for Processors and Connections,
as well optionally logging the deltas between the previous iteration and the
current iteration. Processors' stats are logged using the
org.apache.nifi.controller.ControllerStatusReportingTask.Processors logger,
while Connections' stats are logged using the
org.apache.nifi.controller.ControllerStatusReportingTask.Connections logger.
These can be configured in the NiFi logging configuration to log to different
files, if desired.</p><p><a href="additionalDetails.html">Additional
Details...</a></p><h3>Tags: </h3><p>stats, log</p><h3>Properties: </h3><p>In
the list below, the names of required properties appear in
<strong>bold</strong>. Any other properties (not in b
old) 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>Show
Deltas</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 show the difference in values
between the current status and the previous
status</td></tr></table></body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta
charset="utf-8"></meta><title>ControllerStatusReportingTask</title><link
rel="stylesheet" href="../../css/component-usage.css"
type="text/css"></link></head><body><h2>Description: </h2><p>Logs the 5-minute
stats that are shown in the NiFi Summary Page for Processors and Connections,
as well optionally logging the deltas between the previous iteration and the
current iteration. Processors' stats are logged using the
org.apache.nifi.controller.ControllerStatusReportingTask.Processors logger,
while Connections' stats are logged using the
org.apache.nifi.controller.ControllerStatusReportingTask.Connections logger.
These can be configured in the NiFi logging configuration to log to different
files, if desired.</p><p><a href="additionalDetails.html">Additional
Details...</a></p><h3>Tags: </h3><p>stats, log</p><h3>Properties: </h3><p>In
the list below, the names of required properties appear in
<strong>bold</strong>. Any other properties (not in b
old) 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>Show Deltas</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 show the difference in values
between the current status and the previous
status</td></tr></table></body></html>
\ No newline at end of file
Modified:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.controller.MonitorDiskUsage/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.controller.MonitorDiskUsage/index.html?rev=1695640&r1=1695639&r2=1695640&view=diff
==============================================================================
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.controller.MonitorDiskUsage/index.html
(original)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.controller.MonitorDiskUsage/index.html
Thu Aug 13 01:19:25 2015
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta
charset="utf-8"></meta><title>MonitorDiskUsage</title><link rel="stylesheet"
href="../../css/component-usage.css"
type="text/css"></link></head><body><h2>Description: </h2><p>Checks the amount
of storage space available for the Content Repository and FlowFile Repository
and warns (via a log message and a System-Level Bulletin) if the partition on
which either repository exceeds some configurable threshold of storage
space</p><h3>Tags: </h3><p>disk, storage, warning, monitoring,
repo</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 prop
erty, 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>Content
Repository Threshold</strong></td><td id="default-value">80%</td><td
id="allowable-values"></td><td id="description">The threshold at which a
bulletin will be generated to indicate that the disk usage of the Content
Repository is of concern</td></tr><tr><td id="name"><strong>FlowFile Repository
Threshold</strong></td><td id="default-value">80%</td><td
id="allowable-values"></td><td id="description">The threshold at which a
bulletin will be generated to indicate that the disk usage of the FlowFile
Repository is of concern</td></tr></table></body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta
charset="utf-8"></meta><title>MonitorDiskUsage</title><link rel="stylesheet"
href="../../css/component-usage.css"
type="text/css"></link></head><body><h2>Description: </h2><p>Checks the amount
of storage space available for the Content Repository and FlowFile Repository
and warns (via a log message and a System-Level Bulletin) if the partition on
which either repository exceeds some configurable threshold of storage
space</p><h3>Tags: </h3><p>disk, storage, warning, monitoring,
repo</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>Content
Repository Threshold</strong></td><td id="default-value">80%</td><td
id="allowable-values"></td><td
id="description">The threshold at which a bulletin will be generated to
indicate that the disk usage of the Content Repository is of
concern</td></tr><tr><td id="name"><strong>FlowFile Repository
Threshold</strong></td><td id="default-value">80%</td><td
id="allowable-values"></td><td id="description">The threshold at which a
bulletin will be generated to indicate that the disk usage of the FlowFile
Repository is of concern</td></tr></table></body></html>
\ No newline at end of file
Modified:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.controller.MonitorMemory/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.controller.MonitorMemory/index.html?rev=1695640&r1=1695639&r2=1695640&view=diff
==============================================================================
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.controller.MonitorMemory/index.html
(original)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.controller.MonitorMemory/index.html
Thu Aug 13 01:19:25 2015
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta
charset="utf-8"></meta><title>MonitorMemory</title><link rel="stylesheet"
href="../../css/component-usage.css"
type="text/css"></link></head><body><h2>Description: </h2><p>Checks the amount
of Java Heap available in the JVM for a particular JVM Memory Pool. If the
amount of space used exceeds some configurable threshold, will warn (via a log
message and System-Level Bulletin) that the memory pool is exceeding this
threshold.</p><h3>Tags: </h3><p>monitor, memory, heap, jvm, gc, garbage
collection, warning</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 val
ue 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>Memory
Pool</strong></td><td id="default-value"></td><td
id="allowable-values"></td><td id="description">The name of the JVM Memory Pool
to monitor</td></tr><tr><td id="name"><strong>Usage Threshold</strong></td><td
id="default-value">65%</td><td id="allowable-values"></td><td
id="description">Indicates the threshold at which warnings should be
generated</td></tr><tr><td id="name">Reporting Interval</td><td
id="default-value"></td><td id="allowable-values"></td><td
id="description">Indicates how often this reporting task should report
bulletins while the memory utilization exceeds the configured
threshold</td></tr></table></body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta
charset="utf-8"></meta><title>MonitorMemory</title><link rel="stylesheet"
href="../../css/component-usage.css"
type="text/css"></link></head><body><h2>Description: </h2><p>Checks the amount
of Java Heap available in the JVM for a particular JVM Memory Pool. If the
amount of space used exceeds some configurable threshold, will warn (via a log
message and System-Level Bulletin) that the memory pool is exceeding this
threshold.</p><h3>Tags: </h3><p>monitor, memory, heap, jvm, gc, garbage
collection, warning</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>Memory Pool</strong></td><td id="default-value"></td><td
id="allowable-values"></td><t
d id="description">The name of the JVM Memory Pool to monitor</td></tr><tr><td
id="name"><strong>Usage Threshold</strong></td><td
id="default-value">65%</td><td id="allowable-values"></td><td
id="description">Indicates the threshold at which warnings should be
generated</td></tr><tr><td id="name">Reporting Interval</td><td
id="default-value"></td><td id="allowable-values"></td><td
id="description">Indicates how often this reporting task should report
bulletins while the memory utilization exceeds the configured
threshold</td></tr></table></body></html>
\ No newline at end of file
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.dbcp.DBCPConnectionPool/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.dbcp.DBCPConnectionPool/index.html?rev=1695640&view=auto
==============================================================================
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.dbcp.DBCPConnectionPool/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.dbcp.DBCPConnectionPool/index.html
Thu Aug 13 01:19:25 2015
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta
charset="utf-8"></meta><title>DBCPConnectionPool</title><link rel="stylesheet"
href="../../css/component-usage.css"
type="text/css"></link></head><body><h2>Description: </h2><p>Provides Database
Connection Pooling Service. Connections can be asked from pool and returned
after usage.</p><h3>Tags: </h3><p>dbcp, jdbc, database, connection, pooling,
store</p><h3>Properties: </h3><p>In the list below, the names of required
properties appear in <strong>bold</strong>. Any other properties (not in bold)
are considered optional. The table also indicates any default values, and
whether a property is 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 Connection URL</strong></td><td
id="default-value"></td><td id="allowable-values"></td><td id="description">A
database connection URL used to connect to a database. May contain database
system name, host, port, database name and some parameters. The exact syntax of
a database connection URL is specified by your DBMS.</td></tr><tr><td
id="name"><strong>Database Driver Class Name</strong></td><td
id="default-value"></td><td id="allowable-values"></td><td
id="description">Database driver class name</td></tr><tr><td id="name">Database
Driver Jar Url</td><td id="default-value"></td><td
id="allowable-values"></td><td id="description">Optional database driver jar
file path url. For example
'file:///var/tmp/mariadb-java-client-1.1.7.jar'</td></tr><tr><td
id="name"><strong>Database User</strong></td><td id="default-value"></td><td
id="allowable-values"></td><td id="description">Database user
name</td></tr><tr><td id="name">Password</td><td id="default-value
"></td><td id="allowable-values"></td><td id="description">The password for
the database user<br/><strong>Sensitive Property:
true</strong></td></tr><tr><td id="name"><strong>Max Wait Time</strong></td><td
id="default-value">500 millis</td><td id="allowable-values"></td><td
id="description">The maximum amount of time that the pool will wait (when there
are no available connections) for a connection to be returned before failing,
or -1 to wait indefinitely. </td></tr><tr><td id="name"><strong>Max Total
Connections</strong></td><td id="default-value">8</td><td
id="allowable-values"></td><td id="description">The maximum number of active
connections that can be allocated from this pool at the same time, or negative
for no limit.</td></tr></table></body></html>
\ No newline at end of file
Modified:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.distributed.cache.client.DistributedMapCacheClientService/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.distributed.cache.client.DistributedMapCacheClientService/index.html?rev=1695640&r1=1695639&r2=1695640&view=diff
==============================================================================
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.distributed.cache.client.DistributedMapCacheClientService/index.html
(original)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.distributed.cache.client.DistributedMapCacheClientService/index.html
Thu Aug 13 01:19:25 2015
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta
charset="utf-8"></meta><title>DistributedMapCacheClientService</title><link
rel="stylesheet" href="../../css/component-usage.css"
type="text/css"></link></head><body><h2>Description: </h2><p>Provides the
ability to communicate with a DistributedMapCacheServer. This can be used in
order to share a Map between nodes in a NiFi cluster</p><h3>Tags:
</h3><p>distributed, cache, state, map, cluster</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 <st
rong>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>Server
Hostname</strong></td><td id="default-value"></td><td
id="allowable-values"></td><td id="description">The name of the server that is
running the DistributedMapCacheServer service</td></tr><tr><td
id="name"><strong>Server Port</strong></td><td id="default-value">4557</td><td
id="allowable-values"></td><td id="description">The port on the remote server
that is to be used when communicating with the DistributedMapCacheServer
service</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">If specified, indicates the SSL Context
Service that is used to communicate with the remote server. If not specified,
communications will not be encrypted</td></tr><tr><td
id="name"><strong>Communications Timeout</strong></td><td id="default-value">30
secs</td><td id="allowable-values"></td><td id="description">Specifies how long
to wait when communicating with the remote server before determining that there
is a communications failure if data cannot be sent or
received</td></tr></table><h3>See Also:</h3><p><a
href="../org.apache.nifi.distributed.cache.server.map.DistributedMapCacheServer/index.html">DistributedMapCacheServer</a>,
<a
href="../org.apache.nifi.ssl.StandardSSLContextService/index.html">StandardSSLContextService</a></p></body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta
charset="utf-8"></meta><title>DistributedMapCacheClientService</title><link
rel="stylesheet" href="../../css/component-usage.css"
type="text/css"></link></head><body><h2>Description: </h2><p>Provides the
ability to communicate with a DistributedMapCacheServer. This can be used in
order to share a Map between nodes in a NiFi cluster</p><h3>Tags:
</h3><p>distributed, cache, state, map, cluster</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>Server
Hostname</strong></td><td id="default-value"></td><td
id="allowable-values"></td><td id="description">The name of the server that is
running the DistributedMapCacheServer service</td></tr><tr><t
d id="name"><strong>Server Port</strong></td><td
id="default-value">4557</td><td id="allowable-values"></td><td
id="description">The port on the remote server that is to be used when
communicating with the DistributedMapCacheServer service</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">If specified, indicates the SSL Context Service that is used
to communicate with the remote server. If not specified, communications will
not be encrypted</td></tr><tr><td id="name"><strong>Communications
Timeout</strong></td><td id="default-value">30 secs</td><td
id="allowable-values"></td><td id="description">Specifies how long to wait when
communicating with the remote server before determining that there is a commu
nications failure if data cannot be sent or received</td></tr></table><h3>See
Also:</h3><p><a
href="../org.apache.nifi.distributed.cache.server.map.DistributedMapCacheServer/index.html">DistributedMapCacheServer</a>,
<a
href="../org.apache.nifi.ssl.StandardSSLContextService/index.html">StandardSSLContextService</a></p></body></html>
\ No newline at end of file
Modified:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.distributed.cache.client.DistributedSetCacheClientService/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.distributed.cache.client.DistributedSetCacheClientService/index.html?rev=1695640&r1=1695639&r2=1695640&view=diff
==============================================================================
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.distributed.cache.client.DistributedSetCacheClientService/index.html
(original)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.distributed.cache.client.DistributedSetCacheClientService/index.html
Thu Aug 13 01:19:25 2015
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta
charset="utf-8"></meta><title>DistributedSetCacheClientService</title><link
rel="stylesheet" href="../../css/component-usage.css"
type="text/css"></link></head><body><h2>Description: </h2><p>Provides the
ability to communicate with a DistributedSetCacheServer. This can be used in
order to share a Set between nodes in a NiFi cluster</p><h3>Tags:
</h3><p>distributed, cache, state, set, cluster</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 <st
rong>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>Server
Hostname</strong></td><td id="default-value"></td><td
id="allowable-values"></td><td id="description">The name of the server that is
running the DistributedSetCacheServer service</td></tr><tr><td
id="name"><strong>Server Port</strong></td><td id="default-value">4557</td><td
id="allowable-values"></td><td id="description">The port on the remote server
that is to be used when communicating with the DistributedSetCacheServer
service</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">If specified, indicates the SSL Context
Service that is used to communicate with the remote server. If not specified,
communications will not be encrypted</td></tr><tr><td
id="name"><strong>Communications Timeout</strong></td><td id="default-value">30
secs</td><td id="allowable-values"></td><td id="description">Specifices how
long to wait when communicating with the remote server before determining that
there is a communications failure if data cannot be sent or
received</td></tr></table><h3>See Also:</h3><p><a
href="../org.apache.nifi.distributed.cache.server.DistributedSetCacheServer/index.html">DistributedSetCacheServer</a>,
<a
href="../org.apache.nifi.ssl.StandardSSLContextService/index.html">StandardSSLContextService</a></p></body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta
charset="utf-8"></meta><title>DistributedSetCacheClientService</title><link
rel="stylesheet" href="../../css/component-usage.css"
type="text/css"></link></head><body><h2>Description: </h2><p>Provides the
ability to communicate with a DistributedSetCacheServer. This can be used in
order to share a Set between nodes in a NiFi cluster</p><h3>Tags:
</h3><p>distributed, cache, state, set, cluster</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>Server
Hostname</strong></td><td id="default-value"></td><td
id="allowable-values"></td><td id="description">The name of the server that is
running the DistributedSetCacheServer service</td></tr><tr><t
d id="name"><strong>Server Port</strong></td><td
id="default-value">4557</td><td id="allowable-values"></td><td
id="description">The port on the remote server that is to be used when
communicating with the DistributedSetCacheServer service</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">If specified, indicates the SSL Context Service that is used
to communicate with the remote server. If not specified, communications will
not be encrypted</td></tr><tr><td id="name"><strong>Communications
Timeout</strong></td><td id="default-value">30 secs</td><td
id="allowable-values"></td><td id="description">Specifices how long to wait
when communicating with the remote server before determining that there is a
comm
unications failure if data cannot be sent or received</td></tr></table><h3>See
Also:</h3><p><a
href="../org.apache.nifi.distributed.cache.server.DistributedSetCacheServer/index.html">DistributedSetCacheServer</a>,
<a
href="../org.apache.nifi.ssl.StandardSSLContextService/index.html">StandardSSLContextService</a></p></body></html>
\ No newline at end of file
Modified:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.distributed.cache.server.DistributedSetCacheServer/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.distributed.cache.server.DistributedSetCacheServer/index.html?rev=1695640&r1=1695639&r2=1695640&view=diff
==============================================================================
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.distributed.cache.server.DistributedSetCacheServer/index.html
(original)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.distributed.cache.server.DistributedSetCacheServer/index.html
Thu Aug 13 01:19:25 2015
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta
charset="utf-8"></meta><title>DistributedSetCacheServer</title><link
rel="stylesheet" href="../../css/component-usage.css"
type="text/css"></link></head><body><h2>Description: </h2><p>Provides a set
(collection of unique values) cache that can be accessed over a socket.
Interaction with this service is typically accomplished via a
DistributedSetCacheClient service.</p><h3>Tags: </h3><p>distributed, set,
distinct, cache, server</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> fi
le 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>Port</strong></td><td id="default-value">4557</td><td
id="allowable-values"></td><td id="description">The port to listen on for
incoming connections</td></tr><tr><td id="name"><strong>Maximum Cache
Entries</strong></td><td id="default-value">10000</td><td
id="allowable-values"></td><td id="description">The maximum number of cache
entries that the cache can hold</td></tr><tr><td id="name"><strong>Eviction
Strategy</strong></td><td id="default-value">Least Frequently Used</td><td
id="allowable-values"><ul><li>Least Frequently Used</li><li>Least Recently
Used</li><li>First In, First Out</li></ul></td><td id="description">Determines
which strategy should be used to evict values from the cache to make room for
new entries</td></tr><tr><td id="name">Persistence Directory</td>
<td id="default-value"></td><td id="allowable-values"></td><td
id="description">If specified, the cache will be persisted in the given
directory; if not specified, the cache will be in-memory only</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">If specified, this service will be used to create an SSL
Context that will be used to secure communications; if not specified,
communications will not be secure</td></tr></table></body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta
charset="utf-8"></meta><title>DistributedSetCacheServer</title><link
rel="stylesheet" href="../../css/component-usage.css"
type="text/css"></link></head><body><h2>Description: </h2><p>Provides a set
(collection of unique values) cache that can be accessed over a socket.
Interaction with this service is typically accomplished via a
DistributedSetCacheClient service.</p><h3>Tags: </h3><p>distributed, set,
distinct, cache, server</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">4557</td><td
id="allowable-values"></td><td id="description">The port to listen on for
incoming connections</td></tr><tr><td
id="name"><strong>Maximum Cache Entries</strong></td><td
id="default-value">10000</td><td id="allowable-values"></td><td
id="description">The maximum number of cache entries that the cache can
hold</td></tr><tr><td id="name"><strong>Eviction Strategy</strong></td><td
id="default-value">Least Frequently Used</td><td
id="allowable-values"><ul><li>Least Frequently Used</li><li>Least Recently
Used</li><li>First In, First Out</li></ul></td><td id="description">Determines
which strategy should be used to evict values from the cache to make room for
new entries</td></tr><tr><td id="name">Persistence Directory</td><td
id="default-value"></td><td id="allowable-values"></td><td id="description">If
specified, the cache will be persisted in the given directory; if not
specified, the cache will be in-memory only</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>Impl
ementation:</strong><br/><a
href="../org.apache.nifi.ssl.StandardSSLContextService/index.html">StandardSSLContextService</a></td><td
id="description">If specified, this service will be used to create an SSL
Context that will be used to secure communications; if not specified,
communications will not be secure</td></tr></table></body></html>
\ No newline at end of file
Modified:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.distributed.cache.server.map.DistributedMapCacheServer/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.distributed.cache.server.map.DistributedMapCacheServer/index.html?rev=1695640&r1=1695639&r2=1695640&view=diff
==============================================================================
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.distributed.cache.server.map.DistributedMapCacheServer/index.html
(original)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.distributed.cache.server.map.DistributedMapCacheServer/index.html
Thu Aug 13 01:19:25 2015
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta
charset="utf-8"></meta><title>DistributedMapCacheServer</title><link
rel="stylesheet" href="../../css/component-usage.css"
type="text/css"></link></head><body><h2>Description: </h2><p>Provides a map
(key/value) cache that can be accessed over a socket. Interaction with this
service is typically accomplished via a DistributedMapCacheClient
service.</p><h3>Tags: </h3><p>distributed, cluster, map, cache, server,
key/value</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 a
n 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>Port</strong></td><td id="default-value">4557</td><td
id="allowable-values"></td><td id="description">The port to listen on for
incoming connections</td></tr><tr><td id="name"><strong>Maximum Cache
Entries</strong></td><td id="default-value">10000</td><td
id="allowable-values"></td><td id="description">The maximum number of cache
entries that the cache can hold</td></tr><tr><td id="name"><strong>Eviction
Strategy</strong></td><td id="default-value">Least Frequently Used</td><td
id="allowable-values"><ul><li>Least Frequently Used</li><li>Least Recently
Used</li><li>First In, First Out</li></ul></td><td id="description">Determines
which strategy should be used to evict values from the cache to make room for
new entries</td></tr><tr><td id="name">Persistence Directory</td><td id="
default-value"></td><td id="allowable-values"></td><td id="description">If
specified, the cache will be persisted in the given directory; if not
specified, the cache will be in-memory only</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">If specified, this service will be used to create an SSL
Context that will be used to secure communications; if not specified,
communications will not be secure</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.ssl.StandardSSLContextService/index.html">StandardSSLContextService</a></p></body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta
charset="utf-8"></meta><title>DistributedMapCacheServer</title><link
rel="stylesheet" href="../../css/component-usage.css"
type="text/css"></link></head><body><h2>Description: </h2><p>Provides a map
(key/value) cache that can be accessed over a socket. Interaction with this
service is typically accomplished via a DistributedMapCacheClient
service.</p><h3>Tags: </h3><p>distributed, cluster, map, cache, server,
key/value</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">4557</td><td
id="allowable-values"></td><td id="description">The port to listen on for
incoming connections</td></tr><tr><td id="nam
e"><strong>Maximum Cache Entries</strong></td><td
id="default-value">10000</td><td id="allowable-values"></td><td
id="description">The maximum number of cache entries that the cache can
hold</td></tr><tr><td id="name"><strong>Eviction Strategy</strong></td><td
id="default-value">Least Frequently Used</td><td
id="allowable-values"><ul><li>Least Frequently Used</li><li>Least Recently
Used</li><li>First In, First Out</li></ul></td><td id="description">Determines
which strategy should be used to evict values from the cache to make room for
new entries</td></tr><tr><td id="name">Persistence Directory</td><td
id="default-value"></td><td id="allowable-values"></td><td id="description">If
specified, the cache will be persisted in the given directory; if not
specified, the cache will be in-memory only</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>Implementati
on:</strong><br/><a
href="../org.apache.nifi.ssl.StandardSSLContextService/index.html">StandardSSLContextService</a></td><td
id="description">If specified, this service will be used to create an SSL
Context that will be used to secure communications; if not specified,
communications will not be secure</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.ssl.StandardSSLContextService/index.html">StandardSSLContextService</a></p></body></html>
\ No newline at end of file
Modified:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.http.StandardHttpContextMap/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.http.StandardHttpContextMap/index.html?rev=1695640&r1=1695639&r2=1695640&view=diff
==============================================================================
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.http.StandardHttpContextMap/index.html
(original)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.http.StandardHttpContextMap/index.html
Thu Aug 13 01:19:25 2015
@@ -1 +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><body><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, 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>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>See Also:</h3><p><a
>href="../org.apache.nifi.processors.standard.HandleHttpRequest/index.html">HandleHttpRequest</a>,
> <a
>href="../org.apache.nifi.processors.standard.HandleHttpResponse/index.html">HandleHttpRespons
e</a></p></body></html>
\ No newline at end of file
+<!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><body><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. An
y 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>See Also:</h3><p><a
href="../org.apache.nifi.processors.standard.HandleHttpRequest/index.html">HandleHttpRequest</a>,
<a
href="../org.apache.nifi.processors.standard.HandleHttpResponse/index.html">HandleHttpResponse</a></p></body></html>
\ No newline at end of file
Modified:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.GeoEnrichIP/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.GeoEnrichIP/index.html?rev=1695640&r1=1695639&r2=1695640&view=diff
==============================================================================
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.GeoEnrichIP/index.html
(original)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.GeoEnrichIP/index.html
Thu Aug 13 01:19:25 2015
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta
charset="utf-8"></meta><title>GeoEnrichIP</title><link rel="stylesheet"
href="../../css/component-usage.css"
type="text/css"></link></head><body><h2>Description: </h2><p>Looks up
geolocation information for an IP address and adds the geo information to
FlowFile attributes. The geo data is provided as a MaxMind database. The
attribute that contains the IP address to lookup is provided by the 'IP Address
Attribute' property. If the name of the attribute provided is 'X', then the the
attributes added by enrichment will take the form
X.geo.<fieldName></p><h3>Tags: </h3><p>geo, enrich, ip,
maxmind</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 pro
perty 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>Geo Database
File</strong></td><td id="default-value"></td><td
id="allowable-values"></td><td id="description">Path to Maxmind Geo Enrichment
Database File</td></tr><tr><td id="name"><strong>IP Address
Attribute</strong></td><td id="default-value"></td><td
id="allowable-values"></td><td id="description">The name of an attribute whose
value is a dotted decimal IP address for which enrichment should
occur</td></tr></table><h3>Relationships: </h3><table
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>not
found</td><td>Where to route flow files after unsuccessfully enriching attrib
utes because no geo data was found</td></tr><tr><td>found</td><td>Where to
route flow files after successfully enriching attributes with geo
data</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>X.geo.lookup.micros</td><td>The
number of microseconds that the geo lookup
took</td></tr><tr><td>X.geo.city</td><td>The city identified for the IP
address</td></tr><tr><td>X.geo.latitude</td><td>The latitude identified for
this IP address</td></tr><tr><td>X.geo.longitude</td><td>The longitude
identified for this IP
address</td></tr><tr><td>X.geo.subdivision.N</td><td>Each subdivision that is
identified for this IP address is added with a one-up number appended to the
attribute name, starting with
0</td></tr><tr><td>X.geo.subdivision.isocode.N</td><td>The ISO code for the
subdivision that is identified by
X.geo.subdivision.N</td></tr><tr><td>X.geo.country</td><td>The country i
dentified for this IP
address</td></tr><tr><td>X.geo.country.isocode</td><td>The ISO Code for the
country identified</td></tr><tr><td>X.geo.postalcode</td><td>The postal code
for the country identified</td></tr></table></body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta
charset="utf-8"></meta><title>GeoEnrichIP</title><link rel="stylesheet"
href="../../css/component-usage.css"
type="text/css"></link></head><body><h2>Description: </h2><p>Looks up
geolocation information for an IP address and adds the geo information to
FlowFile attributes. The geo data is provided as a MaxMind database. The
attribute that contains the IP address to lookup is provided by the 'IP Address
Attribute' property. If the name of the attribute provided is 'X', then the the
attributes added by enrichment will take the form
X.geo.<fieldName></p><h3>Tags: </h3><p>geo, enrich, ip,
maxmind</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>Geo Database File</strong></td><td id="default-value"></td><td
id="allowable-values"></td><td id="description">Path to Maxmind Geo Enrichment
Database File</td></tr><tr><td id="name"><strong>IP Address
Attribute</strong></td><td id="default-value"></td><td
id="allowable-values"></td><td id="description">The name of an attribute whose
value is a dotted decimal IP address for which enrichment should
occur</td></tr></table><h3>Relationships: </h3><table
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>not
found</td><td>Where to route flow files after unsuccessfully enriching
attributes because no geo data was found</td></tr><tr><td>found</td><td>Where
to route flow files after successfully enriching attributes with geo
data</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>X.geo.lookup.micros</td><td>The
number of microseconds that the geo l
ookup took</td></tr><tr><td>X.geo.city</td><td>The city identified for the IP
address</td></tr><tr><td>X.geo.latitude</td><td>The latitude identified for
this IP address</td></tr><tr><td>X.geo.longitude</td><td>The longitude
identified for this IP
address</td></tr><tr><td>X.geo.subdivision.N</td><td>Each subdivision that is
identified for this IP address is added with a one-up number appended to the
attribute name, starting with
0</td></tr><tr><td>X.geo.subdivision.isocode.N</td><td>The ISO code for the
subdivision that is identified by
X.geo.subdivision.N</td></tr><tr><td>X.geo.country</td><td>The country
identified for this IP
address</td></tr><tr><td>X.geo.country.isocode</td><td>The ISO Code for the
country identified</td></tr><tr><td>X.geo.postalcode</td><td>The postal code
for the country identified</td></tr></table></body></html>
\ No newline at end of file
Modified:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.attributes.UpdateAttribute/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.attributes.UpdateAttribute/index.html?rev=1695640&r1=1695639&r2=1695640&view=diff
==============================================================================
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.attributes.UpdateAttribute/index.html
(original)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.attributes.UpdateAttribute/index.html
Thu Aug 13 01:19:25 2015
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta
charset="utf-8"></meta><title>UpdateAttribute</title><link rel="stylesheet"
href="../../css/component-usage.css"
type="text/css"></link></head><body><h2>Description: </h2><p>Updates the
Attributes for a FlowFile by using the Attribute Expression Language</p><p><a
href="additionalDetails.html">Additional Details...</a></p><h3>Tags:
</h3><p>attributes, modification, update, Attribute Expression
Language</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 pr
operty <strong>nifi.sensitive.props.key</strong>.</p><p>This component has no
required or optional properties.</p><h3>Dynamic Properties: </h3><p>Dynamic
Properties allow the user to specify both the name and value of a
property.<table
id="dynamic-properties"><tr><th>Name</th><th>Value</th><th>Description</th></tr><tr><td
id="name">A FlowFile attribute to update</td><td id="value">The value to set
it to</td><td>Updates a FlowFile attribute specified by the Dynamic Property's
key with the value specified by the Dynamic Property's
value<br/><strong>Supports Expression Language:
true</strong></td></tr></table></p><h3>Relationships: </h3><table
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>All
FlowFiles are routed to this relationship</td></tr></table><h3>Reads
Attributes: </h3>None specified.<h3>Writes Attributes: </h3><table
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>See
additional details</td><td>This processor may
write zero or more attributes as described in additional
details</td></tr></table></body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta
charset="utf-8"></meta><title>UpdateAttribute</title><link rel="stylesheet"
href="../../css/component-usage.css"
type="text/css"></link></head><body><h2>Description: </h2><p>Updates the
Attributes for a FlowFile by using the Attribute Expression Language</p><p><a
href="additionalDetails.html">Additional Details...</a></p><h3>Tags:
</h3><p>attributes, modification, update, Attribute Expression
Language</p><h3>Properties: </h3><p>This component has no required or optional
properties.</p><h3>Dynamic Properties: </h3><p>Dynamic Properties allow the
user to specify both the name and value of a property.<table
id="dynamic-properties"><tr><th>Name</th><th>Value</th><th>Description</th></tr><tr><td
id="name">A FlowFile attribute to update</td><td id="value">The value to set
it to</td><td>Updates a FlowFile attribute specified by the Dynamic Property's
key with the value specified by the Dynamic Property's
value<br/><strong>Supports Expression Langu
age: true</strong></td></tr></table></p><h3>Relationships: </h3><table
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>All
FlowFiles are routed to this relationship</td></tr></table><h3>Reads
Attributes: </h3>None specified.<h3>Writes Attributes: </h3><table
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>See
additional details</td><td>This processor may write zero or more attributes as
described in additional details</td></tr></table></body></html>
\ No newline at end of file
Modified:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.hadoop.CreateHadoopSequenceFile/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.hadoop.CreateHadoopSequenceFile/index.html?rev=1695640&r1=1695639&r2=1695640&view=diff
==============================================================================
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.hadoop.CreateHadoopSequenceFile/index.html
(original)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.hadoop.CreateHadoopSequenceFile/index.html
Thu Aug 13 01:19:25 2015
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta
charset="utf-8"></meta><title>CreateHadoopSequenceFile</title><link
rel="stylesheet" href="../../css/component-usage.css"
type="text/css"></link></head><body><h2>Description: </h2><p>Creates Hadoop
Sequence Files from incoming flow files</p><p><a
href="additionalDetails.html">Additional Details...</a></p><h3>Tags:
</h3><p>hadoop, sequence file, create, sequencefile</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.k
ey</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">Hadoop Configuration Resources</td><td id="default-value"></td><td
id="allowable-values"></td><td id="description">A file or comma separated list
of files which contains the Hadoop file system configuration. Without this,
Hadoop will search the classpath for a 'core-site.xml' and 'hdfs-site.xml' file
or will revert to a default configuration.</td></tr><tr><td
id="name">compression type</td><td id="default-value"></td><td
id="allowable-values"><ul><li>NONE</li><li>RECORD</li><li>BLOCK</li></ul></td><td
id="description">Type of compression to use when creating Sequence
File</td></tr></table><h3>Relationships: </h3><table
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>Generated
Sequence Files are sent to this
relationship</td></tr><tr><td>failure</td><td>Incoming files that failed to
generate a Sequence F
ile are sent to this relationship</td></tr></table><h3>Reads Attributes:
</h3>None specified.<h3>Writes Attributes: </h3>None specified.<h3>See
Also:</h3><p><a
href="../org.apache.nifi.processors.hadoop.PutHDFS/index.html">PutHDFS</a></p></body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta
charset="utf-8"></meta><title>CreateHadoopSequenceFile</title><link
rel="stylesheet" href="../../css/component-usage.css"
type="text/css"></link></head><body><h2>Description: </h2><p>Creates Hadoop
Sequence Files from incoming flow files</p><p><a
href="additionalDetails.html">Additional Details...</a></p><h3>Tags:
</h3><p>hadoop, sequence file, create, sequencefile</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">Hadoop Configuration
Resources</td><td id="default-value"></td><td id="allowable-values"></td><td
id="description">A file or comma separated list of files which contains the
Hadoop file system configuration. Without this, Hadoop will se
arch the classpath for a 'core-site.xml' and 'hdfs-site.xml' file or will
revert to a default configuration.</td></tr><tr><td id="name">compression
type</td><td id="default-value"></td><td
id="allowable-values"><ul><li>NONE</li><li>RECORD</li><li>BLOCK</li></ul></td><td
id="description">Type of compression to use when creating Sequence
File</td></tr></table><h3>Relationships: </h3><table
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>failure</td><td>Incoming
files that failed to generate a Sequence File are sent to this
relationship</td></tr><tr><td>success</td><td>Generated Sequence Files are sent
to this relationship</td></tr></table><h3>Reads Attributes: </h3>None
specified.<h3>Writes Attributes: </h3>None specified.<h3>See Also:</h3><p><a
href="../org.apache.nifi.processors.hadoop.PutHDFS/index.html">PutHDFS</a></p></body></html>
\ No newline at end of file
Modified:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.hadoop.FetchHDFS/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.hadoop.FetchHDFS/index.html?rev=1695640&r1=1695639&r2=1695640&view=diff
==============================================================================
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.hadoop.FetchHDFS/index.html
(original)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.hadoop.FetchHDFS/index.html
Thu Aug 13 01:19:25 2015
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta
charset="utf-8"></meta><title>FetchHDFS</title><link rel="stylesheet"
href="../../css/component-usage.css"
type="text/css"></link></head><body><h2>Description: </h2><p>Retrieves a file
from HDFS. The content of the incoming FlowFile is replaced by the content of
the file in HDFS. The file in HDFS is left intact without any changes being
made to it.</p><h3>Tags: </h3><p>hadoop, hdfs, get, ingest, fetch,
source</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 fo
r 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">Hadoop Configuration
Resources</td><td id="default-value"></td><td id="allowable-values"></td><td
id="description">A file or comma separated list of files which contains the
Hadoop file system configuration. Without this, Hadoop will search the
classpath for a 'core-site.xml' and 'hdfs-site.xml' file or will revert to a
default configuration.</td></tr><tr><td id="name"><strong>HDFS
Filename</strong></td><td id="default-value">${path}/${filename}</td><td
id="allowable-values"></td><td id="description">The name of the HDFS file to
retrieve<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>FlowFiles
will be routed to this relationship once they have been updated
with the content of the HDFS
file</td></tr><tr><td>comms.failure</td><td>FlowFiles will be routed to this
relationship if the content of the HDFS file cannot be retrieve due to a
communications failure. This generally indicates that the Fetch should be tried
again.</td></tr><tr><td>failure</td><td>FlowFiles will be routed to this
relationship if the content of the HDFS file cannot be retrieved and trying
again will likely not be helpful. This would occur, for instance, if the file
is not found or if there is a permissions issue</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>hdfs.failure.reason</td><td>When
a FlowFile is routed to 'failure', this attribute is added indicating why the
file could not be fetched from HDFS</td></tr></table><h3>See Also:</h3><p><a
href="../org.apache.nifi.processors.hadoop.ListHDFS/index.html">ListHDFS</a>,
<a href="../org.apache.nifi.p
rocessors.hadoop.GetHDFS/index.html">GetHDFS</a>, <a
href="../org.apache.nifi.processors.hadoop.PutHDFS/index.html">PutHDFS</a></p></body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta
charset="utf-8"></meta><title>FetchHDFS</title><link rel="stylesheet"
href="../../css/component-usage.css"
type="text/css"></link></head><body><h2>Description: </h2><p>Retrieves a file
from HDFS. The content of the incoming FlowFile is replaced by the content of
the file in HDFS. The file in HDFS is left intact without any changes being
made to it.</p><h3>Tags: </h3><p>hadoop, hdfs, get, ingest, fetch,
source</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">Hadoop Configuration Resources</td><td id="default-value"></td><td
id="al
lowable-values"></td><td id="description">A file or comma separated list of
files which contains the Hadoop file system configuration. Without this, Hadoop
will search the classpath for a 'core-site.xml' and 'hdfs-site.xml' file or
will revert to a default configuration.</td></tr><tr><td id="name"><strong>HDFS
Filename</strong></td><td id="default-value">${path}/${filename}</td><td
id="allowable-values"></td><td id="description">The name of the HDFS file to
retrieve<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</td><td>FlowFiles
will be routed to this relationship if the content of the HDFS file cannot be
retrieved and trying again will likely not be helpful. This would occur, for
instance, if the file is not found or if there is a permissions
issue</td></tr><tr><td>comms.failure</td><td>FlowFiles will be routed to this
relationship if the content of
the HDFS file cannot be retrieve due to a communications failure. This
generally indicates that the Fetch should be tried
again.</td></tr><tr><td>success</td><td>FlowFiles will be routed to this
relationship once they have been updated with the content of the HDFS
file</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>hdfs.failure.reason</td><td>When
a FlowFile is routed to 'failure', this attribute is added indicating why the
file could not be fetched from HDFS</td></tr></table><h3>See Also:</h3><p><a
href="../org.apache.nifi.processors.hadoop.ListHDFS/index.html">ListHDFS</a>,
<a href="../org.apache.nifi.processors.hadoop.GetHDFS/index.html">GetHDFS</a>,
<a
href="../org.apache.nifi.processors.hadoop.PutHDFS/index.html">PutHDFS</a></p></body></html>
\ No newline at end of file
Modified:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.hadoop.GetHDFS/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.hadoop.GetHDFS/index.html?rev=1695640&r1=1695639&r2=1695640&view=diff
==============================================================================
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.hadoop.GetHDFS/index.html
(original)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.hadoop.GetHDFS/index.html
Thu Aug 13 01:19:25 2015
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta
charset="utf-8"></meta><title>GetHDFS</title><link rel="stylesheet"
href="../../css/component-usage.css"
type="text/css"></link></head><body><h2>Description: </h2><p>Fetch files from
Hadoop Distributed File System (HDFS) into FlowFiles. This Processor will
delete the file from HDFS after fetching it.</p><h3>Tags: </h3><p>hadoop, HDFS,
get, fetch, 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, 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">Hadoop Configuration Resources</td><td id="default-value"></td><td
id="allowable-values"></td><td id="description">A file or comma separated list
of files which contains the Hadoop file system configuration. Without this,
Hadoop will search the classpath for a 'core-site.xml' and 'hdfs-site.xml' file
or will revert to a default configuration.</td></tr><tr><td
id="name"><strong>Directory</strong></td><td id="default-value"></td><td
id="allowable-values"></td><td id="description">The HDFS directory from which
files should be read</td></tr><tr><td id="name"><strong>Recurse
Subdirectories</strong></td><td id="default-value">true</td><td
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td
id="description">Indicates whether to pull files from subdirectories of the
HDFS directory</td></tr><tr><td id="name"><strong>Keep Sour
ce File</strong></td><td id="default-value">false</td><td
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td
id="description">Determines whether to delete the file from HDFS after it has
been successfully transferred. If true, the file will be fetched repeatedly.
This is intended for testing only.</td></tr><tr><td id="name">File Filter
Regex</td><td id="default-value"></td><td id="allowable-values"></td><td
id="description">A Java Regular Expression for filtering Filenames; if a filter
is supplied then only files whose names match that Regular Expression will be
fetched, otherwise all files will be fetched</td></tr><tr><td
id="name"><strong>Filter Match Name Only</strong></td><td
id="default-value">true</td><td
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td
id="description">If true then File Filter Regex will match on just the
filename, otherwise subdirectory names will be included with filename in the
regex comparison</td></tr><tr><td id="name"><
strong>Ignore Dotted 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">If true, files whose names begin with a dot (".") will be
ignored</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 (based on 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 (based on last modification date) will be
ignored</td></tr><tr><td id="name"><strong>Polling Interval</strong></td><td
id="default-value">0 sec</td><td id="allowable-values"></td><td
id="description">Indicates how long to wait between performi
ng directory listings</td></tr><tr><td id="name"><strong>Batch
Size</strong></td><td id="default-value">100</td><td
id="allowable-values"></td><td id="description">The maximum number of files to
pull in each iteration, based on run schedule.</td></tr><tr><td id="name">IO
Buffer Size</td><td id="default-value"></td><td id="allowable-values"></td><td
id="description">Amount of memory to use to buffer file contents during IO.
This overrides the Hadoop Configuration</td></tr></table><h3>Relationships:
</h3><table
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>All
files retrieved from HDFS are transferred to this
relationship</td></tr><tr><td>passthrough</td><td>If this processor has an
input queue for some reason, then FlowFiles arriving on that input are
transferred to this relationship</td></tr></table><h3>Reads Attributes:
</h3>None specified.<h3>Writes Attributes: </h3><table
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><
td>filename</td><td>The name of the file that was read from
HDFS.</td></tr><tr><td>path</td><td>The path is set to the relative path of the
file's directory on HDFS. For example, if the Directory property is set to
/tmp, then files picked up from /tmp will have the path attribute set to "./".
If the Recurse Subdirectories property is set to true and a file is picked up
from /tmp/abc/1/2/3, then the path attribute will be set to
"abc/1/2/3".</td></tr></table><h3>See Also:</h3><p><a
href="../org.apache.nifi.processors.hadoop.PutHDFS/index.html">PutHDFS</a>, <a
href="../org.apache.nifi.processors.hadoop.ListHDFS/index.html">ListHDFS</a></p></body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta
charset="utf-8"></meta><title>GetHDFS</title><link rel="stylesheet"
href="../../css/component-usage.css"
type="text/css"></link></head><body><h2>Description: </h2><p>Fetch files from
Hadoop Distributed File System (HDFS) into FlowFiles. This Processor will
delete the file from HDFS after fetching it.</p><h3>Tags: </h3><p>hadoop, HDFS,
get, fetch, ingest, source, filesystem</p><h3>Properties: </h3><p>In the list
below, the names of required properties appear in <strong>bold</strong>. Any
other properties (not in bold) are considered optional. The table also
indicates any default values.</p><table
id="properties"><tr><th>Name</th><th>Default Value</th><th>Allowable
Values</th><th>Description</th></tr><tr><td id="name">Hadoop Configuration
Resources</td><td id="default-value"></td><td id="allowable-values"></td><td
id="description">A file or comma separated list of files which contains the
Hadoop file system configuration. Without this, Hadoop
will search the classpath for a 'core-site.xml' and 'hdfs-site.xml' file or
will revert to a default configuration.</td></tr><tr><td
id="name"><strong>Directory</strong></td><td id="default-value"></td><td
id="allowable-values"></td><td id="description">The HDFS directory from which
files should be read</td></tr><tr><td id="name"><strong>Recurse
Subdirectories</strong></td><td id="default-value">true</td><td
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td
id="description">Indicates whether to pull files from subdirectories of the
HDFS directory</td></tr><tr><td id="name"><strong>Keep Source
File</strong></td><td id="default-value">false</td><td
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td
id="description">Determines whether to delete the file from HDFS after it has
been successfully transferred. If true, the file will be fetched repeatedly.
This is intended for testing only.</td></tr><tr><td id="name">File Filter
Regex</td><td id="default-va
lue"></td><td id="allowable-values"></td><td id="description">A Java Regular
Expression for filtering Filenames; if a filter is supplied then only files
whose names match that Regular Expression will be fetched, otherwise all files
will be fetched</td></tr><tr><td id="name"><strong>Filter Match Name
Only</strong></td><td id="default-value">true</td><td
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td
id="description">If true then File Filter Regex will match on just the
filename, otherwise subdirectory names will be included with filename in the
regex comparison</td></tr><tr><td id="name"><strong>Ignore Dotted
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">If true, files whose names begin with a dot (".") will be
ignored</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 mi
nimum age that a file must be in order to be pulled; any file younger than
this amount of time (based on 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 (based on last modification date) will be
ignored</td></tr><tr><td id="name"><strong>Polling Interval</strong></td><td
id="default-value">0 sec</td><td id="allowable-values"></td><td
id="description">Indicates how long to wait between performing directory
listings</td></tr><tr><td id="name"><strong>Batch Size</strong></td><td
id="default-value">100</td><td id="allowable-values"></td><td
id="description">The maximum number of files to pull in each iteration, based
on run schedule.</td></tr><tr><td id="name">IO Buffer Size</td><td
id="default-value"></td><td id="allowable-values"></td><td
id="description">Amount of memo
ry to use to buffer file contents during IO. This overrides the Hadoop
Configuration</td></tr><tr><td id="name">Compression codec</td><td
id="default-value"></td><td
id="allowable-values"><ul><li>org.apache.hadoop.io.compress.BZip2Codec</li><li>org.apache.hadoop.io.compress.DefaultCodec</li><li>org.apache.hadoop.io.compress.GzipCodec</li><li>org.apache.hadoop.io.compress.Lz4Codec</li><li>org.apache.hadoop.io.compress.SnappyCodec</li></ul></td><td
id="description">No Description Provided.</td></tr></table><h3>Relationships:
</h3><table
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>passthrough</td><td>If
this processor has an input queue for some reason, then FlowFiles arriving on
that input are transferred to this
relationship</td></tr><tr><td>success</td><td>All files retrieved from HDFS are
transferred to this relationship</td></tr></table><h3>Reads Attributes:
</h3>None specified.<h3>Writes Attributes: </h3><table
id="writes-attributes"><tr><th>Name</th><th>
Description</th></tr><tr><td>filename</td><td>The name of the file that was
read from HDFS.</td></tr><tr><td>path</td><td>The path is set to the relative
path of the file's directory on HDFS. For example, if the Directory property is
set to /tmp, then files picked up from /tmp will have the path attribute set to
"./". If the Recurse Subdirectories property is set to true and a file is
picked up from /tmp/abc/1/2/3, then the path attribute will be set to
"abc/1/2/3".</td></tr></table><h3>See Also:</h3><p><a
href="../org.apache.nifi.processors.hadoop.PutHDFS/index.html">PutHDFS</a>, <a
href="../org.apache.nifi.processors.hadoop.ListHDFS/index.html">ListHDFS</a></p></body></html>
\ No newline at end of file
