svn commit: r1752359 [1/9] - in /nifi/site/trunk/docs/nifi-docs/components: org.apache.nifi.amqp.processors.ConsumeAMQP/ org.apache.nifi.amqp.processors.PublishAMQP/ org.apache.nifi.controller.MonitorMemory/ org.apache.nifi.dbcp.hive.HiveConnectionPool...

[jp...@apache.org]

Author: jpercivall
Date: Tue Jul 12 22:38:04 2016
New Revision: 1752359

URL: http://svn.apache.org/viewvc?rev=1752359&view=rev
Log:
Updating component documentation for 0.7.0

Added:
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.dbcp.hive.HiveConnectionPool/
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.dbcp.hive.HiveConnectionPool/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.aws.dynamodb.DeleteDynamoDB/
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.aws.dynamodb.DeleteDynamoDB/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.aws.dynamodb.GetDynamoDB/
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.aws.dynamodb.GetDynamoDB/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.aws.dynamodb.PutDynamoDB/
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.aws.dynamodb.PutDynamoDB/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.aws.s3.ListS3/
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.aws.s3.ListS3/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.hadoop.inotify.GetHDFSEvents/
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.hadoop.inotify.GetHDFSEvents/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.hive.PutHiveQL/
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.hive.PutHiveQL/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.hive.SelectHiveQL/
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.hive.SelectHiveQL/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.kafka.pubsub.ConsumeKafka/
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.kafka.pubsub.ConsumeKafka/additionalDetails.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.kafka.pubsub.ConsumeKafka/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.kafka.pubsub.PublishKafka/
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.kafka.pubsub.PublishKafka/additionalDetails.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.kafka.pubsub.PublishKafka/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.lumberjack.ListenLumberjack/
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.lumberjack.ListenLumberjack/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.media.ExtractMediaMetadata/
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.media.ExtractMediaMetadata/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.mqtt.ConsumeMQTT/
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.mqtt.ConsumeMQTT/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.mqtt.PublishMQTT/
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.mqtt.PublishMQTT/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.slack.PutSlack/
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.slack.PutSlack/additionalDetails.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.slack.PutSlack/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.DebugFlow/
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.DebugFlow/additionalDetails.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.DebugFlow/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.JoltTransformJSON/
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.JoltTransformJSON/additionalDetails.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.JoltTransformJSON/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.PutTCP/
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.PutTCP/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.PutUDP/
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.PutUDP/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.reporting.SiteToSiteProvenanceReportingTask/
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.reporting.SiteToSiteProvenanceReportingTask/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.snmp.processors.GetSNMP/
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.snmp.processors.GetSNMP/additionalDetails.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.snmp.processors.GetSNMP/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.snmp.processors.SetSNMP/
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.snmp.processors.SetSNMP/additionalDetails.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.snmp.processors.SetSNMP/index.html
Modified:
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.amqp.processors.ConsumeAMQP/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.amqp.processors.PublishAMQP/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.hbase.PutHBaseJSON/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.avro.ConvertAvroToJSON/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.aws.credentials.provider.service.AWSCredentialsProviderControllerService/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.aws.kinesis.firehose.PutKinesisFirehose/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.aws.lambda.PutLambda/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.aws.s3.DeleteS3Object/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.aws.s3.FetchS3Object/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.aws.s3.PutS3Object/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.aws.sns.PutSNS/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.aws.sqs.DeleteSQS/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.aws.sqs.GetSQS/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.aws.sqs.PutSQS/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.cassandra.PutCassandraQL/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.cassandra.QueryCassandra/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.elasticsearch.PutElasticsearch/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.PutHDFS/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.ConvertAvroSchema/index.html
    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/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.script.ExecuteScript/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.script.InvokeScriptedProcessor/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.splunk.GetSplunk/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.splunk.PutSplunk/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ConvertJSONToSQL/index.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.ExecuteSQL/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.FetchFile/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.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.HashContent/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.PutFile/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.PutSQL/index.html
    nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.QueryDatabaseTable/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.SegmentContent/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.UnpackContent/index.html

Modified: nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.amqp.processors.ConsumeAMQP/index.html
URL: http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.amqp.processors.ConsumeAMQP/index.html?rev=1752359&r1=1752358&r2=1752359&view=diff
==============================================================================
--- nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.amqp.processors.ConsumeAMQP/index.html (original)
+++ nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.amqp.processors.ConsumeAMQP/index.html Tue Jul 12 22:38:04 2016
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta charset="utf-8"></meta><title>ConsumeAMQP</title><link rel="stylesheet" href="../../css/component-usage.css" type="text/css"></link></head><body><h2>Description: </h2><p>Consumes AMQP Message transforming its content to a FlowFile and transitioning it to 'success' relationship</p><p><a href="additionalDetails.html">Additional Details...</a></p><h3>Tags: </h3><p>amqp, rabbit, 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, 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>Queue</strong></td><td id="default-value"></td><td id="allowable-values"></td><td id="description">The name of the existing AMQP Queue from which messages will be consumed. Usually pre-defined by AMQP administrator. </td></tr><tr><td id="name"><strong>Host Name</strong></td><td id="default-value">localhost</td><td id="allowable-values"></td><td id="description">Network address of AMQP broker (e.g., localhost)</td></tr><tr><td id="name"><strong>Port</strong></td><td id="default-value">5672</td><td id="allowable-values"></td><td id="description">Numeric value identifying Port of AMQP broker (e.g., 5671)</td></tr><tr><td id="name">Virtual Host</td><td id="default-value"></td><td id="allowable-values"></td><td id="description">Virtual Host name which segregates AMQP system for enhanced security.</td></tr><tr><td id="name"><strong>User Name</strong></td><td id="default-value">guest</td><td id="allowable-valu
 es"></td><td id="description">User Name used for authentication and authorization.</td></tr><tr><td id="name"><strong>Password</strong></td><td id="default-value">guest</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"><strong>AMQP Version</strong></td><td id="default-value">0.9.1</td><td id="allowable-values"><ul><li>0.9.1</li></ul></td><td id="description">AMQP Version. Currently only supports AMQP v0.9.1.</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 AMQP queue are routed to this relationship</td></tr></table><h3>Reads Attributes: </h3>None specified.<h3>Writes Attributes: </h3>None specified.</body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta charset="utf-8"></meta><title>ConsumeAMQP</title><link rel="stylesheet" href="../../css/component-usage.css" type="text/css"></link></head><body><h2>Description: </h2><p>Consumes AMQP Message transforming its content to a FlowFile and transitioning it to 'success' relationship</p><p><a href="additionalDetails.html">Additional Details...</a></p><h3>Tags: </h3><p>amqp, rabbit, 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, 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>Queue</strong></td><td id="default-value"></td><td id="allowable-values"></td><td id="description">The name of the existing AMQP Queue from which messages will be consumed. Usually pre-defined by AMQP administrator. </td></tr><tr><td id="name"><strong>Host Name</strong></td><td id="default-value">localhost</td><td id="allowable-values"></td><td id="description">Network address of AMQP broker (e.g., localhost)</td></tr><tr><td id="name"><strong>Port</strong></td><td id="default-value">5672</td><td id="allowable-values"></td><td id="description">Numeric value identifying Port of AMQP broker (e.g., 5671)</td></tr><tr><td id="name">Virtual Host</td><td id="default-value"></td><td id="allowable-values"></td><td id="description">Virtual Host name which segregates AMQP system for enhanced security.</td></tr><tr><td id="name"><strong>User Name</strong></td><td id="default-value">guest</td><td id="allowable-valu
 es"></td><td id="description">User Name used for authentication and authorization.</td></tr><tr><td id="name"><strong>Password</strong></td><td id="default-value">guest</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"><strong>AMQP Version</strong></td><td id="default-value">0.9.1</td><td id="allowable-values"><ul><li>0.9.1</li></ul></td><td id="description">AMQP Version. Currently only supports AMQP v0.9.1.</td></tr><tr><td id="name">SSL Context Service</td><td id="default-value"></td><td id="allowable-values"><strong>Controller Service API: </strong><br/>SSLContextService<br/><strong>Implementation:</strong><br/><a href="../org.apache.nifi.ssl.StandardSSLContextService/index.html">StandardSSLContextService</a></td><td id="description">The SSL Context Service used to provide client certificate information for TLS/SSL connections.</td></tr><tr><td id="na
 me">Client Auth</td><td id="default-value">REQUIRED</td><td id="allowable-values"><ul><li>WANT</li><li>REQUIRED</li><li>NONE</li></ul></td><td id="description">Client authentication policy when connecting to secure (TLS/SSL) AMQP broker. Possible values are REQUIRED, WANT, NONE. This property is only used when an SSL Context has been defined and enabled.</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 AMQP queue are routed to this relationship</td></tr></table><h3>Reads Attributes: </h3>None specified.<h3>Writes Attributes: </h3>None specified.</body></html>
