Author: joewitt
Date: Tue Nov 29 12:33:21 2016
New Revision: 1771896
URL: http://svn.apache.org/viewvc?rev=1771896&view=rev
Log:
NIFI-3100
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.aws.cloudwatch.PutCloudWatchMetric/
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.aws.cloudwatch.PutCloudWatchMetric/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.aws.kinesis.stream.PutKinesisStream/
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.aws.kinesis.stream.PutKinesisStream/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.elasticsearch.FetchElasticsearch5/
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.elasticsearch.FetchElasticsearch5/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.elasticsearch.PutElasticsearch5/
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.elasticsearch.PutElasticsearch5/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.elasticsearch.QueryElasticsearchHttp/
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.elasticsearch.QueryElasticsearchHttp/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.elasticsearch.ScrollElasticsearchHttp/
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.elasticsearch.ScrollElasticsearchHttp/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.email.ExtractTNEFAttachments/
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.email.ExtractTNEFAttachments/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.enrich.QueryWhois/
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.enrich.QueryWhois/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.ignite.cache.GetIgniteCache/
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.ignite.cache.GetIgniteCache/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.kafka.pubsub.ConsumeKafka_0_10/additionalDetails.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.kafka.pubsub.PublishKafka_0_10/additionalDetails.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.FetchFTP/
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.FetchFTP/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ListFTP/
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ListFTP/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ParseCEF/
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ParseCEF/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.TailFile/additionalDetails.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ValidateCsv/
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ValidateCsv/additionalDetails.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ValidateCsv/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.websocket.ConnectWebSocket/
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.websocket.ConnectWebSocket/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.websocket.ListenWebSocket/
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.websocket.ListenWebSocket/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.websocket.PutWebSocket/
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.websocket.PutWebSocket/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.websocket.jetty.JettyWebSocketClient/
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.websocket.jetty.JettyWebSocketClient/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.websocket.jetty.JettyWebSocketServer/
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.websocket.jetty.JettyWebSocketServer/index.html
Modified:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.GetHTMLElement/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.ModifyHTMLElement/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.PutHTMLElement/index.html
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.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.couchbase.CouchbaseClusterService/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.dbcp.DBCPConnectionPool/index.html
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.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.hbase.GetHBase/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.hbase.HBase_1_1_2_ClientService/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.hbase.PutHBaseCell/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.http.StandardHttpContextMap/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.jms.cf.JMSConnectionFactoryProvider/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.jms.processors.ConsumeJMS/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.jms.processors.PublishJMS/additionalDetails.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.jms.processors.PublishJMS/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/additionalDetails.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.avro.ConvertAvroToJSON/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.avro.ExtractAvroMetadata/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.avro.SplitAvro/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.dynamodb.DeleteDynamoDB/index.html
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/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.ListS3/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.azure.eventhub.GetAzureEventHub/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.azure.eventhub.PutAzureEventHub/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.couchbase.GetCouchbaseKey/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.couchbase.PutCouchbaseKey/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.elasticsearch.FetchElasticsearch/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.elasticsearch.FetchElasticsearchHttp/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.elasticsearch.PutElasticsearchHttp/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.email.ConsumeIMAP/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.email.ConsumePOP3/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.email.ExtractEmailAttachments/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.email.ExtractEmailHeaders/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.email.ListenSMTP/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.enrich.QueryDNS/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.evtx.ParseEvtx/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.flume.ExecuteFlumeSink/additionalDetails.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.flume.ExecuteFlumeSink/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.flume.ExecuteFlumeSource/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.DeleteHDFS/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.hadoop.inotify.GetHDFSEvents/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.hive.ConvertAvroToORC/index.html
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.PutHiveStreaming/index.html
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.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.ignite.cache.PutIgniteCache/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.image.ExtractImageMetadata/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.image.ResizeImage/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.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.ConsumeKafka_0_10/index.html
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.kafka.pubsub.PublishKafka_0_10/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.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.InferAvroSchema/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.lumberjack.ListenLumberjack/index.html
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.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.mqtt.ConsumeMQTT/index.html
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.riemann.PutRiemann/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.slack.PutSlack/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.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.AttributesToJSON/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.ConvertJSONToSQL/index.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.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/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.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.ExecuteSQL/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.FetchDistributedMapCache/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.FetchSFTP/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.GenerateTableFetch/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.GetFTP/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.GetSFTP/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/additionalDetails.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.JoltTransformJSON/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ListDatabaseTables/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ListFile/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ListSFTP/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.ListenRELP/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ListenSyslog/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ListenTCP/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.ParseSyslog/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.PutDistributedMapCache/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.PutSQL/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.PutSyslog/index.html
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/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.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.RouteText/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.TailFile/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.windows.event.log.ConsumeWindowsEventLog/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.SiteToSiteProvenanceReportingTask/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.reporting.ambari.AmbariReportingTask/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.reporting.datadog.DataDogReportingTask/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.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/additionalDetails.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.snmp.processors.SetSNMP/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.spring.SpringContextProcessor/additionalDetails.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.spring.SpringContextProcessor/index.html
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.ssl.StandardSSLContextService/index.html
Modified:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.GetHTMLElement/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.GetHTMLElement/index.html?rev=1771896&r1=1771895&r2=1771896&view=diff
==============================================================================
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.GetHTMLElement/index.html
(original)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.GetHTMLElement/index.html
Tue Nov 29 12:33:21 2016
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta
charset="utf-8"></meta><title>GetHTMLElement</title><link rel="stylesheet"
href="../../css/component-usage.css"
type="text/css"></link></head><body><h2>Description: </h2><p>Extracts HTML
element values from the incoming flowfile's content using a CSS selector. The
incoming HTML is first converted into a HTML Document Object Model so that HTML
elements may be selected in the similar manner that CSS selectors are used to
apply styles to HTML. The resulting HTML DOM is then "queried" using the user
defined CSS selector string. The result of "querying" the HTML DOM may produce
0-N results. If no results are found the flowfile will be transferred to the
"element not found" relationship to indicate so to the end user. If N results
are found a new flowfile will be created and emitted for each result. The query
result will either be placed in the content of the new flowfile or as an
attribute of the new flowfile. By default the result is written to
an attribute. This can be controlled by the "Destination" property. Resulting
query values may also have data prepended or appended to them by setting the
value of property "Prepend Element Value" or "Append Element Value". Prepended
and appended values are treated as string values and concatenated to the result
retrieved from the HTML DOM query operation. A more thorough reference for the
CSS selector syntax can be found at
"http://jsoup.org/apidocs/org/jsoup/select/Selector.html";</p><h3>Tags:
</h3><p>get, html, dom, css, element</p><h3>Properties: </h3><p>In the list
below, the names of required properties appear in <strong>bold</strong>. Any
other properties (not in bold) are considered optional. The table also
indicates any default values, and whether a 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 i
d="name"><strong>URL</strong></td><td id="default-value"></td><td
id="allowable-values"></td><td id="description">Base URL for the HTML page
being parsed.</td></tr><tr><td id="name"><strong>CSS Selector</strong></td><td
id="default-value"></td><td id="allowable-values"></td><td id="description">CSS
selector syntax string used to extract the desired HTML
element(s).<br/><strong>Supports Expression Language:
true</strong></td></tr><tr><td id="name"><strong>HTML Character
Encoding</strong></td><td id="default-value">UTF-8</td><td
id="allowable-values"></td><td id="description">Character encoding of the input
HTML</td></tr><tr><td id="name"><strong>Output Type</strong></td><td
id="default-value">HTML</td><td
id="allowable-values"><ul><li>HTML</li><li>Text</li><li>Attribute</li><li>Data</li></ul></td><td
id="description">Controls the type of DOM value that is retrieved from the
HTML element.</td></tr><tr><td id="name"><strong>Destination</strong></td><td
id="default-value">flowfile-attri
bute</td><td
id="allowable-values"><ul><li>flowfile-attribute</li><li>flowfile-content</li></ul></td><td
id="description">Control if element extracted is written as a flowfile
attribute or as flowfile content.</td></tr><tr><td id="name">Prepend Element
Value</td><td id="default-value"></td><td id="allowable-values"></td><td
id="description">Prepends the specified value to the resulting
Element<br/><strong>Supports Expression Language:
true</strong></td></tr><tr><td id="name">Append Element Value</td><td
id="default-value"></td><td id="allowable-values"></td><td
id="description">Appends the specified value to the resulting
Element<br/><strong>Supports Expression Language:
true</strong></td></tr><tr><td id="name">Attribute Name</td><td
id="default-value"></td><td id="allowable-values"></td><td
id="description">When getting the value of a HTML element attribute this value
is used as the key to determine which attribute on the selected element should
be retrieved. This value is used whe
n the "Output Type" is set to "Attribute"<br/><strong>Supports Expression
Language: true</strong></td></tr></table><h3>Relationships: </h3><table
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>element
not found</td><td>Element could not be found in the HTML document. The original
HTML input will remain in the flowfile content unchanged. Relationship
'original' will not be invoked in this
scenario.</td></tr><tr><td>success</td><td>Successfully parsed HTML
element</td></tr><tr><td>original</td><td>The original HTML
input</td></tr><tr><td>invalid html</td><td>The input HTML syntax is
invalid</td></tr></table><h3>Reads Attributes: </h3>None specified.<h3>Writes
Attributes: </h3><table
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>HTMLElement</td><td>Flowfile
attribute where the element result parsed from the HTML using the CSS selector
syntax are placed if the destination is a flowfile
attribute.</td></tr></table><h3>See Also:</h3><p><a h
ref="../org.apache.nifi.ModifyHTMLElement/index.html">ModifyHTMLElement</a>,
<a
href="../org.apache.nifi.PutHTMLElement/index.html">PutHTMLElement</a></p></body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta
charset="utf-8"></meta><title>GetHTMLElement</title><link rel="stylesheet"
href="../../css/component-usage.css"
type="text/css"></link></head><body><h2>Description: </h2><p>Extracts HTML
element values from the incoming flowfile's content using a CSS selector. The
incoming HTML is first converted into a HTML Document Object Model so that HTML
elements may be selected in the similar manner that CSS selectors are used to
apply styles to HTML. The resulting HTML DOM is then "queried" using the user
defined CSS selector string. The result of "querying" the HTML DOM may produce
0-N results. If no results are found the flowfile will be transferred to the
"element not found" relationship to indicate so to the end user. If N results
are found a new flowfile will be created and emitted for each result. The query
result will either be placed in the content of the new flowfile or as an
attribute of the new flowfile. By default the result is written to
an attribute. This can be controlled by the "Destination" property. Resulting
query values may also have data prepended or appended to them by setting the
value of property "Prepend Element Value" or "Append Element Value". Prepended
and appended values are treated as string values and concatenated to the result
retrieved from the HTML DOM query operation. A more thorough reference for the
CSS selector syntax can be found at
"http://jsoup.org/apidocs/org/jsoup/select/Selector.html";</p><h3>Tags:
</h3><p>get, html, dom, css, element</p><h3>Properties: </h3><p>In the list
below, the names of required properties appear in <strong>bold</strong>. Any
other properties (not in bold) are considered optional. The table also
indicates any default values, and whether a 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 i
d="name"><strong>URL</strong></td><td id="default-value"></td><td
id="allowable-values"></td><td id="description">Base URL for the HTML page
being parsed.</td></tr><tr><td id="name"><strong>CSS Selector</strong></td><td
id="default-value"></td><td id="allowable-values"></td><td id="description">CSS
selector syntax string used to extract the desired HTML
element(s).<br/><strong>Supports Expression Language:
true</strong></td></tr><tr><td id="name"><strong>HTML Character
Encoding</strong></td><td id="default-value">UTF-8</td><td
id="allowable-values"></td><td id="description">Character encoding of the input
HTML</td></tr><tr><td id="name"><strong>Output Type</strong></td><td
id="default-value">HTML</td><td
id="allowable-values"><ul><li>HTML</li><li>Text</li><li>Attribute</li><li>Data</li></ul></td><td
id="description">Controls the type of DOM value that is retrieved from the
HTML element.</td></tr><tr><td id="name"><strong>Destination</strong></td><td
id="default-value">flowfile-attri
bute</td><td
id="allowable-values"><ul><li>flowfile-attribute</li><li>flowfile-content</li></ul></td><td
id="description">Control if element extracted is written as a flowfile
attribute or as flowfile content.</td></tr><tr><td id="name">Prepend Element
Value</td><td id="default-value"></td><td id="allowable-values"></td><td
id="description">Prepends the specified value to the resulting
Element<br/><strong>Supports Expression Language:
true</strong></td></tr><tr><td id="name">Append Element Value</td><td
id="default-value"></td><td id="allowable-values"></td><td
id="description">Appends the specified value to the resulting
Element<br/><strong>Supports Expression Language:
true</strong></td></tr><tr><td id="name">Attribute Name</td><td
id="default-value"></td><td id="allowable-values"></td><td
id="description">When getting the value of a HTML element attribute this value
is used as the key to determine which attribute on the selected element should
be retrieved. This value is used whe
n the "Output Type" is set to "Attribute"<br/><strong>Supports Expression
Language: true</strong></td></tr></table><h3>Relationships: </h3><table
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>element
not found</td><td>Element could not be found in the HTML document. The original
HTML input will remain in the FlowFile content unchanged. Relationship
'original' will not be invoked in this
scenario.</td></tr><tr><td>success</td><td>Successfully parsed HTML
element</td></tr><tr><td>original</td><td>The original HTML
input</td></tr><tr><td>invalid html</td><td>The input HTML syntax is
invalid</td></tr></table><h3>Reads Attributes: </h3>None specified.<h3>Writes
Attributes: </h3><table
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>HTMLElement</td><td>Flowfile
attribute where the element result parsed from the HTML using the CSS selector
syntax are placed if the destination is a flowfile
attribute.</td></tr></table><h3>State management: </h
3>This processor has no state management.<h3>Restricted: </h3><h3>See
Also:</h3><p><a
href="../org.apache.nifi.ModifyHTMLElement/index.html">ModifyHTMLElement</a>,
<a
href="../org.apache.nifi.PutHTMLElement/index.html">PutHTMLElement</a></p></body></html>
\ No newline at end of file
Modified:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.ModifyHTMLElement/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.ModifyHTMLElement/index.html?rev=1771896&r1=1771895&r2=1771896&view=diff
==============================================================================
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.ModifyHTMLElement/index.html
(original)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.ModifyHTMLElement/index.html
Tue Nov 29 12:33:21 2016
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta
charset="utf-8"></meta><title>ModifyHTMLElement</title><link rel="stylesheet"
href="../../css/component-usage.css"
type="text/css"></link></head><body><h2>Description: </h2><p>Modifies the value
of an existing HTML element. The desired element to be modified is located by
using CSS selector syntax. The incoming HTML is first converted into a HTML
Document Object Model so that HTML elements may be selected in the similar
manner that CSS selectors are used to apply styles to HTML. The resulting HTML
DOM is then "queried" using the user defined CSS selector string to find the
element the user desires to modify. If the HTML element is found the element's
value is updated in the DOM using the value specified "Modified Value"
property. All DOM elements that match the CSS selector will be updated. Once
all of the DOM elements have been updated the DOM is rendered to HTML and the
result replaces the flowfile content with the updated HTML. A more th
orough reference for the CSS selector syntax can be found at
"http://jsoup.org/apidocs/org/jsoup/select/Selector.html";</p><h3>Tags:
</h3><p>modify, html, dom, css, element</p><h3>Properties: </h3><p>In the list
below, the names of required properties appear in <strong>bold</strong>. Any
other properties (not in bold) are considered optional. The table also
indicates any default values, and whether a property supports the <a
href="../../html/expression-language-guide.html">NiFi Expression
Language</a>.</p><table id="properties"><tr><th>Name</th><th>Default
Value</th><th>Allowable Values</th><th>Description</th></tr><tr><td
id="name"><strong>URL</strong></td><td id="default-value"></td><td
id="allowable-values"></td><td id="description">Base URL for the HTML page
being parsed.</td></tr><tr><td id="name"><strong>CSS Selector</strong></td><td
id="default-value"></td><td id="allowable-values"></td><td id="description">CSS
selector syntax string used to extract the desired HTML element(s)
.<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td
id="name"><strong>HTML Character Encoding</strong></td><td
id="default-value">UTF-8</td><td id="allowable-values"></td><td
id="description">Character encoding of the input HTML</td></tr><tr><td
id="name"><strong>Output Type</strong></td><td id="default-value">HTML</td><td
id="allowable-values"><ul><li>HTML</li><li>Text</li><li>Attribute</li></ul></td><td
id="description">Controls whether the HTML element is output as HTML,Text or
Data</td></tr><tr><td id="name"><strong>Modified Value</strong></td><td
id="default-value"></td><td id="allowable-values"></td><td
id="description">Value to update the found HTML elements
with<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td
id="name">Attribute Name</td><td id="default-value"></td><td
id="allowable-values"></td><td id="description">When modifying the value of an
element attribute this value is used as the key to determine which attribute on
th
e selected element will be modified with the new value.<br/><strong>Supports
Expression Language: true</strong></td></tr></table><h3>Relationships:
</h3><table
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>element
not found</td><td>Element could not be found in the HTML document. The original
HTML input will remain in the flowfile content unchanged. Relationship
'original' will not be invoked in this
scenario.</td></tr><tr><td>success</td><td>Successfully parsed HTML
element</td></tr><tr><td>original</td><td>The original HTML
input</td></tr><tr><td>invalid html</td><td>The input HTML syntax is
invalid</td></tr></table><h3>Reads Attributes: </h3>None specified.<h3>Writes
Attributes: </h3><table
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>NumElementsModified</td><td>Total
number of HTML element modifications made</td></tr></table><h3>See
Also:</h3><p><a
href="../org.apache.nifi.GetHTMLElement/index.html">GetHTMLElement</a>, <a
href="
../org.apache.nifi.PutHTMLElement/index.html">PutHTMLElement</a></p></body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta
charset="utf-8"></meta><title>ModifyHTMLElement</title><link rel="stylesheet"
href="../../css/component-usage.css"
type="text/css"></link></head><body><h2>Description: </h2><p>Modifies the value
of an existing HTML element. The desired element to be modified is located by
using CSS selector syntax. The incoming HTML is first converted into a HTML
Document Object Model so that HTML elements may be selected in the similar
manner that CSS selectors are used to apply styles to HTML. The resulting HTML
DOM is then "queried" using the user defined CSS selector string to find the
element the user desires to modify. If the HTML element is found the element's
value is updated in the DOM using the value specified "Modified Value"
property. All DOM elements that match the CSS selector will be updated. Once
all of the DOM elements have been updated the DOM is rendered to HTML and the
result replaces the flowfile content with the updated HTML. A more th
orough reference for the CSS selector syntax can be found at
"http://jsoup.org/apidocs/org/jsoup/select/Selector.html";</p><h3>Tags:
</h3><p>modify, html, dom, css, element</p><h3>Properties: </h3><p>In the list
below, the names of required properties appear in <strong>bold</strong>. Any
other properties (not in bold) are considered optional. The table also
indicates any default values, and whether a property supports the <a
href="../../html/expression-language-guide.html">NiFi Expression
Language</a>.</p><table id="properties"><tr><th>Name</th><th>Default
Value</th><th>Allowable Values</th><th>Description</th></tr><tr><td
id="name"><strong>URL</strong></td><td id="default-value"></td><td
id="allowable-values"></td><td id="description">Base URL for the HTML page
being parsed.</td></tr><tr><td id="name"><strong>CSS Selector</strong></td><td
id="default-value"></td><td id="allowable-values"></td><td id="description">CSS
selector syntax string used to extract the desired HTML element(s)
.<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td
id="name"><strong>HTML Character Encoding</strong></td><td
id="default-value">UTF-8</td><td id="allowable-values"></td><td
id="description">Character encoding of the input HTML</td></tr><tr><td
id="name"><strong>Output Type</strong></td><td id="default-value">HTML</td><td
id="allowable-values"><ul><li>HTML</li><li>Text</li><li>Attribute</li></ul></td><td
id="description">Controls whether the HTML element is output as HTML,Text or
Data</td></tr><tr><td id="name"><strong>Modified Value</strong></td><td
id="default-value"></td><td id="allowable-values"></td><td
id="description">Value to update the found HTML elements
with<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td
id="name">Attribute Name</td><td id="default-value"></td><td
id="allowable-values"></td><td id="description">When modifying the value of an
element attribute this value is used as the key to determine which attribute on
th
e selected element will be modified with the new value.<br/><strong>Supports
Expression Language: true</strong></td></tr></table><h3>Relationships:
</h3><table
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>element
not found</td><td>Element could not be found in the HTML document. The original
HTML input will remain in the FlowFile content unchanged. Relationship
'original' will not be invoked in this
scenario.</td></tr><tr><td>success</td><td>Successfully parsed HTML
element</td></tr><tr><td>original</td><td>The original HTML
input</td></tr><tr><td>invalid html</td><td>The input HTML syntax is
invalid</td></tr></table><h3>Reads Attributes: </h3>None specified.<h3>Writes
Attributes: </h3><table
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>NumElementsModified</td><td>Total
number of HTML element modifications made</td></tr></table><h3>State
management: </h3>This processor has no state management.<h3>Restricted:
</h3><h3>See Also:</h3>
<p><a href="../org.apache.nifi.GetHTMLElement/index.html">GetHTMLElement</a>,
<a
href="../org.apache.nifi.PutHTMLElement/index.html">PutHTMLElement</a></p></body></html>
\ No newline at end of file
Modified:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.PutHTMLElement/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.PutHTMLElement/index.html?rev=1771896&r1=1771895&r2=1771896&view=diff
==============================================================================
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.PutHTMLElement/index.html
(original)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.PutHTMLElement/index.html
Tue Nov 29 12:33:21 2016
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta
charset="utf-8"></meta><title>PutHTMLElement</title><link rel="stylesheet"
href="../../css/component-usage.css"
type="text/css"></link></head><body><h2>Description: </h2><p>Places a new HTML
element in the existing HTML DOM. The desired position for the new HTML element
is specified by using CSS selector syntax. The incoming HTML is first converted
into a HTML Document Object Model so that HTML DOM location may be located in a
similar manner that CSS selectors are used to apply styles to HTML. The
resulting HTML DOM is then "queried" using the user defined CSS selector string
to find the position where the user desires to add the new HTML element. Once
the new HTML element is added to the DOM it is rendered to HTML and the result
replaces the flowfile content with the updated HTML. A more thorough reference
for the CSS selector syntax can be found at
"http://jsoup.org/apidocs/org/jsoup/select/Selector.html";</p><h3>Tags:
</h3><p>put, html, d
om, css, element</p><h3>Properties: </h3><p>In the list below, the names of
required properties appear in <strong>bold</strong>. Any other properties (not
in bold) are considered optional. The table also indicates any default values,
and whether a property supports the <a
href="../../html/expression-language-guide.html">NiFi Expression
Language</a>.</p><table id="properties"><tr><th>Name</th><th>Default
Value</th><th>Allowable Values</th><th>Description</th></tr><tr><td
id="name"><strong>URL</strong></td><td id="default-value"></td><td
id="allowable-values"></td><td id="description">Base URL for the HTML page
being parsed.</td></tr><tr><td id="name"><strong>CSS Selector</strong></td><td
id="default-value"></td><td id="allowable-values"></td><td id="description">CSS
selector syntax string used to extract the desired HTML
element(s).<br/><strong>Supports Expression Language:
true</strong></td></tr><tr><td id="name"><strong>HTML Character
Encoding</strong></td><td id="default-value">UT
F-8</td><td id="allowable-values"></td><td id="description">Character encoding
of the input HTML</td></tr><tr><td id="name"><strong>Element Insert Location
Type</strong></td><td id="default-value">append-html</td><td
id="allowable-values"><ul><li>append-html</li><li>prepend-html</li></ul></td><td
id="description">Controls whether the new element is prepended or appended to
the children of the Element located by the CSS selector. EX: prepended value
'<b>Hi</b>' inside of Element (using CSS Selector 'p')
'<p>There</p>' would result in
'<p><b>Hi</b>There</p>'. Appending the value would
result in '<p>There<b>Hi</b></p>'</td></tr><tr><td
id="name"><strong>Put Value</strong></td><td id="default-value"></td><td
id="allowable-values"></td><td id="description">Value used when creating the
new Element. Value should be a valid HTML element. The text should be supplied
unencoded: characters like '<', '>', etc will be
properly HTML encoded in the resulting output.<br/><strong>Supports Expression
Language: true</strong></td></tr></table><h3>Relationships: </h3><table
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>element
not found</td><td>Element could not be found in the HTML document. The original
HTML input will remain in the flowfile content unchanged. Relationship
'original' will not be invoked in this
scenario.</td></tr><tr><td>success</td><td>Successfully parsed HTML
element</td></tr><tr><td>original</td><td>The original HTML
input</td></tr><tr><td>invalid html</td><td>The input HTML syntax is
invalid</td></tr></table><h3>Reads Attributes: </h3>None specified.<h3>Writes
Attributes: </h3>None specified.<h3>See Also:</h3><p><a
href="../org.apache.nifi.GetHTMLElement/index.html">GetHTMLElement</a>, <a
href="../org.apache.nifi.ModifyHTMLElement/index.html">ModifyHTMLElement</a></p></body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta
charset="utf-8"></meta><title>PutHTMLElement</title><link rel="stylesheet"
href="../../css/component-usage.css"
type="text/css"></link></head><body><h2>Description: </h2><p>Places a new HTML
element in the existing HTML DOM. The desired position for the new HTML element
is specified by using CSS selector syntax. The incoming HTML is first converted
into a HTML Document Object Model so that HTML DOM location may be located in a
similar manner that CSS selectors are used to apply styles to HTML. The
resulting HTML DOM is then "queried" using the user defined CSS selector string
to find the position where the user desires to add the new HTML element. Once
the new HTML element is added to the DOM it is rendered to HTML and the result
replaces the flowfile content with the updated HTML. A more thorough reference
for the CSS selector syntax can be found at
"http://jsoup.org/apidocs/org/jsoup/select/Selector.html";</p><h3>Tags:
</h3><p>put, html, d
om, css, element</p><h3>Properties: </h3><p>In the list below, the names of
required properties appear in <strong>bold</strong>. Any other properties (not
in bold) are considered optional. The table also indicates any default values,
and whether a property supports the <a
href="../../html/expression-language-guide.html">NiFi Expression
Language</a>.</p><table id="properties"><tr><th>Name</th><th>Default
Value</th><th>Allowable Values</th><th>Description</th></tr><tr><td
id="name"><strong>URL</strong></td><td id="default-value"></td><td
id="allowable-values"></td><td id="description">Base URL for the HTML page
being parsed.</td></tr><tr><td id="name"><strong>CSS Selector</strong></td><td
id="default-value"></td><td id="allowable-values"></td><td id="description">CSS
selector syntax string used to extract the desired HTML
element(s).<br/><strong>Supports Expression Language:
true</strong></td></tr><tr><td id="name"><strong>HTML Character
Encoding</strong></td><td id="default-value">UT
F-8</td><td id="allowable-values"></td><td id="description">Character encoding
of the input HTML</td></tr><tr><td id="name"><strong>Element Insert Location
Type</strong></td><td id="default-value">append-html</td><td
id="allowable-values"><ul><li>append-html</li><li>prepend-html</li></ul></td><td
id="description">Controls whether the new element is prepended or appended to
the children of the Element located by the CSS selector. EX: prepended value
'<b>Hi</b>' inside of Element (using CSS Selector 'p')
'<p>There</p>' would result in
'<p><b>Hi</b>There</p>'. Appending the value would
result in '<p>There<b>Hi</b></p>'</td></tr><tr><td
id="name"><strong>Put Value</strong></td><td id="default-value"></td><td
id="allowable-values"></td><td id="description">Value used when creating the
new Element. Value should be a valid HTML element. The text should be supplied
unencoded: characters like '<', '>', etc will be
properly HTML encoded in the resulting output.<br/><strong>Supports Expression
Language: true</strong></td></tr></table><h3>Relationships: </h3><table
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>element
not found</td><td>Element could not be found in the HTML document. The original
HTML input will remain in the FlowFile content unchanged. Relationship
'original' will not be invoked in this
scenario.</td></tr><tr><td>success</td><td>Successfully parsed HTML
element</td></tr><tr><td>original</td><td>The original HTML
input</td></tr><tr><td>invalid html</td><td>The input HTML syntax is
invalid</td></tr></table><h3>Reads Attributes: </h3>None specified.<h3>Writes
Attributes: </h3>None specified.<h3>State management: </h3>This processor has
no state management.<h3>Restricted: </h3><h3>See Also:</h3><p><a
href="../org.apache.nifi.GetHTMLElement/index.html">GetHTMLElement</a>, <a
href="../org.apache.nifi.ModifyHTMLElement/index.html">ModifyHTMLElement</a></p></body
></html>
\ No newline at end of file
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=1771896&r1=1771895&r2=1771896&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 Nov 29 12:33:21 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><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
+<!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.<h3>State management:
</h3>This processor has no state management.<h3>Restricted: </h3></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=1771896&r1=1771895&r2=1771896&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 Nov 29 12:33:21 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><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
+<!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.<h3>St
ate management: </h3>This processor has no state management.<h3>Restricted:
</h3></body></html>
\ No newline at end of file
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=1771896&r1=1771895&r2=1771896&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
Tue Nov 29 12:33:21 2016
@@ -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.</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><h3>State
management: </h3>This processor has no state management.<h3>Restricted:
</h3></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=1771896&r1=1771895&r2=1771896&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
Tue Nov 29 12:33:21 2016
@@ -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 specified directory and warns (via a log
message and a System-Level Bulletin) if the partition on which it lives 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>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 partition on which
the directory found is of concern</td></tr><tr><td id="name"><strong>Directory
Location</strong></td><td id="default-value"></td><td
id="allowable-values"></td><td id="description">The directory path of the
partition to be monitored.</td></tr><tr><td id="name">Directory Display
Name</td><td id="default-value">Un-Named</td><td id="allowable-values"></td><td
id="description">The name to display for the directory in
alerts.</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 specified directory and warns (via a log
message and a System-Level Bulletin) if the partition on which it lives 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>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 partition on which
the directory found is of concern</td></tr><tr><td id="name"><strong>Directory
Location</strong></td><td id="default-value"></td><td
id="allowable-values"></td><td id="description">The directory path of the
partition to be monitored.</td></tr><tr><td id="name">Directory Display
Name</td><td id="default-value">Un-Named</td><td id="allowable-values"></td><td
id="description">The name to display for the directory in
alerts.</td></tr></table><h3>State management: </h3>This processor has no state
management.<h3>Restricted: </h3></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=1771896&r1=1771895&r2=1771896&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 Nov 29 12:33:21 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"><ul><li
>Code Cache</li><li>Metaspace</li><li>Compressed Class Space</li><li>G1 Eden
>Space</li><li>G1 Survivor Space</li><li>G1 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
+<!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>G1 Eden
>Space</li><li>G1 Survivor Space</li><li>G1 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><h3>State management: </h3>This processor has no
>state management.<h3>Restricted: </h3></body></html>
\ No newline at end of file
Modified:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.couchbase.CouchbaseClusterService/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.couchbase.CouchbaseClusterService/index.html?rev=1771896&r1=1771895&r2=1771896&view=diff
==============================================================================
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.couchbase.CouchbaseClusterService/index.html
(original)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.couchbase.CouchbaseClusterService/index.html
Tue Nov 29 12:33:21 2016
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta
charset="utf-8"></meta><title>CouchbaseClusterService</title><link
rel="stylesheet" href="../../css/component-usage.css"
type="text/css"></link></head><body><h2>Description: </h2><p>Provides a
centralized Couchbase connection and bucket passwords management. Bucket
passwords can be specified via dynamic properties.</p><h3>Tags: </h3><p>nosql,
couchbase, database, connection</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>Connection String</strong></td><td
id="default-value"></td><td id="allowable-values"></td><td id="description">The
hostnames or ip addresses of the bootstraping nodes and optional parameters.
Syntax) couchbase://node1,n
ode2,nodeN?param1=value1&param2=value2&paramN=valueN</td></tr></table><h3>Dynamic
Properties: </h3><p>Dynamic Properties allow the user to specify both the name
and value of a property.<table
id="dynamic-properties"><tr><th>Name</th><th>Value</th><th>Description</th></tr><tr><td
id="name">Bucket Password for BUCKET_NAME</td><td id="value">bucket
password</td><td>Specify bucket password if
neseccery.</td></tr></table></p></body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta
charset="utf-8"></meta><title>CouchbaseClusterService</title><link
rel="stylesheet" href="../../css/component-usage.css"
type="text/css"></link></head><body><h2>Description: </h2><p>Provides a
centralized Couchbase connection and bucket passwords management. Bucket
passwords can be specified via dynamic properties.</p><h3>Tags: </h3><p>nosql,
couchbase, database, connection</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>Connection String</strong></td><td
id="default-value"></td><td id="allowable-values"></td><td id="description">The
hostnames or ip addresses of the bootstraping nodes and optional parameters.
Syntax) couchbase://node1,n
ode2,nodeN?param1=value1&param2=value2&paramN=valueN</td></tr></table><h3>Dynamic
Properties: </h3><p>Dynamic Properties allow the user to specify both the name
and value of a property.<table
id="dynamic-properties"><tr><th>Name</th><th>Value</th><th>Description</th></tr><tr><td
id="name">Bucket Password for BUCKET_NAME</td><td id="value">bucket
password</td><td>Specify bucket password if
necessary.</td></tr></table></p><h3>State management: </h3>This processor has
no state management.<h3>Restricted: </h3></body></html>
\ No newline at end of file