\ No newline at end of file

Modified: nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.amqp.processors.PublishAMQP/index.html
URL: http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.amqp.processors.PublishAMQP/index.html?rev=1752359&r1=1752358&r2=1752359&view=diff
==============================================================================
--- nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.amqp.processors.PublishAMQP/index.html (original)
+++ nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.amqp.processors.PublishAMQP/index.html Tue Jul 12 22:38:04 2016
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta charset="utf-8"></meta><title>PublishAMQP</title><link rel="stylesheet" href="../../css/component-usage.css" type="text/css"></link></head><body><h2>Description: </h2><p>Creates a AMQP Message from the contents of a FlowFile and sends the message to an AMQP Exchange.In a typical AMQP exchange model, the message that is sent to the AMQP Exchange will be routed based on the 'Routing Key' to its final destination in the queue (the binding). If due to some misconfiguration the binding between the Exchange, Routing Key and Queue is not set up, the message will have no final destination and will return (i.e., the data will not make it to the queue). If that happens you will see a log in both app-log and bulletin stating to that effect. Fixing the binding (normally done by AMQP administrator) will resolve the issue.</p><p><a href="additionalDetails.html">Additional Details...</a></p><h3>Tags: </h3><p>amqp, rabbit, put, message, send, publish</p><h
 3>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>Exchange Name</strong></td><td id="default-value"></td><td id="allowable-values"></td><td id="description">The name of the AMQP Exchange the messages will be sent to. Usually provided by the AMQP administrator (e.g., 'amq.direct'). It is an optional property. If kept empty the messages will be sent to a default AMQP exchange.</td></tr><tr><td id="name"><strong>Routing Key</
 strong></td><td id="default-value"></td><td id="allowable-values"></td><td id="description">The name of the Routing Key that will be used by AMQP to route messages from the exchange to a destination queue(s). Usually provided by the administrator (e.g., 'myKey')In the event when messages are sent to a default exchange this property corresponds to a destination queue name, otherwise a binding from the Exchange to a Queue via Routing Key must be set (usually by the AMQP administrator)</td></tr><tr><td id="name"><strong>Host Name</strong></td><td id="default-value">localhost</td><td id="allowable-values"></td><td id="description">Network address of AMQP broker (e.g., localhost)</td></tr><tr><td id="name"><strong>Port</strong></td><td id="default-value">5672</td><td id="allowable-values"></td><td id="description">Numeric value identifying Port of AMQP broker (e.g., 5671)</td></tr><tr><td id="name">Virtual Host</td><td id="default-value"></td><td id="allowable-values"></td><td id="descri
 ption">Virtual Host name which segregates AMQP system for enhanced security.</td></tr><tr><td id="name"><strong>User Name</strong></td><td id="default-value">guest</td><td id="allowable-values"></td><td id="description">User Name used for authentication and authorization.</td></tr><tr><td id="name"><strong>Password</strong></td><td id="default-value">guest</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"><strong>AMQP Version</strong></td><td id="default-value">0.9.1</td><td id="allowable-values"><ul><li>0.9.1</li></ul></td><td id="description">AMQP Version. Currently only supports AMQP v0.9.1.</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 AMQP destination are routed to this relationship</td></tr><tr><td>failure</td><td>All FlowFiles 
 that cannot be routed to the AMQP destination are routed to this relationship</td></tr></table><h3>Reads Attributes: </h3>None specified.<h3>Writes Attributes: </h3>None specified.</body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta charset="utf-8"></meta><title>PublishAMQP</title><link rel="stylesheet" href="../../css/component-usage.css" type="text/css"></link></head><body><h2>Description: </h2><p>Creates a AMQP Message from the contents of a FlowFile and sends the message to an AMQP Exchange.In a typical AMQP exchange model, the message that is sent to the AMQP Exchange will be routed based on the 'Routing Key' to its final destination in the queue (the binding). If due to some misconfiguration the binding between the Exchange, Routing Key and Queue is not set up, the message will have no final destination and will return (i.e., the data will not make it to the queue). If that happens you will see a log in both app-log and bulletin stating to that effect. Fixing the binding (normally done by AMQP administrator) will resolve the issue.</p><p><a href="additionalDetails.html">Additional Details...</a></p><h3>Tags: </h3><p>amqp, rabbit, put, message, send, publish</p><h
 3>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>Exchange Name</strong></td><td id="default-value"></td><td id="allowable-values"></td><td id="description">The name of the AMQP Exchange the messages will be sent to. Usually provided by the AMQP administrator (e.g., 'amq.direct'). It is an optional property. If kept empty the messages will be sent to a default AMQP exchange.</td></tr><tr><td id="name"><strong>Routing Key</
 strong></td><td id="default-value"></td><td id="allowable-values"></td><td id="description">The name of the Routing Key that will be used by AMQP to route messages from the exchange to a destination queue(s). Usually provided by the administrator (e.g., 'myKey')In the event when messages are sent to a default exchange this property corresponds to a destination queue name, otherwise a binding from the Exchange to a Queue via Routing Key must be set (usually by the AMQP administrator)</td></tr><tr><td id="name"><strong>Host Name</strong></td><td id="default-value">localhost</td><td id="allowable-values"></td><td id="description">Network address of AMQP broker (e.g., localhost)</td></tr><tr><td id="name"><strong>Port</strong></td><td id="default-value">5672</td><td id="allowable-values"></td><td id="description">Numeric value identifying Port of AMQP broker (e.g., 5671)</td></tr><tr><td id="name">Virtual Host</td><td id="default-value"></td><td id="allowable-values"></td><td id="descri
 ption">Virtual Host name which segregates AMQP system for enhanced security.</td></tr><tr><td id="name"><strong>User Name</strong></td><td id="default-value">guest</td><td id="allowable-values"></td><td id="description">User Name used for authentication and authorization.</td></tr><tr><td id="name"><strong>Password</strong></td><td id="default-value">guest</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"><strong>AMQP Version</strong></td><td id="default-value">0.9.1</td><td id="allowable-values"><ul><li>0.9.1</li></ul></td><td id="description">AMQP Version. Currently only supports AMQP v0.9.1.</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.StandardSSLContextServ
 ice/index.html">StandardSSLContextService</a></td><td id="description">The SSL Context Service used to provide client certificate information for TLS/SSL connections.</td></tr><tr><td id="name">Client Auth</td><td id="default-value">REQUIRED</td><td id="allowable-values"><ul><li>WANT</li><li>REQUIRED</li><li>NONE</li></ul></td><td id="description">Client authentication policy when connecting to secure (TLS/SSL) AMQP broker. Possible values are REQUIRED, WANT, NONE. This property is only used when an SSL Context has been defined and enabled.</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 AMQP destination are routed to this relationship</td></tr><tr><td>failure</td><td>All FlowFiles that cannot be routed to the AMQP destination are routed to this relationship</td></tr></table><h3>Reads Attributes: </h3>None specified.<h3>Writes Attributes: </h3>None specified.</body
 ></html>
\ No newline at end of file

Modified: nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.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=1752359&r1=1752358&r2=1752359&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 Tue Jul 12 22:38:04 2016
@@ -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.</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
+<!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"><ul><li
 >Code Cache</li><li>Metaspace</li><li>Compressed Class Space</li><li>PS Eden Space</li><li>PS Survivor Space</li><li>PS Old Gen</li></ul></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

Added: nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.dbcp.hive.HiveConnectionPool/index.html
URL: http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.dbcp.hive.HiveConnectionPool/index.html?rev=1752359&view=auto
==============================================================================
--- nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.dbcp.hive.HiveConnectionPool/index.html (added)
+++ nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.dbcp.hive.HiveConnectionPool/index.html Tue Jul 12 22:38:04 2016
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta charset="utf-8"></meta><title>HiveConnectionPool</title><link rel="stylesheet" href="../../css/component-usage.css" type="text/css"></link></head><body><h2>Description: </h2><p>Provides Database Connection Pooling Service for Apache Hive. Connections can be asked from pool and returned after usage.</p><h3>Tags: </h3><p>hive, 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 the Hive documentation. For example, the server principal is often included as a connection parameter when connecting to a secure Hive server.</td></tr><tr><td id="name">Hive 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 Hive configuration (hive-site.xml, e.g.). Without this, Hadoop will search the classpath for a 'hive-site.xml' file or will revert to a default configuration. Note that to enable authentication with Kerberos e.g., the appropriate properties must be set in the configuration files. Please se
 e the Hive documentation for more details.</td></tr><tr><td id="name">Kerberos Principal</td><td id="default-value"></td><td id="allowable-values"></td><td id="description">Kerberos principal to authenticate as. Requires nifi.kerberos.krb5.file to be set in your nifi.properties</td></tr><tr><td id="name">Kerberos Keytab</td><td id="default-value"></td><td id="allowable-values"></td><td id="description">Kerberos keytab associated with the principal. Requires nifi.kerberos.krb5.file to be set in your nifi.properties</td></tr><tr><td id="name">Database User</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.hbase.PutHBaseJSON/index.html
URL: http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.hbase.PutHBaseJSON/index.html?rev=1752359&r1=1752358&r2=1752359&view=diff
==============================================================================
--- nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.hbase.PutHBaseJSON/index.html (original)
+++ nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.hbase.PutHBaseJSON/index.html Tue Jul 12 22:38:04 2016
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta charset="utf-8"></meta><title>PutHBaseJSON</title><link rel="stylesheet" href="../../css/component-usage.css" type="text/css"></link></head><body><h2>Description: </h2><p>Adds rows to HBase based on the contents of incoming JSON documents. Each FlowFile must contain a single UTF-8 encoded JSON document, and any FlowFiles where the root element is not a single document will be routed to failure. Each JSON field name and value will become a column qualifier and value of the HBase row. Any fields with a null value will be skipped, and fields with a complex value will be handled according to the Complex Field Strategy. The row id can be specified either directly on the processor through the Row Identifier property, or can be extracted from the JSON document by specifying the Row Identifier Field Name property. This processor will hold the contents of all FlowFiles for the given batch in memory at one time.</p><h3>Tags: </h3><p>hadoop, hbase, pu
 t, json</p><h3>Properties: </h3><p>In the list below, the names of required properties appear in <strong>bold</strong>. Any other properties (not in bold) are considered optional. The table also indicates any default values, and whether a property supports the <a href="../../html/expression-language-guide.html">NiFi Expression Language</a>.</p><table id="properties"><tr><th>Name</th><th>Default Value</th><th>Allowable Values</th><th>Description</th></tr><tr><td id="name"><strong>HBase Client Service</strong></td><td id="default-value"></td><td id="allowable-values"><strong>Controller Service API: </strong><br/>HBaseClientService<br/><strong>Implementation:</strong><br/><a href="../org.apache.nifi.hbase.HBase_1_1_2_ClientService/index.html">HBase_1_1_2_ClientService</a></td><td id="description">Specifies the Controller Service to use for accessing HBase.</td></tr><tr><td id="name"><strong>Table Name</strong></td><td id="default-value"></td><td id="allowable-values"></td><td id="descr
 iption">The name of the HBase Table to put data into<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td id="name">Row Identifier</td><td id="default-value"></td><td id="allowable-values"></td><td id="description">Specifies the Row ID to use when inserting data into HBase<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td id="name">Row Identifier Field Name</td><td id="default-value"></td><td id="allowable-values"></td><td id="description">Specifies the name of a JSON element whose value should be used as the row id for the given JSON document.<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td id="name"><strong>Column Family</strong></td><td id="default-value"></td><td id="allowable-values"></td><td id="description">The Column Family to use when inserting data into HBase<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td id="name"><strong>Batch Size</strong></td><td id="default-value">25</td><td 
 id="allowable-values"></td><td id="description">The maximum number of FlowFiles to process in a single execution. The FlowFiles will be grouped by table, and a single Put per table will be performed.</td></tr><tr><td id="name"><strong>Complex Field Strategy</strong></td><td id="default-value">Text</td><td id="allowable-values"><ul><li>Fail <img src="../../html/images/iconInfo.png" alt="Route entire FlowFile to failure if any elements contain complex values." title="Route entire FlowFile to failure if any elements contain complex values."></img></li><li>Warn <img src="../../html/images/iconInfo.png" alt="Provide a warning and do not include field in row sent to HBase." title="Provide a warning and do not include field in row sent to HBase."></img></li><li>Ignore <img src="../../html/images/iconInfo.png" alt="Silently ignore and do not include in row sent to HBase." title="Silently ignore and do not include in row sent to HBase."></img></li><li>Text <img src="../../html/images/iconInf
 o.png" alt="Use the string representation of the complex field as the value of the given column." title="Use the string representation of the complex field as the value of the given column."></img></li></ul></td><td id="description">Indicates how to handle complex fields, i.e. fields that do not have a single text value.</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 after it has been successfully stored in HBase</td></tr><tr><td>failure</td><td>A FlowFile is routed to this relationship if it cannot be sent to HBase</td></tr></table><h3>Reads Attributes: </h3>None specified.<h3>Writes Attributes: </h3>None specified.</body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta charset="utf-8"></meta><title>PutHBaseJSON</title><link rel="stylesheet" href="../../css/component-usage.css" type="text/css"></link></head><body><h2>Description: </h2><p>Adds rows to HBase based on the contents of incoming JSON documents. Each FlowFile must contain a single UTF-8 encoded JSON document, and any FlowFiles where the root element is not a single document will be routed to failure. Each JSON field name and value will become a column qualifier and value of the HBase row. Any fields with a null value will be skipped, and fields with a complex value will be handled according to the Complex Field Strategy. The row id can be specified either directly on the processor through the Row Identifier property, or can be extracted from the JSON document by specifying the Row Identifier Field Name property. This processor will hold the contents of all FlowFiles for the given batch in memory at one time.</p><h3>Tags: </h3><p>hadoop, hbase, pu
 t, json</p><h3>Properties: </h3><p>In the list below, the names of required properties appear in <strong>bold</strong>. Any other properties (not in bold) are considered optional. The table also indicates any default values, and whether a property supports the <a href="../../html/expression-language-guide.html">NiFi Expression Language</a>.</p><table id="properties"><tr><th>Name</th><th>Default Value</th><th>Allowable Values</th><th>Description</th></tr><tr><td id="name"><strong>HBase Client Service</strong></td><td id="default-value"></td><td id="allowable-values"><strong>Controller Service API: </strong><br/>HBaseClientService<br/><strong>Implementation:</strong><br/><a href="../org.apache.nifi.hbase.HBase_1_1_2_ClientService/index.html">HBase_1_1_2_ClientService</a></td><td id="description">Specifies the Controller Service to use for accessing HBase.</td></tr><tr><td id="name"><strong>Table Name</strong></td><td id="default-value"></td><td id="allowable-values"></td><td id="descr
 iption">The name of the HBase Table to put data into<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td id="name">Row Identifier</td><td id="default-value"></td><td id="allowable-values"></td><td id="description">Specifies the Row ID to use when inserting data into HBase<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td id="name">Row Identifier Field Name</td><td id="default-value"></td><td id="allowable-values"></td><td id="description">Specifies the name of a JSON element whose value should be used as the row id for the given JSON document.<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td id="name"><strong>Column Family</strong></td><td id="default-value"></td><td id="allowable-values"></td><td id="description">The Column Family to use when inserting data into HBase<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td id="name"><strong>Batch Size</strong></td><td id="default-value">25</td><td 
 id="allowable-values"></td><td id="description">The maximum number of FlowFiles to process in a single execution. The FlowFiles will be grouped by table, and a single Put per table will be performed.</td></tr><tr><td id="name"><strong>Complex Field Strategy</strong></td><td id="default-value">Text</td><td id="allowable-values"><ul><li>Fail <img src="../../html/images/iconInfo.png" alt="Route entire FlowFile to failure if any elements contain complex values." title="Route entire FlowFile to failure if any elements contain complex values."></img></li><li>Warn <img src="../../html/images/iconInfo.png" alt="Provide a warning and do not include field in row sent to HBase." title="Provide a warning and do not include field in row sent to HBase."></img></li><li>Ignore <img src="../../html/images/iconInfo.png" alt="Silently ignore and do not include in row sent to HBase." title="Silently ignore and do not include in row sent to HBase."></img></li><li>Text <img src="../../html/images/iconInf
 o.png" alt="Use the string representation of the complex field as the value of the given column." title="Use the string representation of the complex field as the value of the given column."></img></li></ul></td><td id="description">Indicates how to handle complex fields, i.e. fields that do not have a single text value.</td></tr><tr><td id="name"><strong>Field Encoding Strategy</strong></td><td id="default-value">String</td><td id="allowable-values"><ul><li>String <img src="../../html/images/iconInfo.png" alt="Stores the value of each field as a UTF-8 String." title="Stores the value of each field as a UTF-8 String."></img></li><li>Bytes <img src="../../html/images/iconInfo.png" alt="Stores the value of each field as the byte representation of the type derived from the JSON." title="Stores the value of each field as the byte representation of the type derived from the JSON."></img></li></ul></td><td id="description">Indicates how to store the value of each field in HBase. The defau
 lt behavior is to convert each value from the JSON to a String, and store the UTF-8 bytes. Choosing Bytes will interpret the type of each field from the JSON, and convert the value to the byte representation of that type, meaning an integer will be stored as the byte representation of that integer.</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 after it has been successfully stored in HBase</td></tr><tr><td>failure</td><td>A FlowFile is routed to this relationship if it cannot be sent to HBase</td></tr></table><h3>Reads Attributes: </h3>None specified.<h3>Writes Attributes: </h3>None specified.</body></html>
\ No newline at end of file

Modified: nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.avro.ConvertAvroToJSON/index.html
URL: http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.avro.ConvertAvroToJSON/index.html?rev=1752359&r1=1752358&r2=1752359&view=diff
==============================================================================
--- nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.avro.ConvertAvroToJSON/index.html (original)
+++ nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.avro.ConvertAvroToJSON/index.html Tue Jul 12 22:38:04 2016
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta charset="utf-8"></meta><title>ConvertAvroToJSON</title><link rel="stylesheet" href="../../css/component-usage.css" type="text/css"></link></head><body><h2>Description: </h2><p>Converts a Binary Avro record into a JSON object. This processor provides a direct mapping of an Avro field to a JSON field, such that the resulting JSON will have the same hierarchical structure as the Avro document. Note that the Avro schema information will be lost, as this is not a translation from binary Avro to JSON formatted Avro. The output JSON is encoded the UTF-8 encoding. If an incoming FlowFile contains a stream of multiple Avro records, the resultant FlowFile will contain a JSON Array containing all of the Avro records or a sequence of JSON Objects.  If an incoming FlowFile does not contain any records, an empty JSON object is the output. Empty/Single Avro record FlowFile inputs are optionally wrapped in a container as dictated by 'Wrap Single Record'</p
 ><h3>Tags: </h3><p>avro, convert, json</p><h3>Properties: </h3><p>In the list below, the names of required properties appear in <strong>bold</strong>. Any other properties (not in bold) are considered optional. The table also indicates any default values.</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>JSON container options</strong></td><td id="default-value">array</td><td id="allowable-values"><ul><li>none</li><li>array</li></ul></td><td id="description">Determines how stream of records is exposed: either as a sequence of single Objects (none) (i.e. writing every Object to a new line), or as an array of Objects (array).</td></tr><tr><td id="name"><strong>Wrap Single Record</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 if the resulting output for empty records or a single record should be wrap
 ped in a container array as specified by 'JSON container options'</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 after it has been converted to JSON</td></tr><tr><td>failure</td><td>A FlowFile is routed to this relationship if it cannot be parsed as Avro or cannot be converted to JSON for any reason</td></tr></table><h3>Reads Attributes: </h3>None specified.<h3>Writes Attributes: </h3><table id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>mime.type</td><td>Sets the mime type to application/json</td></tr></table></body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta charset="utf-8"></meta><title>ConvertAvroToJSON</title><link rel="stylesheet" href="../../css/component-usage.css" type="text/css"></link></head><body><h2>Description: </h2><p>Converts a Binary Avro record into a JSON object. This processor provides a direct mapping of an Avro field to a JSON field, such that the resulting JSON will have the same hierarchical structure as the Avro document. Note that the Avro schema information will be lost, as this is not a translation from binary Avro to JSON formatted Avro. The output JSON is encoded the UTF-8 encoding. If an incoming FlowFile contains a stream of multiple Avro records, the resultant FlowFile will contain a JSON Array containing all of the Avro records or a sequence of JSON Objects.  If an incoming FlowFile does not contain any records, an empty JSON object is the output. Empty/Single Avro record FlowFile inputs are optionally wrapped in a container as dictated by 'Wrap Single Record'</p
 ><h3>Tags: </h3><p>avro, convert, json</p><h3>Properties: </h3><p>In the list below, the names of required properties appear in <strong>bold</strong>. Any other properties (not in bold) are considered optional. The table also indicates any default values.</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>JSON container options</strong></td><td id="default-value">array</td><td id="allowable-values"><ul><li>none</li><li>array</li></ul></td><td id="description">Determines how stream of records is exposed: either as a sequence of single Objects (none) (i.e. writing every Object to a new line), or as an array of Objects (array).</td></tr><tr><td id="name"><strong>Wrap Single Record</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 if the resulting output for empty records or a single record should be wrap
 ped in a container array as specified by 'JSON container options'</td></tr><tr><td id="name">Avro schema</td><td id="default-value"></td><td id="allowable-values"></td><td id="description">If the Avro records do not contain the schema (datum only), it must be specified here.</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 after it has been converted to JSON</td></tr><tr><td>failure</td><td>A FlowFile is routed to this relationship if it cannot be parsed as Avro or cannot be converted to JSON for any reason</td></tr></table><h3>Reads Attributes: </h3>None specified.<h3>Writes Attributes: </h3><table id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>mime.type</td><td>Sets the mime type to application/json</td></tr></table></body></html>
\ No newline at end of file

Modified: nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.aws.credentials.provider.service.AWSCredentialsProviderControllerService/index.html
URL: http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.aws.credentials.provider.service.AWSCredentialsProviderControllerService/index.html?rev=1752359&r1=1752358&r2=1752359&view=diff
==============================================================================
--- nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.aws.credentials.provider.service.AWSCredentialsProviderControllerService/index.html (original)
+++ nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.aws.credentials.provider.service.AWSCredentialsProviderControllerService/index.html Tue Jul 12 22:38:04 2016
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta charset="utf-8"></meta><title>AWSCredentialsProviderControllerService</title><link rel="stylesheet" href="../../css/component-usage.css" type="text/css"></link></head><body><h2>Description: </h2><p>Defines credentials for Amazon Web Services processors.</p><h3>Tags: </h3><p>aws, credentials, provider</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>Defaul
 t Value</th><th>Allowable Values</th><th>Description</th></tr><tr><td id="name">Access Key</td><td id="default-value"></td><td id="allowable-values"></td><td id="description">No Description Provided.<br/><strong>Sensitive Property: true</strong><br/><strong>Supports Expression Language: true</strong></td></tr><tr><td id="name">Secret Key</td><td id="default-value"></td><td id="allowable-values"></td><td id="description">No Description Provided.<br/><strong>Sensitive Property: true</strong><br/><strong>Supports Expression Language: true</strong></td></tr><tr><td id="name">Credentials File</td><td id="default-value"></td><td id="allowable-values"></td><td id="description">No Description Provided.</td></tr><tr><td id="name">Assume Role ARN</td><td id="default-value"></td><td id="allowable-values"></td><td id="description">The AWS Role ARN for cross account access. This is used in conjunction with role name and session timeout</td></tr><tr><td id="name">Assume Role Session Name</td><td 
 id="default-value"></td><td id="allowable-values"></td><td id="description">The aws role name for cross account access. This is used in conjunction with role arn and session time out</td></tr><tr><td id="name">Session Time</td><td id="default-value">3600</td><td id="allowable-values"></td><td id="description">Session time for role based session (between 900 and 3600 seconds). This is used in conjunction with role arn and name</td></tr></table></body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta charset="utf-8"></meta><title>AWSCredentialsProviderControllerService</title><link rel="stylesheet" href="../../css/component-usage.css" type="text/css"></link></head><body><h2>Description: </h2><p>Defines credentials for Amazon Web Services processors. Uses default credentials without configuration. Default credentials support EC2 instance profile/role, default user profile, environment variables, etc. Additional options include access key / secret key pairs, credentials file, named profile, and assume role credentials.</p><h3>Tags: </h3><p>aws, credentials, provider</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">Use Default Credentials</td><td id="default-value">false</td><td id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td id="description">If true, uses the Default Credential chain, including EC2 instance profiles or roles, environment variables, default user credentials, etc.</td></tr><tr><td id="name">Access Key</td><td id="default-value"></td><td id="allowable-values"></td><td id="description">No Description Provided.<br/><strong>Sensitive Property: true</strong><br/><strong>Supports Expression Language: true</strong></td></tr><tr><td id="name">Secret Key</td><td id="default-value"></td><td id="allowable-values"></td><td i
 d="description">No Description Provided.<br/><strong>Sensitive Property: true</strong><br/><strong>Supports Expression Language: true</strong></td></tr><tr><td id="name">Credentials File</td><td id="default-value"></td><td id="allowable-values"></td><td id="description">Path to a file containing AWS access key and secret key in properties file format.</td></tr><tr><td id="name">Profile Name</td><td id="default-value"></td><td id="allowable-values"></td><td id="description">The AWS profile name for credentials from the profile configuration file.<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td id="name">Use Anonymous Credentials</td><td id="default-value">false</td><td id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td id="description">If true, uses Anonymous credentials</td></tr><tr><td id="name">Assume Role ARN</td><td id="default-value"></td><td id="allowable-values"></td><td id="description">The AWS Role ARN for cross account access. This 
 is used in conjunction with role name and session timeout</td></tr><tr><td id="name">Assume Role Session Name</td><td id="default-value"></td><td id="allowable-values"></td><td id="description">The AWS Role Name for cross account access. This is used in conjunction with role ARN and session time out</td></tr><tr><td id="name">Session Time</td><td id="default-value">3600</td><td id="allowable-values"></td><td id="description">Session time for role based session (between 900 and 3600 seconds). This is used in conjunction with role ARN and name</td></tr><tr><td id="name">Assume Role External ID</td><td id="default-value"></td><td id="allowable-values"></td><td id="description">External ID for cross-account access. This is used in conjunction with role arn, role name, and optional session time out</td></tr></table></body></html>
\ No newline at end of file

Added: nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.aws.dynamodb.DeleteDynamoDB/index.html
URL: http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.aws.dynamodb.DeleteDynamoDB/index.html?rev=1752359&view=auto
==============================================================================
--- nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.aws.dynamodb.DeleteDynamoDB/index.html (added)
+++ nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.aws.dynamodb.DeleteDynamoDB/index.html Tue Jul 12 22:38:04 2016
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta charset="utf-8"></meta><title>DeleteDynamoDB</title><link rel="stylesheet" href="../../css/component-usage.css" type="text/css"></link></head><body><h2>Description: </h2><p>Deletes a document from DynamoDB based on hash and range key. The key can be string or number. The request requires all the primary keys for the operation (hash or hash and range key)</p><h3>Tags: </h3><p>Amazon, DynamoDB, AWS, Delete, Remove</p><h3>Properties: </h3><p>In the list below, the names of required properties appear in <strong>bold</strong>. Any other properties (not in bold) are considered optional. The table also indicates any default values, whether a property supports the <a href="../../html/expression-language-guide.html">NiFi Expression Language</a>, and whether a property is considered "sensitive", meaning that its value will be encrypted. Before entering a value in a sensitive property, ensure that the <strong>nifi.properties</strong> file has an entry
  for the property <strong>nifi.sensitive.props.key</strong>.</p><table id="properties"><tr><th>Name</th><th>Default Value</th><th>Allowable Values</th><th>Description</th></tr><tr><td id="name"><strong>Table Name</strong></td><td id="default-value"></td><td id="allowable-values"></td><td id="description">The DynamoDB table name</td></tr><tr><td id="name"><strong>Hash Key Name</strong></td><td id="default-value"></td><td id="allowable-values"></td><td id="description">The hash key name of the item</td></tr><tr><td id="name">Range Key Name</td><td id="default-value"></td><td id="allowable-values"></td><td id="description">The range key name of the item</td></tr><tr><td id="name"><strong>Hash Key Value</strong></td><td id="default-value">${dynamodb.item.hash.key.value}</td><td id="allowable-values"></td><td id="description">The hash key value of the item<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td id="name">Range Key Value</td><td id="default-value">${dynam
 odb.item.range.key.value}</td><td id="allowable-values"></td><td id="description">No Description Provided.<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td id="name"><strong>Hash Key Value Type</strong></td><td id="default-value">string</td><td id="allowable-values"><ul><li>string</li><li>number</li></ul></td><td id="description">The hash key value type of the item</td></tr><tr><td id="name"><strong>Range Key Value Type</strong></td><td id="default-value">string</td><td id="allowable-values"><ul><li>string</li><li>number</li></ul></td><td id="description">The range key value type of the item</td></tr><tr><td id="name">Batch items for each request (between 1 and 50)</td><td id="default-value">1</td><td id="allowable-values"></td><td id="description">The items to be retrieved in one batch</td></tr><tr><td id="name"><strong>Region</strong></td><td id="default-value">us-west-2</td><td id="allowable-values"><ul><li>us-gov-west-1 <img src="../../html/images/iconInf
 o.png" alt="us-gov-west-1" title="us-gov-west-1"></img></li><li>us-east-1 <img src="../../html/images/iconInfo.png" alt="us-east-1" title="us-east-1"></img></li><li>us-west-1 <img src="../../html/images/iconInfo.png" alt="us-west-1" title="us-west-1"></img></li><li>us-west-2 <img src="../../html/images/iconInfo.png" alt="us-west-2" title="us-west-2"></img></li><li>eu-west-1 <img src="../../html/images/iconInfo.png" alt="eu-west-1" title="eu-west-1"></img></li><li>eu-central-1 <img src="../../html/images/iconInfo.png" alt="eu-central-1" title="eu-central-1"></img></li><li>ap-southeast-1 <img src="../../html/images/iconInfo.png" alt="ap-southeast-1" title="ap-southeast-1"></img></li><li>ap-southeast-2 <img src="../../html/images/iconInfo.png" alt="ap-southeast-2" title="ap-southeast-2"></img></li><li>ap-northeast-1 <img src="../../html/images/iconInfo.png" alt="ap-northeast-1" title="ap-northeast-1"></img></li><li>sa-east-1 <img src="../../html/images/iconInfo.png" alt="sa-east-1" tit
 le="sa-east-1"></img></li><li>cn-north-1 <img src="../../html/images/iconInfo.png" alt="cn-north-1" title="cn-north-1"></img></li></ul></td><td id="description">No Description Provided.</td></tr><tr><td id="name">Access Key</td><td id="default-value"></td><td id="allowable-values"></td><td id="description">No Description Provided.<br/><strong>Sensitive Property: true</strong><br/><strong>Supports Expression Language: true</strong></td></tr><tr><td id="name">Secret Key</td><td id="default-value"></td><td id="allowable-values"></td><td id="description">No Description Provided.<br/><strong>Sensitive Property: true</strong><br/><strong>Supports Expression Language: true</strong></td></tr><tr><td id="name">Credentials File</td><td id="default-value"></td><td id="allowable-values"></td><td id="description">Path to a file containing AWS access key and secret key in properties file format.</td></tr><tr><td id="name">AWS Credentials Provider service</td><td id="default-value"></td><td id="al
 lowable-values"><strong>Controller Service API: </strong><br/>AWSCredentialsProviderService<br/><strong>Implementation:</strong><br/><a href="../org.apache.nifi.processors.aws.credentials.provider.service.AWSCredentialsProviderControllerService/index.html">AWSCredentialsProviderControllerService</a></td><td id="description">The Controller Service that is used to obtain aws credentials provider</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">No Description Provided.</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">Specifies an optional SSL Context Service that, if provided, will be used to creat
 e connections</td></tr></table><h3>Relationships: </h3><table id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>unprocessed</td><td>FlowFiles are routed to unprocessed relationship when DynamoDB is not able to process all the items in the request. Typical reasons are insufficient table throughput capacity and exceeding the maximum bytes per request. Unprocessed FlowFiles can be retried with a new request.</td></tr><tr><td>success</td><td>FlowFiles are routed to success relationship</td></tr><tr><td>failure</td><td>FlowFiles are routed to failure relationship</td></tr></table><h3>Reads Attributes: </h3><table id="reads-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>  dynamodb.item.hash.key.value</td><td>Items hash key value</td></tr><tr><td>  dynamodb.item.range.key.value</td><td>Items range key value</td></tr></table><h3>Writes Attributes: </h3><table id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>dynamodb.key.error.unproce
 ssed</td><td>Dynamo db unprocessed keys</td></tr><tr><td>dynmodb.range.key.value.error</td><td>Dynamod db range key error</td></tr><tr><td>dynamodb.key.error.not.found</td><td>Dynamo db key not found</td></tr><tr><td>dynamodb.error.exception.message</td><td>Dynamo db exception message</td></tr><tr><td>dynamodb.error.code</td><td>Dynamo db error code</td></tr><tr><td>dynamodb.error.message</td><td>Dynamo db error message</td></tr><tr><td>dynamodb.error.type</td><td>Dynamo db error type</td></tr><tr><td>dynamodb.error.service</td><td>Dynamo db error service</td></tr><tr><td>dynamodb.error.retryable</td><td>Dynamo db error is retryable</td></tr><tr><td>dynamodb.error.request.id</td><td>Dynamo db error request id</td></tr><tr><td>dynamodb.error.status.code</td><td>Dynamo db status code</td></tr></table><h3>See Also:</h3><p><a href="../org.apache.nifi.processors.aws.dynamodb.GetDynamoDB/index.html">GetDynamoDB</a>, <a href="../org.apache.nifi.processors.aws.dynamodb.PutDynamoDB/index.htm
 l">PutDynamoDB</a></p></body></html>
\ No newline at end of file

Added: nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.aws.dynamodb.GetDynamoDB/index.html
URL: http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.aws.dynamodb.GetDynamoDB/index.html?rev=1752359&view=auto
==============================================================================
--- nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.aws.dynamodb.GetDynamoDB/index.html (added)
+++ nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.aws.dynamodb.GetDynamoDB/index.html Tue Jul 12 22:38:04 2016
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta charset="utf-8"></meta><title>GetDynamoDB</title><link rel="stylesheet" href="../../css/component-usage.css" type="text/css"></link></head><body><h2>Description: </h2><p>Retrieves a document from DynamoDB based on hash and range key.  The key can be string or number.For any get request all the primary keys are required (hash or hash and range based on the table keys).A Json Document ('Map') attribute of the DynamoDB item is read into the content of the FlowFile.</p><h3>Tags: </h3><p>Amazon, DynamoDB, AWS, Get, Fetch</p><h3>Properties: </h3><p>In the list below, the names of required properties appear in <strong>bold</strong>. Any other properties (not in bold) are considered optional. The table also indicates any default values, whether a property supports the <a href="../../html/expression-language-guide.html">NiFi Expression Language</a>, and whether a property is considered "sensitive", meaning that its value will be encrypted. Before en
 tering 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>Table Name</strong></td><td id="default-value"></td><td id="allowable-values"></td><td id="description">The DynamoDB table name</td></tr><tr><td id="name"><strong>Hash Key Name</strong></td><td id="default-value"></td><td id="allowable-values"></td><td id="description">The hash key name of the item</td></tr><tr><td id="name">Range Key Name</td><td id="default-value"></td><td id="allowable-values"></td><td id="description">The range key name of the item</td></tr><tr><td id="name"><strong>Hash Key Value</strong></td><td id="default-value">${dynamodb.item.hash.key.value}</td><td id="allowable-values"></td><td id="description">The hash key value of the item<br/><strong>Supports Expres
 sion Language: true</strong></td></tr><tr><td id="name">Range Key Value</td><td id="default-value">${dynamodb.item.range.key.value}</td><td id="allowable-values"></td><td id="description">No Description Provided.<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td id="name"><strong>Hash Key Value Type</strong></td><td id="default-value">string</td><td id="allowable-values"><ul><li>string</li><li>number</li></ul></td><td id="description">The hash key value type of the item</td></tr><tr><td id="name"><strong>Range Key Value Type</strong></td><td id="default-value">string</td><td id="allowable-values"><ul><li>string</li><li>number</li></ul></td><td id="description">The range key value type of the item</td></tr><tr><td id="name"><strong>Json Document attribute</strong></td><td id="default-value"></td><td id="allowable-values"></td><td id="description">The Json document to be retrieved from the dynamodb item</td></tr><tr><td id="name">Batch items for each request (be
 tween 1 and 50)</td><td id="default-value">1</td><td id="allowable-values"></td><td id="description">The items to be retrieved in one batch</td></tr><tr><td id="name"><strong>Region</strong></td><td id="default-value">us-west-2</td><td id="allowable-values"><ul><li>us-gov-west-1 <img src="../../html/images/iconInfo.png" alt="us-gov-west-1" title="us-gov-west-1"></img></li><li>us-east-1 <img src="../../html/images/iconInfo.png" alt="us-east-1" title="us-east-1"></img></li><li>us-west-1 <img src="../../html/images/iconInfo.png" alt="us-west-1" title="us-west-1"></img></li><li>us-west-2 <img src="../../html/images/iconInfo.png" alt="us-west-2" title="us-west-2"></img></li><li>eu-west-1 <img src="../../html/images/iconInfo.png" alt="eu-west-1" title="eu-west-1"></img></li><li>eu-central-1 <img src="../../html/images/iconInfo.png" alt="eu-central-1" title="eu-central-1"></img></li><li>ap-southeast-1 <img src="../../html/images/iconInfo.png" alt="ap-southeast-1" title="ap-southeast-1"></i
 mg></li><li>ap-southeast-2 <img src="../../html/images/iconInfo.png" alt="ap-southeast-2" title="ap-southeast-2"></img></li><li>ap-northeast-1 <img src="../../html/images/iconInfo.png" alt="ap-northeast-1" title="ap-northeast-1"></img></li><li>sa-east-1 <img src="../../html/images/iconInfo.png" alt="sa-east-1" title="sa-east-1"></img></li><li>cn-north-1 <img src="../../html/images/iconInfo.png" alt="cn-north-1" title="cn-north-1"></img></li></ul></td><td id="description">No Description Provided.</td></tr><tr><td id="name">Access Key</td><td id="default-value"></td><td id="allowable-values"></td><td id="description">No Description Provided.<br/><strong>Sensitive Property: true</strong><br/><strong>Supports Expression Language: true</strong></td></tr><tr><td id="name">Secret Key</td><td id="default-value"></td><td id="allowable-values"></td><td id="description">No Description Provided.<br/><strong>Sensitive Property: true</strong><br/><strong>Supports Expression Language: true</strong
 ></td></tr><tr><td id="name">Credentials File</td><td id="default-value"></td><td id="allowable-values"></td><td id="description">Path to a file containing AWS access key and secret key in properties file format.</td></tr><tr><td id="name">AWS Credentials Provider service</td><td id="default-value"></td><td id="allowable-values"><strong>Controller Service API: </strong><br/>AWSCredentialsProviderService<br/><strong>Implementation:</strong><br/><a href="../org.apache.nifi.processors.aws.credentials.provider.service.AWSCredentialsProviderControllerService/index.html">AWSCredentialsProviderControllerService</a></td><td id="description">The Controller Service that is used to obtain aws credentials provider</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">No Description Provided.</td></tr><tr><td id="name">SSL Context Service</td><td id="default-value"></td><td id="allowable-value
 s"><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">Specifies an optional SSL Context Service that, if provided, will be used to create connections</td></tr></table><h3>Relationships: </h3><table id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>unprocessed</td><td>FlowFiles are routed to unprocessed relationship when DynamoDB is not able to process all the items in the request. Typical reasons are insufficient table throughput capacity and exceeding the maximum bytes per request. Unprocessed FlowFiles can be retried with a new request.</td></tr><tr><td>success</td><td>FlowFiles are routed to success relationship</td></tr><tr><td>failure</td><td>FlowFiles are routed to failure relationship</td></tr><tr><td>not found</td><td>FlowFiles are routed to not found relationship if key not found
  in the table</td></tr></table><h3>Reads Attributes: </h3><table id="reads-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>  dynamodb.item.hash.key.value</td><td>Items hash key value</td></tr><tr><td>  dynamodb.item.range.key.value</td><td>Items range key value</td></tr></table><h3>Writes Attributes: </h3><table id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>dynamodb.key.error.unprocessed</td><td>Dynamo db unprocessed keys</td></tr><tr><td>dynmodb.range.key.value.error</td><td>Dynamod db range key error</td></tr><tr><td>dynamodb.key.error.not.found</td><td>Dynamo db key not found</td></tr><tr><td>dynamodb.error.exception.message</td><td>Dynamo db exception message</td></tr><tr><td>dynamodb.error.code</td><td>Dynamo db error code</td></tr><tr><td>dynamodb.error.message</td><td>Dynamo db error message</td></tr><tr><td>dynamodb.error.type</td><td>Dynamo db error type</td></tr><tr><td>dynamodb.error.service</td><td>Dynamo db error service</td></tr
 ><tr><td>dynamodb.error.retryable</td><td>Dynamo db error is retryable</td></tr><tr><td>dynamodb.error.request.id</td><td>Dynamo db error request id</td></tr><tr><td>dynamodb.error.status.code</td><td>Dynamo db status code</td></tr></table><h3>See Also:</h3><p><a href="../org.apache.nifi.processors.aws.dynamodb.DeleteDynamoDB/index.html">DeleteDynamoDB</a>, <a href="../org.apache.nifi.processors.aws.dynamodb.PutDynamoDB/index.html">PutDynamoDB</a></p></body></html>
\ No newline at end of file

Added: nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.aws.dynamodb.PutDynamoDB/index.html
URL: http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.aws.dynamodb.PutDynamoDB/index.html?rev=1752359&view=auto
==============================================================================
--- nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.aws.dynamodb.PutDynamoDB/index.html (added)
+++ nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.aws.dynamodb.PutDynamoDB/index.html Tue Jul 12 22:38:04 2016
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta charset="utf-8"></meta><title>PutDynamoDB</title><link rel="stylesheet" href="../../css/component-usage.css" type="text/css"></link></head><body><h2>Description: </h2><p>Puts a document from DynamoDB based on hash and range key.  The table can have either hash and range or hash key alone. Currently the keys supported are string and number and value can be json document. In case of hash and range keys both key are required for the operation. The FlowFile content must be JSON. FlowFile content is mapped to the specified Json Document attribute in the DynamoDB item.</p><h3>Tags: </h3><p>Amazon, DynamoDB, AWS, Put, Insert</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>Table Name</strong></td><td id="default-value"></td><td id="allowable-values"></td><td id="description">The DynamoDB table name</td></tr><tr><td id="name"><strong>Hash Key Name</strong></td><td id="default-value"></td><td id="allowable-values"></td><td id="description">The hash key name of the item</td></tr><tr><td id="name">Range Key Name</td><td id="default-value"></td><td id="allowable-values"></td><td id="description">The range key name of the item</td></tr><tr><td id="name"><strong>Hash Key Value</strong></td><td id="default-value">${dynamodb.item.hash.key.value}</td><td id
 ="allowable-values"></td><td id="description">The hash key value of the item<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td id="name">Range Key Value</td><td id="default-value">${dynamodb.item.range.key.value}</td><td id="allowable-values"></td><td id="description">No Description Provided.<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td id="name"><strong>Hash Key Value Type</strong></td><td id="default-value">string</td><td id="allowable-values"><ul><li>string</li><li>number</li></ul></td><td id="description">The hash key value type of the item</td></tr><tr><td id="name"><strong>Range Key Value Type</strong></td><td id="default-value">string</td><td id="allowable-values"><ul><li>string</li><li>number</li></ul></td><td id="description">The range key value type of the item</td></tr><tr><td id="name"><strong>Json Document attribute</strong></td><td id="default-value"></td><td id="allowable-values"></td><td id="description">The Json doc
 ument to be retrieved from the dynamodb item</td></tr><tr><td id="name"><strong>Character set of document</strong></td><td id="default-value">UTF-8</td><td id="allowable-values"></td><td id="description">Character set of data in the document</td></tr><tr><td id="name">Batch items for each request (between 1 and 50)</td><td id="default-value">1</td><td id="allowable-values"></td><td id="description">The items to be retrieved in one batch</td></tr><tr><td id="name"><strong>Region</strong></td><td id="default-value">us-west-2</td><td id="allowable-values"><ul><li>us-gov-west-1 <img src="../../html/images/iconInfo.png" alt="us-gov-west-1" title="us-gov-west-1"></img></li><li>us-east-1 <img src="../../html/images/iconInfo.png" alt="us-east-1" title="us-east-1"></img></li><li>us-west-1 <img src="../../html/images/iconInfo.png" alt="us-west-1" title="us-west-1"></img></li><li>us-west-2 <img src="../../html/images/iconInfo.png" alt="us-west-2" title="us-west-2"></img></li><li>eu-west-1 <img
  src="../../html/images/iconInfo.png" alt="eu-west-1" title="eu-west-1"></img></li><li>eu-central-1 <img src="../../html/images/iconInfo.png" alt="eu-central-1" title="eu-central-1"></img></li><li>ap-southeast-1 <img src="../../html/images/iconInfo.png" alt="ap-southeast-1" title="ap-southeast-1"></img></li><li>ap-southeast-2 <img src="../../html/images/iconInfo.png" alt="ap-southeast-2" title="ap-southeast-2"></img></li><li>ap-northeast-1 <img src="../../html/images/iconInfo.png" alt="ap-northeast-1" title="ap-northeast-1"></img></li><li>sa-east-1 <img src="../../html/images/iconInfo.png" alt="sa-east-1" title="sa-east-1"></img></li><li>cn-north-1 <img src="../../html/images/iconInfo.png" alt="cn-north-1" title="cn-north-1"></img></li></ul></td><td id="description">No Description Provided.</td></tr><tr><td id="name">Access Key</td><td id="default-value"></td><td id="allowable-values"></td><td id="description">No Description Provided.<br/><strong>Sensitive Property: true</strong><br
 /><strong>Supports Expression Language: true</strong></td></tr><tr><td id="name">Secret Key</td><td id="default-value"></td><td id="allowable-values"></td><td id="description">No Description Provided.<br/><strong>Sensitive Property: true</strong><br/><strong>Supports Expression Language: true</strong></td></tr><tr><td id="name">Credentials File</td><td id="default-value"></td><td id="allowable-values"></td><td id="description">Path to a file containing AWS access key and secret key in properties file format.</td></tr><tr><td id="name">AWS Credentials Provider service</td><td id="default-value"></td><td id="allowable-values"><strong>Controller Service API: </strong><br/>AWSCredentialsProviderService<br/><strong>Implementation:</strong><br/><a href="../org.apache.nifi.processors.aws.credentials.provider.service.AWSCredentialsProviderControllerService/index.html">AWSCredentialsProviderControllerService</a></td><td id="description">The Controller Service that is used to obtain aws crede
 ntials provider</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">No Description Provided.</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">Specifies an optional SSL Context Service that, if provided, will be used to create connections</td></tr></table><h3>Relationships: </h3><table id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>unprocessed</td><td>FlowFiles are routed to unprocessed relationship when DynamoDB is not able to process all the items in the request. Typical reasons are insufficient table throughput capacity and exceeding the maximum bytes per request. Unprocesse
 d FlowFiles can be retried with a new request.</td></tr><tr><td>success</td><td>FlowFiles are routed to success relationship</td></tr><tr><td>failure</td><td>FlowFiles are routed to failure relationship</td></tr></table><h3>Reads Attributes: </h3><table id="reads-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>  dynamodb.item.hash.key.value</td><td>Items hash key value</td></tr><tr><td>  dynamodb.item.range.key.value</td><td>Items range key value</td></tr></table><h3>Writes Attributes: </h3><table id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>dynamodb.key.error.unprocessed</td><td>Dynamo db unprocessed keys</td></tr><tr><td>dynmodb.range.key.value.error</td><td>Dynamod db range key error</td></tr><tr><td>dynamodb.key.error.not.found</td><td>Dynamo db key not found</td></tr><tr><td>dynamodb.error.exception.message</td><td>Dynamo db exception message</td></tr><tr><td>dynamodb.error.code</td><td>Dynamo db error code</td></tr><tr><td>dynamodb.err
 or.message</td><td>Dynamo db error message</td></tr><tr><td>dynamodb.error.type</td><td>Dynamo db error type</td></tr><tr><td>dynamodb.error.service</td><td>Dynamo db error service</td></tr><tr><td>dynamodb.error.retryable</td><td>Dynamo db error is retryable</td></tr><tr><td>dynamodb.error.request.id</td><td>Dynamo db error request id</td></tr><tr><td>dynamodb.error.status.code</td><td>Dynamo db error status code</td></tr><tr><td>dynamodb.item.io.error</td><td>IO exception message on creating item</td></tr></table><h3>See Also:</h3><p><a href="../org.apache.nifi.processors.aws.dynamodb.DeleteDynamoDB/index.html">DeleteDynamoDB</a>, <a href="../org.apache.nifi.processors.aws.dynamodb.GetDynamoDB/index.html">GetDynamoDB</a></p></body></html>
\ No newline at end of file