[nifi] Git Push Summary
Repository: nifi Updated Tags: refs/tags/rel/nifi-1.7.0 [created] 75eaea16f
svn commit: r1834461 [34/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.PutSQL/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.PutSQL/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.PutSQL/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.PutSQL/index.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1 @@
+PutSQLwindow.onload =
function(){if(self==top) { document.getElementById('nameHeader').style.display
= "inherit"; } }PutSQLDescription: Executes a SQL UPDATE or INSERT
command. The content of an incoming FlowFile is expected to be the SQL command
to execute. The SQL command may use the ? to escape parameters. In this case,
the parameters to use must exist as FlowFile attributes with the naming
convention sql.args.N.type and sql.args.N.value, where N is a positive integer.
The sql.args.N.type is expected to be a number indicating the JDBC Type. The
content of the FlowFile is expected to be in UTF-8 format.Tags:
sql, put, rdbms, database, update, insert,
relationalProperties: In the list below, the names of required properties appear in
>bold. Any other properties (not in bold) are considered
>optional. The table also indicates any default values, and whether a property
>supports the href="../../../../../html/expression-language-guide.html">NiFi Expression
>Language.NameDefault
>ValueAllowable ValuesDescriptionid="name">JDBC Connection Poolid="default-value">Controller Service
>API: DBCPServiceImplementations: href="../../../nifi-dbcp-service-nar/1.7.0/org.apache.nifi.dbcp.DBCPConnectionPoolLookup/index.html">DBCPConnectionPoolLookup
>href="../../../nifi-dbcp-service-nar/1.7.0/org.apache.nifi.dbcp.DBCPConnectionPool/index.html">DBCPConnectionPool
>href="../../../nifi-hive-nar/1.7.0/org.apache.nifi.dbcp.hive.HiveConnectionPool/index.
html">HiveConnectionPoolSpecifies the JDBC
Connection Pool to use in order to convert the JSON message to a SQL statement.
The Connection Pool is necessary in order to determine the appropriate database
column types.SQL StatementThe
SQL statement to execute. The statement can be empty, a constant value, or
built from attributes using Expression Language. If this property is specified,
it will be used regardless of the content of incoming flowfiles. If this
property is empty, the content of the incoming flow file is expected to contain
a valid SQL statement, to be issued by the processor to the
database.Supports Expression Language: true (will be evaluated
using flow file attributes and variable registry)Support Fragmented TransactionstruetruefalseIf true, when
a FlowFile is consumed by this Processor, the Processor will first check the
fragment.identifier and fragment.count attributes of that FlowFile. If the
fragment.count value is greater than 1, the Processor will not process any
FlowFile with that fragment.identifier until all are available; at that point,
it will process all FlowFiles with that fragment.identifier as a single
transaction, in the order specified by the FlowFiles' fragment.index
attributes. This Provides atomicity of those SQL statements. If this value is
false, these attributes will be ignored and the updates will occur independent
of one another.Transaction TimeoutIf
the Support Fragmented Transactions property is set to true, specifies
how long to wait for all FlowFiles for a particular fragment.identifier
attribute to
arrive before just transferring all of the FlowFiles with that identifier to
the 'failure' relationshipBatch
Size100The preferred number of
FlowFiles to put to the database in a single transactionObtain Generated KeysfalsetruefalseIf true, any key that is automatically generated by the
database will be added to the FlowFile that generated it using the
sql.generate.key attribute. This may result in slightly slower performance and
is not supported by all databases.Rollback
On FailurefalsetruefalseSpecify how to handle error. By default (false), if an error
occurs wh
ile processing a FlowFile, the FlowFile will be routed to 'failure' or 'retry'
relationship based on error type, and processor can continue with next
FlowFile. Instead, you may want to rollback currently processed FlowFiles and
stop further processing immediately. In that case, you can do so by enabling
this 'Rollback On Failure' property. If enabled, failed FlowFiles will stay in
the input relationship without penalizing it and being processed repeatedly
until it gets processed successfully or removed by other means. It is important
to set adequate 'Yield Duration' to avoid retrying
svn commit: r1834461 [38/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache
Modified: nifi/site/trunk/docs/nifi-docs/html/administration-guide.html URL: http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/html/administration-guide.html?rev=1834461=1834460=1834461=diff == --- nifi/site/trunk/docs/nifi-docs/html/administration-guide.html (original) +++ nifi/site/trunk/docs/nifi-docs/html/administration-guide.html Wed Jun 27 00:37:46 2018 @@ -1,4 +1,20 @@ - + + @@ -528,6 +544,7 @@ body.book #toc,body.book #preamble,body. Encrypted Write Ahead Provenance Repository Properties Component Status Repository Site to Site Properties +Site to Site Routing Properties for Reverse Proxies Web Properties Security Properties Identity Mapping Properties @@ -897,7 +914,7 @@ properties can be specified. -It is important when enabling HTTPS that the nifi.web.http.port property be unset. +It is important when enabling HTTPS that the nifi.web.http.port property be unset. NiFi only supports running on HTTP or HTTPS, not both simultaneously. @@ -2361,6 +2378,15 @@ memberUid: user2 * + +view provenance + + + +* + + + @@ -2539,15 +2565,17 @@ Instructions requiring interaction with - - - + + + + Policy Privilege Global Menu Selection +Resource Descriptor @@ -2555,16 +2583,19 @@ Instructions requiring interaction with view the UI Allow users to view the UI N/A +/flow access the controller Allows users to view/modify the controller including Reporting Tasks, Controller Services, and Nodes in the Cluster Controller Settings +/controller query provenance Allows users to submit a Provenance Search and request Event Lineage Data Provenance +/provenance access restricted components @@ -2573,36 +2604,43 @@ components may indicate which specific p restrictions or be granted regardless of restrictions. If permission is granted regardless of restrictions, the user can create/modify all restricted components. N/A +/restricted-components access all policies Allows users to view/modify the policies for all components Policies +/policies access users/user groups Allows users to view/modify the users and user groups Users +/tenants retrieve site-to-site details Allows other NiFi instances to retrieve Site-To-Site details N/A +/site-to-site view system diagnostics Allows users to view System Diagnostics Summary +/system proxy user requests Allows proxy machines to send requests on the behalf of others N/A +/proxy access counters Allows users to view/modify Counters Counters +/counters @@ -2614,47 +2652,62 @@ the user can create/modify all restricte - - + + + Policy Privilege +Resource Descriptor Action view the component Allows users to view component configuration details +resource="/component-type/component-UUID" action="R" modify the component Allows users to modify component configuration details +resource="/component-type/component-UUID" action="W" + + +view provenance +Allows users to view provenance events generated by this component +resource="/provenance-data/component-type/component-UUID" action="R" view the data -Allows user to view metadata and content for this component through provenance data and flowfile queues in outbound connections +Allows users to view metadata and content for this component in flowfile queues in outbound connections and through provenance events +resource="/data/component-type/component-UUID" action="R" modify the data -Allows user to empty flowfile queues in outbound connections and submit replays +Allows users to empty flowfile queues in outbound connections and submit replays through provenance events +resource="/data/component-type/component-UUID" action="W" view the policies Allows users to view the list of users who can view/modify a component +resource="/policies/component-type/component-UUID" action="R" modify the policies Allows users to modify the list of users who can view/modify a component +resource="/policies/component-type/component-UUID" action="W" receive data via site-to-site Allows a port to receive data from NiFi instances +resource="/data-transfer/input-ports/port-UUID" action="W" send data via site-to-site Allows a port to send data from NiFi instances +resource="/data-transfer/output-ports/port-UUID" action="W" @@ -4187,8 +4240,8 @@ they must be set the same on every insta -Under the Web Properties section, set either the http or https port that you want the Node to run on. -Also, consider whether you need to set the http or https host property. +Under the Web Properties section, set either the HTTP or HTTPS port that you want the Node to run on. +Also, consider whether you need to set the HTTP or HTTPS host property. All nodes in the cluster should use the same protocol setting.
svn commit: r1834461 [39/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache
Modified: nifi/site/trunk/docs/nifi-docs/html/user-guide.html URL: http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/html/user-guide.html?rev=1834461=1834460=1834461=diff == --- nifi/site/trunk/docs/nifi-docs/html/user-guide.html (original) +++ nifi/site/trunk/docs/nifi-docs/html/user-guide.html Wed Jun 27 00:37:46 2018 @@ -1,4 +1,20 @@ - + + @@ -499,6 +515,8 @@ body.book #toc,body.book #preamble,body. Change Version Stop Version Control Nested Versioned Flows +Variables in Versioned Flows +Restricted Components in Versioned Flows Templates @@ -857,12 +875,16 @@ of restrictions. If permission is grante Allows users to modify component configuration details +view provenance +Allows users to view provenance events generated by this component + + view the data -Allows users to view metadata and content for this component through provenance data and flowfile queues in outbound connection +Allows users to view metadata and content for this component in flowfile queues in outbound connections and through provenance events modify the data -Allows users to empty flowfile queues in outbound connections and to submit replays +Allows users to empty flowfile queues in outbound connections and submit replays through provenance events view the policies @@ -955,20 +977,17 @@ Processors that allow us to ingest files Restricted components will be marked with a -icon next to their name. Hovering over the tooltip will display the specific restrictions this component requires. If the component -does not list any specific restrictions it will require access to restricted components regardless of restrictions. These are components +icon next to their name. These are components that can be used to execute arbitrary unsanitized code provided by the operator through the NiFi REST API/UI or can be used to obtain or alter data on the NiFi host system using the NiFi OS credentials. These components could be used by an otherwise authorized NiFi user to go beyond the intended use of the application, escalate privilege, or could expose data about the internals of the NiFi process or the host system. All of these capabilities should be considered privileged, and admins should be aware of these capabilities and -explicitly enable them for a subset of trusted users. - - -Before a user is allowed to create and modify restricted components they must be granted access to restricted components. This can be +explicitly enable them for a subset of trusted users. Before a user is allowed to create and modify restricted components they must be granted access. Hovering over the +icon will display the specific permissions a restricted component requires. Permissions can be assigned regardless of restrictions. In this case, the user will have access to all restricted components. Alternatively, users can be assigned access to specific restrictions. If the user has been granted access to all restrictions a component requires, they will have access to that component assuming otherwise sufficient permissions. For more information refer to -Accessing the UI with Multi-Tenant Authorization. +Accessing the UI with Multi-Tenant Authorization and Restricted Components in Versioned Flows. Clicking the Add button or double-clicking on a Processor Type will add the selected Processor to the canvas at the @@ -1434,20 +1453,20 @@ such as when a DFM starts an entire Proc Below the Name configuration, the Processors unique identifier is displayed along with the Processors type and NAR bundle. These values cannot be modified. -Next are two dialogues for configuring `Penalty duration' and `Yield duration'. During the normal course of processing a +Next are two dialogues for configuring 'Penalty Duration' and 'Yield Duration'. During the normal course of processing a piece of data (a FlowFile), an event may occur that indicates that the data cannot be processed at this time but the data may be processable at a later time. When this occurs, the Processor may choose to Penalize the FlowFile. This will prevent the FlowFile from being Processed for some period of time. For example, if the Processor is to push the data to a remote service, but the remote service already has a file with the same name as the filename that the Processor -is specifying, the Processor may penalize the FlowFile. The `Penalty duration' allows the DFM to specify how long the +is specifying, the Processor may penalize the FlowFile. The 'Penalty Duration' allows the DFM to specify how long the FlowFile should be penalized. The default value is 30 seconds. Similarly, the Processor may determine that some situation exists such that the Processor can no longer make any progress, regardless of the data that it is processing. For example, if a Processor is to push data to a remote
svn commit: r1834461 [31/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.ListenHTTP/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.ListenHTTP/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.ListenHTTP/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.ListenHTTP/index.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1 @@
+ListenHTTPwindow.onload =
function(){if(self==top) { document.getElementById('nameHeader').style.display
= "inherit"; } }ListenHTTPDescription: Starts an HTTP Server and
listens on a given base path to transform incoming requests into FlowFiles. The
default URI of the Service will be http://{hostname}:{port}/contentListener.
Only HEAD and POST requests are supported. GET, PUT, and DELETE will result in
an error and the HTTP response status code 405.Tags: ingest,
http, https, rest, listenProperties: In the list below, the
names of required properties appear in bold. Any other
properties (not in bold) are considered optional. The table also indicates any d
efault values, and whether a property supports the NiFi Expression
Language.NameDefault
ValueAllowable ValuesDescriptionBase PathcontentListenerBase path for incoming connectionsSupports
Expression Language: true (will be evaluated using variable registry
only)Listening
PortThe Port to listen on for
incoming connectionsSupports Expression Language: true (will be
evaluated using variable registry only)Max
Data to Receive per SecondThe maximum amount
of data to receive per second; this allows the bandwidth to be throttled to a
specified data rate; if not specified, the data rate is not
throttledSSL Context ServiceController Service
API: RestrictedSSLContextServiceImplementation:
StandardRestrictedSSLContextServiceThe Controller Service to use in order to obtain an SSL
ContextAuthorized DN
Pattern.*A Regular Expression to apply
against the Distinguished Name of incoming connections. If the Pattern does not
match the DN, the connection will be refused.Max Unconfirmed Flowfile Time60 secsThe maximum amount of time to wait for a FlowFile to be
confirmed before it is removed from the cacheHTTP
Headers to receive as Attributes (Regex)Specifies the Regular
Expression that determines the names of HTTP Headers that should be passed
along as FlowFile attributesReturn Code200The HTTP return code returned after every HTTP
callRelationships: NameDescriptionsuccessRelationship
for successfully received FlowFilesReads Attributes:
None specified.Writes Attributes: None specified.State
management: This component does not store sta
te.Restricted: This component is not restricted.Input
requirement: This component does not allow an incoming
relationship.System Resource Considerations:None
specified.
\ No newline at end of file
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.ListenRELP/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.ListenRELP/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.ListenRELP/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.ListenRELP/index.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1 @@
+ListenRELPwindow.onload =
function(){if(self==top) { document.getElementById('nameHeader').style.display
= "inherit"; } }ListenRELPDescription: Listens for RELP messages being
sent to a given port over TCP. Each message will be acknowledged after
successfully writing the message to a FlowFile. Each FlowFile will contain data
portion of one or more RELP frames. In the case where the RELP frames contain
syslog messages, the output of this processor can be sent to a ParseSyslog
processor for further processing.Tags: listen, relp, tcp,
logsProperties: In the list below, the names of required
properties appear in bold. Any other properties (not in bold)
are c
onsidered optional. The table also indicates any default values, and whether a
property supports the NiFi Expression
Language.NameDefault
ValueAllowable ValuesDescriptionLocal Network InterfaceThe name of a local network
interface to be used to restrict listening to a specific
LAN.Supports Expression Language: true (will be evaluated using
variable registry
svn commit: r1834461 [41/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache
Modified: nifi/site/trunk/docs/nifi-docs/rest-api/index.html URL: http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/rest-api/index.html?rev=1834461=1834460=1834461=diff == --- nifi/site/trunk/docs/nifi-docs/rest-api/index.html (original) +++ nifi/site/trunk/docs/nifi-docs/rest-api/index.html Wed Jun 27 00:37:46 2018 @@ -15,7 +15,7 @@ --> -NiFi Rest Api-1.6.0 +NiFi Rest Api-1.7.0 @@ -471,7 +471,7 @@ /nifi-api -NiFi Rest Api 1.6.0 +NiFi Rest Api 1.7.0 @@ -2013,6 +2013,19 @@ +disconnectedNodeAcknowledged +query + + + +boolean + + + +Acknowledges that this node is disconnected to allow for mutable requests to proceed. + + + id path @@ -2477,6 +2490,19 @@ +disconnectedNodeAcknowledged +query + + + +boolean + + + +Acknowledges that this node is disconnected to allow for mutable requests to proceed. + + + id path @@ -5094,6 +5120,19 @@ +disconnectedNodeAcknowledged +query + + + +boolean + + + +Acknowledges that this node is disconnected to allow for mutable requests to proceed. + + + id path @@ -14074,6 +14113,19 @@ +disconnectedNodeAcknowledged +query + + + +boolean + + + +Acknowledges that this node is disconnected to allow for mutable requests to proceed. + + + id path @@ -14530,6 +14582,19 @@ +disconnectedNodeAcknowledged +query + + + +boolean + + + +Acknowledges that this node is disconnected to allow for mutable requests to proceed. + + + id path @@ -14986,6 +15051,19 @@ +disconnectedNodeAcknowledged +query + + + +boolean + + + +Acknowledges that this node is disconnected to allow for mutable requests to proceed. + + + id path @@ -15442,6 +15520,19 @@ +disconnectedNodeAcknowledged +query + + + +boolean + + + +Acknowledges that this node is disconnected to allow for mutable requests to proceed. + + + id path @@ -16202,6 +16293,19 @@ +disconnectedNodeAcknowledged +query + + + +boolean + + + +Acknowledges that this node is disconnected to allow for mutable requests to proceed. + + + id path @@ -16531,6 +16635,19 @@ The ID of the Variable Registry Update Request + +disconnectedNodeAcknowledged +query + + + +boolean + + + +Acknowledges that this node is disconnected to allow for mutable requests to proceed. + + @@ -16971,6 +17088,19 @@ +disconnectedNodeAcknowledged +query + + + +boolean + + + +Acknowledges that this node is disconnected to allow for mutable requests to proceed. + + + id path @@
svn commit: r1834461 [37/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-update-attribute-nar/1.7.0/org.apache.nifi.processors.attributes.UpdateAttribute/additionalDetails.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-update-attribute-nar/1.7.0/org.apache.nifi.processors.attributes.UpdateAttribute/additionalDetails.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-update-attribute-nar/1.7.0/org.apache.nifi.processors.attributes.UpdateAttribute/additionalDetails.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-update-attribute-nar/1.7.0/org.apache.nifi.processors.attributes.UpdateAttribute/additionalDetails.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1,396 @@
+
+
+
+
+
+UpdateAttribute
+
+
+
+
+
+
+Description:
+
+This processor updates the attributes of a FlowFile using
properties or rules that are added by the user.
+There are three ways to use this processor to add or modify
attributes. One way is the "Basic Usage"; this allows you to set default
attribute changes that affect
+every FlowFile going through the processor. The second way is the
"Advanced Usage"; this allows you to make conditional attribute changes that
only affect a FlowFile if it
+meets certain conditions. It is possible to use both methods in
the same processor at the same time. The third way is the "Delete Attributes
Expression"; this allows you to
+provide a regular expression and any attributes with a matching
name will be deleted.
+
+
+
+Please note that "Delete Attributes Expression" supersedes any
updates that occur. If an existing attribute matches the "Delete Attributes
Expression", it will be removed whether it
+was updated or not. That said, the "Delete Attributes Expression"
only applies to attributes that exist in the input FlowFile, if it is added by
this processor, the "Delete Attributes Expression"
+will not detect it.
+
+
+
+Properties:
+
+
+The properties in this processor are added by the user. The
expression language is supported in user-added
+properties for this processor. See the NiFi Expression Language
Guide to learn how to formulate proper expression language statements to
perform the desired functions.
+
+
+
+If an Attribute is added with the name
alternate.identifier and that attribute's value is a URI, an
ADD_INFO Provenance Event will be registered,
+correlating the FlowFile with the given alternate identifier.
+
+
+
+Relationships:
+
+
+success
+
+If the processor successfully updates the specified
attribute(s), then the FlowFile follows this relationship.
+
+
+set state fail
+
+If the processor is running statefully, and fails to
set the state after adding attributes to the FlowFile, then the FlowFile will
be routed to this relationship.
+
+
+
+
+
+Basic Usage
+
+
+
+For basic usage, changes are made by adding a new processor
property and referencing as its name the attribute you want to change. Then
enter the desired attribute
+value as the Value. The Value can be as simple as any text string
or it can be a NiFi Expression Language statement that specifies how to
formulate the value.
+(See the NiFi Expression Language Usage Guide for details on
crafting NiFi Expression Language statements.)
+
+
+
+As an example, to alter the standard "filename" attribute so that
it has ".txt" appended to the end of it, add a new property and make the
property
+name "filename" (to reference the desired attribute), and as the
value, use the NiFi Expression Language statement shown below:
+
+
+
+Property: filename
+
+Value: ${filename}.txt
+
+
+
+
+The preceding example illustrates how to modify an existing
attribute. If an attribute does not already exist, this processor can also be
used to add a new attribute.
+For example, the following property could be added to create a new
attribute called myAttribute that has the value myValue:
+
+
+
+Property: myAttribute
+
+Value: myValue
+
+
+
+
+In this example, all FlowFiles passing through this processor will
receive an additional FlowFile attribute called
svn commit: r1834461 [23/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-rethinkdb-nar/1.7.0/org.apache.nifi.processors.rethinkdb.PutRethinkDB/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-rethinkdb-nar/1.7.0/org.apache.nifi.processors.rethinkdb.PutRethinkDB/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-rethinkdb-nar/1.7.0/org.apache.nifi.processors.rethinkdb.PutRethinkDB/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-rethinkdb-nar/1.7.0/org.apache.nifi.processors.rethinkdb.PutRethinkDB/index.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1 @@
+PutRethinkDBwindow.onload =
function(){if(self==top) { document.getElementById('nameHeader').style.display
= "inherit"; } }PutRethinkDBDescription: Processor to write the JSON
content of a FlowFile to RethinkDB (https://www.rethinkdb.com/). The flow file
should contain either JSON Object an array of JSON documentsTags:
rethinkdb, stream, insert, update, write, putProperties:
In the list below, the names of required properties appear in
bold. Any other properties (not in bold) are considered
optional. The table also indicates any default values, whether a property
supports the NiFi
Expression La
nguage, 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 nifi.properties file has an entry for the
property nifi.sensitive.props.key.NameDefault ValueAllowable
ValuesDescriptionDB
NameRethinkDB database to connect
toHostnamelocalhostRethinkDB hostnameDB
Port28015RethinkDB database port to
connect toUsernameUsername for accessing RethinkDBid="name">Passwordid="allowable-values">Password for
>userSensitive Property: trueid="name">Table nameid="allowable-values">RethinkDB table to connect
>toCharacter Setid="default-value">UTF-8id="description">Specifies the character set of the document
>data.Supports Expression Language: true (will be evaluated using
>flow file attributes and variable registry)id="name">Conflict strategyid="default-value">updateUpdate src="../../../../../html/images/iconInfo.png" alt="Update the document having
>same id with new values" title="Update the
document having same id with new values">Replace Error Conflict strategy to be used
in case of inserting existing document.Supports Expression
Language: true (will be evaluated using flow file attributes and variable
registry)Durablity of
documentshardHard Soft Durability of documents
being insertedSupports Expression Language: true (will be
evaluated using flow file attributes and variable
registry)Max size of
documents1 MBMaximum size of documents
allowed to be posted in one batchRelationships:
NameDescriptionsuccessSucessful
FlowFiles are routed to this
relationshipfailureFailed FlowFiles are routed to
this relationshipReads Attributes: None
specified.Writes Attributes: NameDescriptionrethinkdb.error.messageRethinkDB
error messa
gerethinkdb.insert.errorsError count while
inserting documentsrethinkdb.insert.deletedNumber of
documents deletedrethinkdb.insert.generated_keysKeys
generated on inserting
documentsrethinkdb.insert.insertedNumber of
documents insertedrethinkdb.insert.replacedNumber of
documents replacedrethinkdb.insert.skippedNumber of
documents skipped because they already
existedrethinkdb.insert.unchangedNumber of documents
unchanged since they already
existedrethinkdb.insert.first_errorFirst error while
inserting documentsrethinkdb.insert.warningsWarning
message in case of large number of ids being returned on
insertionState management: This component does not
store state.Restricted: This component is not restricted.In
put requirement: This component requires an incoming
relationship.System Resource Considerations:None specified.See
Also:GetRethinkDB,
DeleteRethinkDB
\ No newline at end of file
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-riemann-nar/1.7.0/org.apache.nifi.processors.riemann.PutRiemann/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-riemann-nar/1.7.0/org.apache.nifi.processors.riemann.PutRiemann/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-riemann-nar/1.7.0/org.apache.nifi.processors.riemann.PutRiemann/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-riemann-nar/1.7.0/org.apache.nifi.processors.riemann.PutRiemann/index.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1 @@
+PutRiemannwindow.onload =
function(){if(self==top) { document.getElementById('nameHeader').style.display
= "inherit"; } }PutRiemannDescription: Send events to Riemann
svn commit: r1834461 [19/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-mongodb-nar/1.7.0/org.apache.nifi.processors.mongodb.GetMongo/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-mongodb-nar/1.7.0/org.apache.nifi.processors.mongodb.GetMongo/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-mongodb-nar/1.7.0/org.apache.nifi.processors.mongodb.GetMongo/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-mongodb-nar/1.7.0/org.apache.nifi.processors.mongodb.GetMongo/index.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1 @@
+GetMongowindow.onload =
function(){if(self==top) { document.getElementById('nameHeader').style.display
= "inherit"; } }GetMongoDescription: Creates FlowFiles from documents
in MongoDBTags: mongodb, read, getProperties:
In the list below, the names of required properties appear in
bold. Any other properties (not in bold) are considered
optional. The table also indicates any default values, and whether a property
supports the NiFi
Expression Language.NameDefault
ValueAllowable ValuesDescriptionMo
ngo URIMongoURI, typically of the
form: mongodb://host1[:port1][,host2[:port2],...]Supports
Expression Language: true (will be evaluated using variable registry
only)Mongo Database
NameThe name of the database to
useSupports Expression Language: true (will be evaluated using
flow file attributes and variable registry)Mongo Collection NameThe
name of the collection to useSupports Expression Language: true
(will be evaluated using flow file attributes and variable
registry)SSL Context ServiceController Service API:
SSLContextServiceImplementations: StandardRestrictedSSLContextServiceStandardSSLContextServiceThe SSL Context Service used to provide client certificate
information for TLS/SSL connections.Client
AuthREQUIREDWANTREQUIREDNONEClient authentication policy when connecting to secure
(TLS/SSL) cluster. Possible values are REQUIRED, WANT, NONE. This property is
only used when an SSL Context has been defined and enabled.JSON TypeExtend
edExtended JSON Standard JSON By default, MongoDB's Java driver returns "extended JSON".
Some of the features of this variant of JSON may cause problems for other JSON
parsers that expect only standard JSON types and conventions. This
configuration setting controls whether to use extended JSON or provide a
clean view that conforms to standard JSON.Pretty Print Results JSONtrueTrueFalseChoose whether or not to pretty print the JSON from the
results of the query. Choosing yes can greatly increase the space requirements
on disk depending on the complexity of the JSON documentCharacter SetUTF-8Specifies the character set of the document
data.Supports Expression Language: true (will be evaluated using
flow file attributes and variable registry)QueryThe selection criteria to do
the lookup. If the field is left blank, it will look for input from an incoming
connection from anot
her processor to provide the query as a valid JSON document inside of the
flowfile's body. If this field is left blank and a timer is enabled instead of
an incoming connection, that will result in a full collection fetch using a
"{}" query.Supports Expression Language: true (will be evaluated
using flow file attributes and variable registry)Query Output AttributeIf set, the query will be
written to a specified attribute on the output flowfiles.Supports
Expression Language: true (will be evaluated using flow file attributes and
variable registry)ProjectionThe
fields to be returned from the documents in the result set; must be a valid
BSON documentSupports Expression Language: true (will be evaluated
using
flow file attributes and variable registry)SortThe fields by which to sort;
must be a valid BSON documentSupports Expression Language: true
(will be evaluated using flow file attributes and variable
registry)LimitThe
maximum number of elements to returnSupports Expression Language:
true (will be evaluated using flow file attributes and variable
registry)Batch SizeThe
number of elements returned from the server in one batchSupports
Expression Language: true (will be evaluated using flow file attributes and
variable registry)Results Per
FlowFile<
td id="default-value">How many results to put into a flowfile at once. The whole
body will be treated as a JSON array of results.Supports
Expression Language: true (will be evaluated using flow file attributes and
variable registry)SSL Context
ServiceController Service API:
SSLContextServiceImplementations: StandardRestrictedSSLContextServiceStandardSSLContextServiceThe SSL Context Service used to provide client certificate
information for TLS/SSL connections.Client
AuthREQUIREDWANTREQUIREDNONEClient authentication policy when connecting to secure
(TLS/SSL) cluster. Possible
svn commit: r1834461 [27/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.EncryptContent/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.EncryptContent/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.EncryptContent/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.EncryptContent/index.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1 @@
+EncryptContentwindow.onload =
function(){if(self==top) { document.getElementById('nameHeader').style.display
= "inherit"; } }EncryptContentDescription: Encrypts or Decrypts a
FlowFile using either symmetric encryption with a password and randomly
generated salt, or asymmetric encryption using a public and secret
key.Additional
Details...Tags: encryption, decryption, password, JCE,
OpenPGP, PGP, GPGProperties: In the list below, the names of
required properties appear in bold. Any other properties (not
in bold) are considered optional. The table also indicates any default values,
whether a property supports the
NiFi Expression
Language, 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 nifi.properties file has an entry for the
property nifi.sensitive.props.key.NameDefault ValueAllowable
ValuesDescriptionModeEncryptEncryptDecryptSpecifies whether the content should be encrypted or
decryptedKey Derivation
FunctionBCRYPTNiFi Legacy KDF OpenSSL
EVP_BytesToKey Bcrypt Scrypt PBKDF2 None Specifies the key derivation function to generate the key from
the password (and salt)Encryption
AlgorithmMD5_128AESMD5_128AES MD5_192AES MD5_256AES MD5_DES MD5_RC2 SHA1_RC2 SHA1_DES SHA_128AES SHA_192AES SHA_256AES SHA_40RC2 SHA_128RC2 SHA_40RC4 SHA_128RC4 SHA256_128AES SHA256_192AES SHA256_256AES SHA_2KEYTRIPLEDES SHA_3KEYTRIPLEDES SHA_TWOFISH PGP PGP_ASCII_ARMOR AES_CBC AES_CTR AES_GCM The
Encryption Algorithm to useAllow insecure
cryptographic modesnot-allowedAllowed Not Allowed Overrides the default behavior to prevent unsafe combinations
of encryption algorithms and short passwords on JVMs with limited strength
cryptographic jurisdiction policiesPasswordThe Password to use for encrypting or
decrypting the dataSensitive Property:
trueRaw Key (hexadecimal)In
keyed encryption, this is the raw key, encoded in
hexadecimalSensitive Property: truePublic Keyring FileIn a PGP encrypt mode, this
keyring contains the public key of the recipientPublic Key User IdIn a PGP encrypt mode, this
user id of the recipientPrivate Keyring
FileIn a PGP decrypt mode, this keyring contains the private key
of the recipientPrivate Keyring PassphraseIn a PGP decrypt mode, this is
the private keyring passphraseSensitive Property:
trueSupports Expression Language: true (will be evaluated
using variable registry only)Relationships:
NameDescriptionsuccessAny
FlowFile that is successfully encrypted or decrypted will be routed to
successfailureAny FlowFile that cannot be encrypted
or decrypted will be routed to failureReads Attributes:
None specified.Writes Attributes: None specified.State
management: This component does not store state.Restricted: This
component is not restricted.Input requirement: This component requires
an incoming relationship.System Resource Considerations:
ResourceDescriptionCPUAn
instance of this component can cause high usage of this system resource.
Multiple instances or high concurrency settings may result a degradation of
performance.
\ No newline at end of file
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.EnforceOrder/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.EnforceOrder/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.EnforceOrder/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.EnforceOrder/index.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1 @@
+EnforceOrderwindow.onload =
function(){if(self==top) { document.getElementById('nameHeader').style.display
= "inherit"; } }EnforceOrderDescription: Enforces expected ordering of
FlowFiles those belong to the same data group. Although
PriorityAttributePrioritizer can be used on a connection to ensure
svn commit: r1834461 [24/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-site-to-site-reporting-nar/1.7.0/org.apache.nifi.reporting.SiteToSiteStatusReportingTask/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-site-to-site-reporting-nar/1.7.0/org.apache.nifi.reporting.SiteToSiteStatusReportingTask/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-site-to-site-reporting-nar/1.7.0/org.apache.nifi.reporting.SiteToSiteStatusReportingTask/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-site-to-site-reporting-nar/1.7.0/org.apache.nifi.reporting.SiteToSiteStatusReportingTask/index.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1 @@
+SiteToSiteStatusReportingTaskwindow.onload =
function(){if(self==top) { document.getElementById('nameHeader').style.display
= "inherit"; } }SiteToSiteStatusReportingTaskDescription: Publishes
Status events using the Site To Site protocol. The component type and name
filter regexes form a union: only components matching both regexes will be
reported. However, all process groups are recursively searched for matching
components, regardless of whether the process group matches the component
filters.Additional
Details...Tags: status, metrics, history, site, site to
siteProperties: In the list below, the names of required
propertie
s appear in bold. Any other properties (not in bold) are
considered optional. The table also indicates any default values, whether a
property supports the NiFi Expression
Language, 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 nifi.properties file has an entry for the
property nifi.sensitive.props.key.NameDefault ValueAllowable
ValuesDescriptionDestination
URLThe URL of the destination NiFi instance to send data to,
should be a comma-separated list of address in the format of
http(s)://host:port/nifi.Supports Expression Language: true (will
be evaluated using
variable registry only)Input
Port NameThe name of the Input Port to
deliver data to.Supports Expression Language: true (will be
evaluated using variable registry only)SSL
Context ServiceController Service API:
RestrictedSSLContextServiceImplementation:
StandardRestrictedSSLContextServiceThe SSL Context Service to use when communicating with the
destination. If not specified, communications will not be
secure.Instance URLhttp://${hostname(true)}:8080/nifiThe URL of this instance to use in the
Content URI of each event.Supports Expression Language: true (will
be evaluated using variable registry only)Compress EventstruetruefalseIndicates whether or not to compress the data being
sent.Communications
Timeout30 secsSpecifies how long to wait to a
response from the destination before deciding that an error has occurred and
canceling the transactionBatch
Size1000Specifies how many records to
send in a single batch, at most.Transport
Proto
colRAWRAWHTTPSpecifies which transport protocol to use for Site-to-Site
communication.HTTP Proxy hostnameSpecify the proxy server's hostname to use. If not specified,
HTTP traffics are sent directly to the target NiFi instance.HTTP Proxy portSpecify the proxy server's port
number, optional. If not specified, default port 80 will be
used.HTTP Proxy usernameSpecify an user name to connect to the proxy server,
optional.HTTP Proxy passwordSpecify an user password to connect to the proxy server,
optional.Sensitive Property: trueRecord WriterController Service API:
RecordSetWriterFactoryImplementations: AvroRecordSetWriterCSVRecordSetWriterFreeFormTextRecordSetWriterJsonRecordSetWriterScriptedRecordSetWriterXMLRecordSetWriterSpecifies the Controller Service to use for writing out the
records.PlatformnifiThe value to use for the platform field in each status
record.Supports Expression Language: true (will be evaluated using
variable registry only)Component
Type Filter Regex(Processor|ProcessGroup|RemoteProcessGroup|RootProcessGroup|Connection|InputPort|OutputPort)A regex specifying which
component types to report. Any component type matching this regex will be
included. Component types are: Processor,
RootProcessGroup, ProcessGroup, RemoteProcessGroup, Connection, InputPort,
OutputPortSupports Expression Language: true (will be evaluated
using variable registry only)Component Name Filter Regex.*A
regex specifying which component names to report. Any component name matching
this regex will be included.Supports Expression Language: true
(will be evaluated using variable registry
only)State management: This component does
not store state.Restricted: This component is not
restricted.System Resource Considerations:None specified.
\ No newline at end of file
Added:
svn commit: r1834461 [26/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.CalculateRecordStats/additionalDetails.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.CalculateRecordStats/additionalDetails.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.CalculateRecordStats/additionalDetails.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.CalculateRecordStats/additionalDetails.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1,47 @@
+
+
+
+
+
+CalculateRecordStats
+
+
+
+
+This processor takes in a record set and counts both the overall count
and counts that are defined as dynamic properties
+that map a property name to a record path. Record path counts are provided
at two levels:
+
+The overall count of all records that successfully evaluated a
record path.
+A breakdown of counts of unique values that matched the record
path operation.
+
+Consider the following record structure:
+
+{
+"sport": "Soccer",
+"name": "John Smith"
+}
+
+A valid mapping here would be sport => /sport.
+For a record set with JSON like that, five entries and 3 instances of
soccer and two instances of football, it would set the following
+attributes:
+
+record_count: 5
+sport: 5
+sport.Soccer: 3
+sport.Football: 2
+
+
+
\ No newline at end of file
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.CalculateRecordStats/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.CalculateRecordStats/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.CalculateRecordStats/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.CalculateRecordStats/index.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1 @@
+CalculateRecordStatswindow.onload =
function(){if(self==top) { document.getElementById('nameHeader').style.display
= "inherit"; } }CalculateRecordStatsDescription: A processor that can
count the number of items in a record set, as well as provide counts based on
user-defined criteria on subsets of the record set.Additional Details...Tags:
record, stats, metricsProperties: In the list below,
the names of required properties appear in bold. Any other
properties (not in bold) are considered optional. The table also indicates any
default values, and whether a property supports the NiFi Expression Language.NameDefault ValueAllowable
ValuesDescriptionRecord
ReaderController Service API:
RecordReaderFactoryImplementations: ScriptedReaderGrokReaderJsonPathReaderJsonTreeReaderAvroReaderXMLReaderCSVReaderA record reader to use for reading the
records.record-stats-limit10Limit the number of individual stats that are returned for
each record path to the top N results.Supports Expression
Language: true (will be evaluated using flow file attributes and variable
registry)Relationships: NameDescriptionsuccessIf
a flowfile is successfully processed, it goes
here.failureIf a flowfile fails to be processed, it
goes here.
Reads Attributes: None specified.Writes Attributes:
NameDescriptionrecord.countA
count of the records in the record set in the
flowfile.recordStats.User Defined Property
Name.countA count of the records that contain a value for the user
defined property.recordStats.User Defined Property
Name.value.countEach value discovered for the user defined
property will have its own count attribute. Total number of top N value counts
to be added is defined by the limit configuration.State
management: This component does not store state.Restricted: This
component is not restricted.Input requirement: This component requires
an incoming relationship.System Resource Considerations:None
specified.
\ No newline at end of file
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.CompressContent/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.CompressContent/index.html?rev=1834461=auto
svn commit: r1834461 [14/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-10-nar/1.7.0/org.apache.nifi.processors.kafka.pubsub.PublishKafkaRecord_0_10/additionalDetails.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-10-nar/1.7.0/org.apache.nifi.processors.kafka.pubsub.PublishKafkaRecord_0_10/additionalDetails.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-10-nar/1.7.0/org.apache.nifi.processors.kafka.pubsub.PublishKafkaRecord_0_10/additionalDetails.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-10-nar/1.7.0/org.apache.nifi.processors.kafka.pubsub.PublishKafkaRecord_0_10/additionalDetails.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1,143 @@
+
+
+
+
+
+PublishKafka
+
+
+
+
+
+Description:
+
+This Processor puts the contents of a FlowFile to a Topic in
+http://kafka.apache.org/;>Apache Kafka using
KafkaProducer API available
+with Kafka 0.10.x API. The contents of the incoming FlowFile will
be read using the
+configured Record Reader. Each record will then be serialized
using the configured
+Record Writer, and this serialized form will be the content of a
Kafka message.
+This message is optionally assigned a key by using the Kafka
Key Property.
+
+Security Configuration:
+
+The Security Protocol property allows the user to specify the
protocol for communicating
+with the Kafka broker. The following sections describe each of the
protocols in further detail.
+
+PLAINTEXT
+
+This option provides an unsecured connection to the broker, with
no client authentication and no encryption.
+In order to use this option the broker must be configured with a
listener of the form:
+
+PLAINTEXT://host.name:port
+
+
+SSL
+
+This option provides an encrypted connection to the broker, with
optional client authentication. In order
+to use this option the broker must be configured with a listener
of the form:
+
+SSL://host.name:port
+
+In addition, the processor must have an SSL Context Service
selected.
+
+
+If the broker specifies ssl.client.auth=none, or does not specify
ssl.client.auth, then the client will
+not be required to present a certificate. In this case, the SSL
Context Service selected may specify only
+a truststore containing the public key of the certificate
authority used to sign the broker's key.
+
+
+If the broker specifies ssl.client.auth=required then the client
will be required to present a certificate.
+In this case, the SSL Context Service must also specify a keystore
containing a client key, in addition to
+a truststore as described above.
+
+SASL_PLAINTEXT
+
+This option uses SASL with a PLAINTEXT transport layer to
authenticate to the broker. In order to use this
+option the broker must be configured with a listener of the form:
+
+SASL_PLAINTEXT://host.name:port
+
+In addition, the Kerberos Service Name must be specified in the
processor.
+
+SASL_PLAINTEXT - GSSAPI
+
+If the SASL mechanism is GSSAPI, then the client must provide a
JAAS configuration to authenticate. The
+JAAS configuration can be provided by specifying the
java.security.auth.login.config system property in
+NiFi's bootstrap.conf, such as:
+
+
java.arg.16=-Djava.security.auth.login.config=/path/to/kafka_client_jaas.conf
+
+
+
+An example of the JAAS config file would be the following:
+
+KafkaClient {
+com.sun.security.auth.module.Krb5LoginModule required
+useKeyTab=true
+storeKey=true
+keyTab="/path/to/nifi.keytab"
+serviceName="kafka"
+principal="n...@yourrealm.com";
+};
+
+NOTE: The serviceName in the JAAS file must match the Kerberos
Service Name in the processor.
+
+
+Alternatively, starting with Apache NiFi 1.2.0 which uses the
Kafka 0.10.2 client, the JAAS
+configuration when using GSSAPI can be provided by specifying the
Kerberos Principal and Kerberos Keytab
+directly in the processor properties. This will dynamically create
a JAAS configuration like above, and
+will take precedence over the java.security.auth.login.config
system property.
+
+SASL_PLAINTEXT -
svn commit: r1834461 [15/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-11-nar/1.7.0/org.apache.nifi.processors.kafka.pubsub.ConsumeKafka_0_11/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-11-nar/1.7.0/org.apache.nifi.processors.kafka.pubsub.ConsumeKafka_0_11/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-11-nar/1.7.0/org.apache.nifi.processors.kafka.pubsub.ConsumeKafka_0_11/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-11-nar/1.7.0/org.apache.nifi.processors.kafka.pubsub.ConsumeKafka_0_11/index.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1 @@
+ConsumeKafka_0_11window.onload =
function(){if(self==top) { document.getElementById('nameHeader').style.display
= "inherit"; } }ConsumeKafka_0_11Description: Consumes messages from
Apache Kafka specifically built against the Kafka 0.11.x Consumer API. The
complementary NiFi processor for sending messages is
PublishKafka_0_11.Additional
Details...Tags: Kafka, Get, Ingest, Ingress, Topic, PubSub,
Consume, 0.11.xProperties: In the list below, the names of
required properties appear in bold. Any other properties (not
in bold) are considered optional. The table also indicates any default values,
and whether a proper
ty supports the NiFi Expression
Language.NameDefault
ValueAllowable ValuesDescriptionKafka Brokerslocalhost:9092A comma-separated list of known Kafka Brokers in the format
host:portSupports Expression Language: true (will
be evaluated using variable registry only)Security ProtocolPLAINTEXTPLAINTEXT
SSL SASL_PLAINTEXT SASL_SSL Protocol used to
communicate with brokers. Corresponds to Kafka's 'security.protocol'
property.Kerberos Credentials ServiceController Service
API: KerberosCredentialsServiceImplementation:
KeytabCredentialsServiceSpecifies the Kerberos Credentials Controller Service that
should be used for authenticating with KerberosKerberos Service NameThe Kerberos principal name
that Kafka runs as. This can be defined either in Kafka's JAAS config
or in Kafka's config. Corresponds to Kafka's 'security.protocol' property.It
is ignored unless one of the SASL options of the Security Protocol are
selected.Supports Expression Language: true (will be evaluated
using variable registry only)Kerberos
PrincipalThe Kerberos principal that will be used to connect to
brokers. If not set, it is expected to set a JAAS configuration file in the JVM
properties defined in the bootstrap.conf file. This principal will be set into
'sasl.jaas.config' Kafka's property.Supports Expression Language:
true (will be evaluated using variable registry only)Kerberos KeytabThe Kerberos keytab that will
be used to connect to brokers. If not set, it is expected to set a JAAS
configurati
on file in the JVM properties defined in the bootstrap.conf file. This
principal will be set into 'sasl.jaas.config' Kafka's
property.Supports Expression Language: true (will be evaluated
using variable registry only)SSL Context
ServiceController Service API:
SSLContextServiceImplementations: StandardRestrictedSSLContextServiceStandardSSLContextServiceSpecifies the SSL Context Service to use for communicating
with Kafka.Topic Name(s)The
na
me of the Kafka Topic(s) to pull from. More than one can be supplied if comma
separated.Supports Expression Language: true (will be evaluated
using variable registry only)Topic
Name Formatnamesnames pattern Specifies whether the
Topic(s) provided are a comma separated list of names or a single regular
expressionHonor
Transactionstruetruefa
lseSpecifies whether or not NiFi should
honor transactional guarantees when communicating with Kafka. If false, the
Processor will use an "isolation level" of read_uncomitted. This means that
messages will be received as soon as they are written to Kafka but will be
pulled, even if the producer cancels the transactions. If this value is true,
NiFi will not receive any messages for which the producer's transaction was
canceled, but this can result in some latency since the consumer must wait for
the producer to finish its entire transaction instead of pulling as the
messages become available.Group
IDA Group ID is used to identify consumers that are within the
same consumer group. Corresponds to Kafka's 'group.id'
property.Offset Resetlatestearliest latest none Allows you to manage the
condition when there is no initial offset in Kafka or if the current offset
does not exist any more on the server (e.g. because that data has been
deleted). Corresponds to Kafka's 'auto.offset.reset' property.Key Attribute Encodin
gutf-8UTF-8 Encoded Hex Encoded FlowFiles that are emitted
have an attribute named 'kafka.key'. This property dictates how the value of
the attribute should be encoded.Message
DemarcatorSince
svn commit: r1834461 [22/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-record-serialization-services-nar/1.7.0/org.apache.nifi.text.FreeFormTextRecordSetWriter/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-record-serialization-services-nar/1.7.0/org.apache.nifi.text.FreeFormTextRecordSetWriter/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-record-serialization-services-nar/1.7.0/org.apache.nifi.text.FreeFormTextRecordSetWriter/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-record-serialization-services-nar/1.7.0/org.apache.nifi.text.FreeFormTextRecordSetWriter/index.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1 @@
+FreeFormTextRecordSetWriterwindow.onload =
function(){if(self==top) { document.getElementById('nameHeader').style.display
= "inherit"; } }FreeFormTextRecordSetWriterDescription: Writes the
contents of a RecordSet as free-form text. The configured text is able to make
use of the Expression Language to reference each of the fields that are
available in a Record. Each record in the RecordSet will be separated by a
single newline character.Tags: text, freeform, expression,
language, el, record, recordset, resultset, writer,
serializeProperties: In the list below, the names of required
properties appear in bold. Any other properties (not in bold)
are consider
ed optional. The table also indicates any default values, and whether a
property supports the NiFi Expression
Language.NameDefault
ValueAllowable ValuesDescriptionTextThe text to use when writing
the results. This property will evaluate the Expression Language using any of
the fields available in a Record.Supports Expression Language:
true (will be evaluated using flow file attributes and variable
registry)Character
SetUTF-8The Character set to use when
writing the data to the FlowFileState management:
This component does not store state.Restricted: <
/h3>This component is not restricted.System Resource
Considerations:None specified.
\ No newline at end of file
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-record-serialization-services-nar/1.7.0/org.apache.nifi.xml.XMLReader/additionalDetails.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-record-serialization-services-nar/1.7.0/org.apache.nifi.xml.XMLReader/additionalDetails.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-record-serialization-services-nar/1.7.0/org.apache.nifi.xml.XMLReader/additionalDetails.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-record-serialization-services-nar/1.7.0/org.apache.nifi.xml.XMLReader/additionalDetails.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1,433 @@
+
+
+
+
+
+XMLReader
+
+
+
+
+
+The XMLReader Controller Service reads XML content and creates Record
objects. The Controller Service
+must be configured with a schema that describes the structure of the
XML data. Fields in the XML data
+that are not defined in the schema will be skipped. Depending on
whether the property "Expect Records as Array"
+is set to "false" or "true", the reader either expects a single record
or an array of records for each FlowFile.
+
+
+Example: Single record
+
+
+
+record
+ field1content/field1
+ field2content/field2
+/record
+
+
+
+
+An array of records has to be enclosed by a root tag.
+Example: Array of records
+
+
+
+
+root
+ record
+field1content/field1
+field2content/field2
+ /record
+ record
+field1content/field1
+field2content/field2
+ /record
+/root
+
+
+
+Example: Simple Fields
+
+
+The simplest kind of data within XML data are tags / fields only
containing content (no attributes, no embedded tags).
+They can be described in the schema by simple types (e. g. INT,
STRING, ...).
+
+
+
+
+root
+ record
+simple_fieldcontent/simple_field
+ /record
+/root
+
+
+
+
+This record can be described by a schema containing one field (e. g.
of type string). By providing this schema,
+the reader expects zero or one occurrences of "simple_field" in the
record.
+
+
+
+
+{
+
svn commit: r1834461 [3/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache.
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-aws-nar/1.7.0/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/nifi-aws-nar/1.7.0/org.apache.nifi.processors.aws.dynamodb.PutDynamoDB/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-aws-nar/1.7.0/org.apache.nifi.processors.aws.dynamodb.PutDynamoDB/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-aws-nar/1.7.0/org.apache.nifi.processors.aws.dynamodb.PutDynamoDB/index.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1 @@
+PutDynamoDBwindow.onload =
function(){if(self==top) { document.getElementById('nameHeader').style.display
= "inherit"; } }PutDynamoDBDescription: 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.Tags:
Amazon, DynamoDB, AWS, Put, InsertProperties: In the
list below, the names of required properties appear in bold. Any other properties (not in bold) are considered optional. The table also
>indicates any default values, whether a property supports the href="../../../../../html/expression-language-guide.html">NiFi Expression
>Language, 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 nifi.properties file has an entry for the
>property nifi.sensitive.props.key.id="properties">NameDefault ValueAllowable
>ValuesDescriptionTable
>Nameid="allowable-values">The DynamoDB table
>nameSupports Expression Language: true (will be evaluated using
>variable registry only)Hash Key
>Nameid="allowable-values">The hash key name of the itemSupports
Expression Language: true (will be evaluated using variable registry
only)Range Key NameThe
range key name of the itemSupports Expression Language: true (will
be evaluated using variable registry only)Hash Key Value${dynamodb.item.hash.key.value}The hash key value of the
itemSupports Expression Language: true (will be evaluated using
flow file attributes and variable registry)Range Key Value${dynamodb.item.range.key.value}No Description
Provided.Supports Expression Language: true (will be evaluated us
ing flow file attributes and variable registry)Hash Key Value TypestringstringnumberThe hash key value type of the itemRange Key Value TypestringstringnumberThe range key value type of the itemJson Document attributeThe
Json document to be retrieved from the dynamodb itemSupports
Expression Language: true (will be evaluated using variable registry
only)Character set of
documentUTF-8Charact
er set of data in the documentSupports Expression Language: true
(will be evaluated using variable registry only)Batch items for each request (between 1 and 50)1The items to be retrieved in one batchSupports
Expression Language: true (will be evaluated using variable registry
only)Regionus-west-2AWS GovCloud
(US)US East (N. Virginia)US East (Ohio)US West (N.
California)US West (Oregon)EU (Ireland)EU
(London)EU (Paris)EU (Frankfurt)Asia Pacific
(Mumbai)Asia Pacific (Singapore)Asia Pacific
(Sydney)Asia Pacific (Tokyo)Asia Pacific
(Seoul)South America (Sao Paulo)China (Beijing)Chi
na (Ningxia)Canada (Central)No
Description Provided.Access KeyNo
Description Provided.Sensitive Property:
trueSupports Expression Language: true (will be evaluated
using variable registry only)Secret
KeyNo Description Provided.Sensitive Property:
trueSupports Expression Language: true (will be evaluated
using variable registry only)Credentials
FilePath to a file containing AWS access key and secret key in
properties file format.AWS Credentials Provider
service
Controller Service API:
AWSCredentialsProviderServiceImplementation:
AWSCredentialsProviderControllerServiceThe Controller Service that is used to obtain aws credentials
providerCommunications
Timeout30 secsNo Description
Provided.SSL Context ServiceController Service
API: SSLContextServiceImplementations: StandardRestrictedSSLContextServiceStandardSSLContextServiceSpecifies an optional SSL Context Service that, if provided,
will be used to create connectionsProxy
Configuration ServiceController Service API:
ProxyConfigurationServiceImplementation: StandardProxyConfigurationServiceSpecifies the Proxy Configuration Controller Service to proxy
network requests. If set, it supersedes proxy settings configured per
component. Supported proxies: HTTP + AuthNProxy
HostProxy host name or IPSupports Expression
svn commit: r1834461 [12/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hive-nar/1.7.0/org.apache.nifi.dbcp.hive.HiveConnectionPool/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hive-nar/1.7.0/org.apache.nifi.dbcp.hive.HiveConnectionPool/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hive-nar/1.7.0/org.apache.nifi.dbcp.hive.HiveConnectionPool/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hive-nar/1.7.0/org.apache.nifi.dbcp.hive.HiveConnectionPool/index.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1 @@
+HiveConnectionPoolwindow.onload =
function(){if(self==top) { document.getElementById('nameHeader').style.display
= "inherit"; } }HiveConnectionPoolDescription: Provides Database
Connection Pooling Service for Apache Hive. Connections can be asked from pool
and returned after usage.Tags: hive, dbcp, jdbc, database,
connection, pooling, storeProperties: In the list below, the
names of required properties appear in bold. Any other
properties (not in bold) are considered optional. The table also indicates any
default values, whether a property supports the NiFi Expression
Language, 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
nifi.properties file has an entry for the property
nifi.sensitive.props.key.NameDefault ValueAllowable
ValuesDescriptionDatabase
Connection URLA 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.Supports Expression Language: true (will be evaluated using
variable registry only)Hive Con
figuration ResourcesA 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 see the Hive documentation for more details.Supports
Expression Language: true (will be evaluated using variable registry
only)Database UserDatabase user nameSupports Expression Language:
true (will be evaluated using variable registry only)PasswordThe password for the datab
ase userSensitive Property: trueSupports
Expression Language: true (will be evaluated using variable registry
only)Max Wait
Time500 millisThe 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.
Supports Expression Language: true (will be evaluated using
variable registry only)Max Total
Connections8The maximum number of active
connections that can be allocated from this pool at the same time, or negative
for no limit.Supports Expression Language: true (will be evaluated
using variable registry only)Vali
dation queryValidation query used to
validate connections before returning them. When a borrowed connection is
invalid, it gets dropped and a new valid connection will be returned. NOTE:
Using validation may have a performance penalty.Supports
Expression Language: true (will be evaluated using variable registry
only)Kerberos Credentials ServiceController Service
API: KerberosCredentialsServiceImplementation:
KeytabCredentialsServiceSpecifies the Kerberos Credentials Controller Service that
should be used for authenticating with KerberosKerberos PrincipalKerberos
principal to authenticate as. Requires nifi.kerberos.krb5.file to be set in
your nifi.propertiesSupports Expression Language: true (will be
evaluated using variable registry only)Kerberos KeytabKerberos keytab associated with
the principal. Requires nifi.kerberos.krb5.file to be set in your
nifi.propertiesSupports Expression Language: true (will be
evaluated using variable registry only)State
management: This component does not store state.Restricted: This
component is not restricted.System Resource Considerations:None
specified.
\ No newline at end of file
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hive-nar/1.7.0/org.apache.nifi.processors.hive.ConvertAvroToORC/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hive-nar/1.7.0/org.apache.nifi.processors.hive.ConvertAvroToORC/index.html?rev=1834461=auto
==
---
svn commit: r1834461 [32/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.MergeContent/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.MergeContent/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.MergeContent/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.MergeContent/index.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1 @@
+MergeContentwindow.onload =
function(){if(self==top) { document.getElementById('nameHeader').style.display
= "inherit"; } }MergeContentDescription: Merges a Group of FlowFiles
together based on a user-defined strategy and packages them into a single
FlowFile. It is recommended that the Processor be configured with only a single
incoming connection, as Group of FlowFiles will not be created from FlowFiles
in different connections. This processor updates the mime.type attribute as
appropriate.Tags: merge, content, correlation, tar, zip,
stream, concatenation, archive, flowfile-stream,
flowfile-stream-v3Properties: In the list below, the names of
required properties appear
in bold. Any other properties (not in bold) are considered
optional. The table also indicates any default values, and whether a property
supports the NiFi
Expression Language.NameDefault
ValueAllowable ValuesDescriptionMerge StrategyBin-Packing AlgorithmBin-Packing Algorithm Defragment Specifies the algorithm used to merge content. The
'Defragment' algorithm combines fragments that are associated by attributes
back into a single cohesive FlowFile. The 'Bin-Packing Algorithm' generates a
FlowFile populated by arbitrarily chosen FlowFilesMerge FormatBinary
ConcatenationTAR ZIP FlowFile Stream, v3 FlowFile Stream, v2 FlowFile Tar, v1 Binary Concatenation Avro Determines the format that will be used
to merge the content.Attribute
StrategyKeep Only Common
AttributesKeep Only Common Attributes
Keep All Unique Attributes Determines which FlowFile
attributes should be added to the bundle. If 'Keep All Unique Attributes' is
selected, any attribute on any FlowFile that gets bundled will be kept unless
its value conflicts with the value from another FlowFile. If 'Keep Only Common
Attributes' is selected, only the attributes that exist on all FlowFiles in the
bundle, with the same value, will be preserved.Correlation Attribute NameIf specified, like FlowFiles will be binned
together, where 'like FlowFiles' means FlowFiles that have the same value for
this Attribute. If not specified, FlowFiles are bundled by the order in which
they are pulled from the queue.Supports Expression Language: true
(will be evaluated using flow file attributes and variable
registry)Metadata
StrategyDo Not Merge Uncommon
MetadataUse First Metadata Keep Only Common Metadata Do Not Merge Uncommon
Metadata Ignore Metadata For FlowFiles whose input format supports metadata (Avro,
e.g.), this property determines which metadata should be added to the bundle.
If 'Use First Metadata' is selected, the metadata keys/values from the first
FlowFile to be bundled will be used. If 'Keep Only Common Metadata' is
selected, only the metadata that exists on all FlowFiles in the bundle, with
the same value, will be preserved. If 'Ignore Metadata' is selected, no
metadata is transferred to the outgoing bundled FlowFile. If 'Do Not Merge
Uncommon Metadata' is selected, any FlowFi
le whose metadata values do not match those of the first bundled FlowFile will
not be merged.Minimum Number of
Entries1The minimum number of files to
include in a bundleMaximum Number of
Entries1000The maximum number of files to
include in a bundleMinimum Group
Size0 BThe minimum size of for the
bundleMaximum Group SizeThe
maximum size for the bundle. If not specified, there is no
maximum.Max Bin AgeThe maximum age of a Bin that will trigger a Bin to be
>complete. Expected format is duration time unit where
>duration is a positive integer and time unit is one of seconds,
>minutes, hoursMaximum number of
>Bins5id="allowable-values">Specifies the maximum number
>of bins that can be held in memory at any one timeid="name">Delimiter Strategyid="default-value">FilenameFilename
>title="The values of Header, Footer, and Demarcator will be retrieved from
>the contents of a file">Text src="../../../../../html/images/iconInfo.png" alt="The values of Header,
>Footer, and Demarcator will be specified
as property values" title="The values of Header, Footer, and Demarcator will
be specified as property values">Determines if Header, Footer, and Demarcator should point to
files containing the respective content,
svn commit: r1834461 [16/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-9-nar/1.7.0/org.apache.nifi.processors.kafka.pubsub.ConsumeKafka/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-9-nar/1.7.0/org.apache.nifi.processors.kafka.pubsub.ConsumeKafka/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-9-nar/1.7.0/org.apache.nifi.processors.kafka.pubsub.ConsumeKafka/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-0-9-nar/1.7.0/org.apache.nifi.processors.kafka.pubsub.ConsumeKafka/index.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1 @@
+ConsumeKafkawindow.onload =
function(){if(self==top) { document.getElementById('nameHeader').style.display
= "inherit"; } }ConsumeKafkaDescription: Consumes messages from Apache
Kafka specifically built against the Kafka 0.9.x Consumer API. Please note
there are cases where the publisher can get into an indefinite stuck state. We
are closely monitoring how this evolves in the Kafka community and will take
advantage of those fixes as soon as we can. In the mean time it is possible to
enter states where the only resolution will be to restart the JVM NiFi runs on.
The complementary NiFi processor for sending messages is PublishKafka.Additional Details...<
h3>Tags: Kafka, Get, Ingest, Ingress, Topic, PubSub, Consume,
0.9.xProperties: In the list below, the names of required
properties appear in bold. Any other properties (not in bold)
are considered optional. The table also indicates any default values, and
whether a property supports the NiFi Expression
Language.NameDefault
ValueAllowable ValuesDescriptionKafka Brokerslocalhost:9092A comma-separated list of known Kafka Brokers in the format
host:portSupports Expression Language: true (will
be evaluated using variable registry only)Security ProtocolPLAINTEXTPLAINTEXT SSL SASL_PLAINTEXT SASL_SSL Protocol used to
communicate with brokers. Corresponds to Kafka's 'security.protocol'
property.Kerberos Service NameThe
Kerberos principal name that Kafka runs as. This can be defined either in
Kafka's JAAS config or in Kafka's config. Corresponds to Kafka's
'security.protocol' property.It is ignored unless one of the SASL options of
the Security Protocol are selected.SSL
Context ServiceController Service API:
SSLContextServiceImplementations: StandardRestrictedSSLContextServiceStandardSSLContextServiceSpecifies the SSL Context Service to use for communicating
with Kafka.Topic Name(s)The
name of the Kafka Topic(s) to pull from. More than one can be supplied if comma
separated.Supports Expression Language: true (will be evaluated
using variable registry only)Group
IDA Group ID is
used to identify consumers that are within the same consumer group. Corresponds
to Kafka's 'group.id' property.Offset
Resetlatestearliest latest none Allow
s you to manage the condition when there is no initial offset in Kafka or if
the current offset does not exist any more on the server (e.g. because that
data has been deleted). Corresponds to Kafka's 'auto.offset.reset'
property.Key Attribute
Encodingutf-8UTF-8 Encoded Hex Encoded FlowFiles that are emitted
have an attribute named 'kafka.key'. This property dictates
how the value of the attribute should be encoded.Message DemarcatorSince KafkaConsumer receives
messages in batches, you have an option to output FlowFiles which contains all
Kafka messages in a single batch for a given topic and partition and this
property allows you to provide a string (interpreted as UTF-8) to use for
demarcating apart multiple Kafka messages. This is an optional property and if
not provided each Kafka message received will result in a single FlowFile which
time it is triggered. To enter special character such as 'new line' use
CTRL+Enter or Shift+Enter depending on the OSSupports Expression
Language: true (will be evaluated using variable registry
only)Max Poll Records1Specifies the maximum number of records Kafk
a should return in a single poll.Max Uncommitted
Time1 secsSpecifies the maximum amount of time allowed to pass before
offsets must be committed. This value impacts how often offsets will be
committed. Committing offsets less often increases throughput but also
increases the window of potential data duplication in the event of a rebalance
or JVM restart between commits. This value is also related to maximum poll
records and the use of a message demarcator. When using a message demarcator
we can have far more uncommitted messages than when we're not as there is much
less for us to keep track of in memory.Dynamic
Properties: Dynamic Properties allow the user to specify both the name
and value of a property.NameValueDescriptionThe name of a Kafka configuratio
n property.The value of a given Kafka
svn commit: r1834461 [5/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache.
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-azure-nar/1.7.0/org.apache.nifi.processors.azure.storage.PutAzureBlobStorage/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-azure-nar/1.7.0/org.apache.nifi.processors.azure.storage.PutAzureBlobStorage/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-azure-nar/1.7.0/org.apache.nifi.processors.azure.storage.PutAzureBlobStorage/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-azure-nar/1.7.0/org.apache.nifi.processors.azure.storage.PutAzureBlobStorage/index.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1 @@
+PutAzureBlobStoragewindow.onload =
function(){if(self==top) { document.getElementById('nameHeader').style.display
= "inherit"; } }PutAzureBlobStorageDescription: Puts content into an
Azure Storage BlobTags: azure, microsoft, cloud, storage,
blobProperties: In the list below, the names of required
properties appear in bold. Any other properties (not in bold)
are considered optional. The table also indicates any default values, whether a
property supports the NiFi Expression
Language, 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
nifi.properties file has an entry for the property
nifi.sensitive.props.key.NameDefault ValueAllowable
ValuesDescriptionContainer
NameName of the Azure storage
containerSupports Expression Language: true (will be evaluated
using flow file attributes and variable registry)SAS TokenShared Access Signature token,
including the leading '?'. Specify either SAS Token (recommended) or Account
Key. There are certain risks in allowing the SAS token to be stored as a
flowfile attribute. While it does provide for a more flexible flow by allowing
the account name to be fetched dynamically from
a flowfile attribute, care must be taken to restrict access to the event
provenance data (e.g. by strictly controlling the policies governing provenance
for this Processor). In addition, the provenance repositories may be put on
encrypted disk partitions.Sensitive Property:
trueSupports Expression Language: true (will be evaluated
using flow file attributes and variable registry)Storage Account NameThe
storage account name. There are certain risks in allowing the account name to
be stored as a flowfile attribute. While it does provide for a more flexible
flow by allowing the account name to be fetched dynamically from a flowfile
attribute, care must be taken to restrict access to the event provenance data
(e.g. by strictly controlling the policies governing provenance for this
Processor). In addition, the prov
enance repositories may be put on encrypted disk
partitions.Sensitive Property: trueSupports
Expression Language: true (will be evaluated using flow file attributes and
variable registry)Storage Account
KeyThe storage account key. This is an admin-like password
providing access to every container in this account. It is recommended one uses
Shared Access Signature (SAS) token instead for fine-grained control with
policies. There are certain risks in allowing the account key to be stored as a
flowfile attribute. While it does provide for a more flexible flow by allowing
the account key to be fetched dynamically from a flow file attribute, care must
be taken to restrict access to the event provenance data (e.g. by strictly
controlling the policies governing provenance for this Processor). In addition,
the provenance repositories ma
y be put on encrypted disk partitions.Sensitive Property:
trueSupports Expression Language: true (will be evaluated
using flow file attributes and variable registry)Blob${azure.blobname}The filename of the blobSupports Expression
Language: true (will be evaluated using flow file attributes and variable
registry)Proxy Configuration
ServiceController Service API:
ProxyConfigurationServiceImplementation: StandardProxyConfigurationServiceSpecifies the Proxy Configuration Controller Service to proxy
network requests. S
upported proxies: HTTP, SOCKSRelationships: NameDescriptionsuccessAll
successfully processed FlowFiles are routed to this
relationshipfailureUnsuccessful operations will be
transferred to the failure relationship.Reads Attributes:
None specified.Writes Attributes: NameDescriptionazure.containerThe
name of the Azure containerazure.blobnameThe name
of the Azure blobazure.primaryUriPrimary location
for blob contentazure.etagEtag for the Azure
blobazure.lengthLength of the
blobazure.timestampThe timestamp in Azure for the
blobState management: This component does not store
state.Restricted: This component is not restricted.Input requirement: This component
requires an incoming relationship.System
svn commit: r1834461 [36/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.UpdateRecord/additionalDetails.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.UpdateRecord/additionalDetails.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.UpdateRecord/additionalDetails.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.UpdateRecord/additionalDetails.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1,390 @@
+
+
+
+
+
+UpdateRecord
+
+
+
+
+
+
+ UpdateRecord makes use of the NiFi
+ RecordPath Domain-Specific Language (DSL) to allow the user
+ to indicate which field(s) in the Record should be updated.
Users do this by adding a User-defined
+ Property to the Processor's configuration. The name of the
User-defined Property must be the
+ RecordPath text that should be evaluated against each Record.
The value of the Property specifies
+ what value should go into that selected Record field.
+
+
+
+ When specifying the replacement value (the value of the
User-defined Property), the user is able
+ to specify a literal value such as the number 10;
an Expression Language Expression
+ to reference FlowFile attributes, such as
${filename}; or another RecordPath path
+ from which to retrieve the desired value from the Record
itself. Whether the value entered should
+ be interpreted as a literal or a RecordPath path is determined
by the value of the Replacement
+ Value Strategy Property.
+
+
+
+ If a RecordPath is given and does not match any field in an
input Record, that Property will be skipped
+ and all other Properties will still be evaluated. If the
RecordPath matches exactly one field, that field
+ will be updated with the corresponding value. If multiple
fields match the RecordPath, then all fields that
+ match will be updated. If the replacement value is itself a
RecordPath that does not match, then a
+ null value will be set for the field. For
instances where this is not the desired behavior,
+ RecordPath predicates can be used to filter the fields that
match so that no fields will be selected.
+ See RecordPath
Predicates for more information.
+
+
+
+ Below, we lay out some examples in order to provide clarity
about the Processor's behavior. For all of
+ the examples below, consider the example to operate on the
following set of 2 (JSON) records:
+
+
+
+
+ [{
+"id": 17,
+"name": "John",
+"child": {
+"id": "1"
+},
+"siblingIds": [4, 8],
+"siblings": [
+{ "name": "Jeremy", "id": 4 },
+{ "name": "Julia", "id": 8 }
+]
+ },
+ {
+"id": 98,
+"name": "Jane",
+"child": {
+"id": 2
+},
+"gender": "F",
+"siblingIds": [],
+"siblings": []
+ }]
+
+
+
+
+ For brevity, we will omit the corresponding schema and
configuration of the RecordReader and
+ RecordWriter. Otherwise, consider the following set of
Properties are configured for the Processor
+ and their associated outputs.
+
+
+ Example 1 - Replace with Literal
+
+
+ Here, we will replace the name of each Record with the
name 'Jeremy' and set the gender to 'M':
+
+
+
+
+ Property Name
+ Property Value
+
+
+ Replacement Value Strategy
+ Literal Value
+
+
+ /name
+ Jeremy
+
+
+ /gender
+ M
+
+
+
+
+ This will yield the following output:
+
+
+
+
+ [{
+"id": 17,
+"name": "Jeremy",
+"child": {
+"id": "1"
+},
+"gender": "M",
+"siblingIds": [4, 8],
+"siblings": [
+{ "name": "Jeremy", "id": 4 },
+{ "name": "Julia", "id": 8 }
+]
+ },
+ {
+"id": 98,
+"name":
svn commit: r1834461 [10/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hadoop-nar/1.7.0/org.apache.nifi.processors.hadoop.FetchHDFS/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hadoop-nar/1.7.0/org.apache.nifi.processors.hadoop.FetchHDFS/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hadoop-nar/1.7.0/org.apache.nifi.processors.hadoop.FetchHDFS/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hadoop-nar/1.7.0/org.apache.nifi.processors.hadoop.FetchHDFS/index.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1,3 @@
+FetchHDFSwindow.onload =
function(){if(self==top) { document.getElementById('nameHeader').style.display
= "inherit"; } }FetchHDFSDescription: Retrieves a file from HDFS. The
content of the incoming FlowFile is replaced by the content of the file in
HDFS. The file in HDFS is left intact without any changes being made to
it.Tags: hadoop, hdfs, get, ingest, fetch,
sourceProperties: In the list below, the names of required
properties appear in bold. Any other properties (not in bold)
are considered optional. The table also indicates any default values, and
whether a property supports the NiFi Expre
ssion Language.NameDefault
ValueAllowable ValuesDescriptionHadoop Configuration ResourcesA file or comma separated list
of files which contains the Hadoop file system configuration. Without this,
Hadoop will search the classpath for a 'core-site.xml' and 'hdfs-site.xml' file
or will revert to a default configuration. To use swebhdfs, see 'Additional
Details' section of PutHDFS's documentation.Supports Expression
Language: true (will be evaluated using variable registry
only)Kerberos Credentials ServiceController Service
API: KerberosCredentialsServiceImplementation:
KeytabCredentialsServiceSpecifies the Kerberos Credentials Controller Service that
should be used for authenticating with KerberosKerberos PrincipalKerberos principal to
authenticate as. Requires nifi.kerberos.krb5.file to be set in your
nifi.propertiesSupports Expression Language: true (will be
evaluated using variable registry only)Kerberos KeytabKerberos keytab associated with
the principal. Requires nifi.kerberos.krb5.file to be set in your
nifi.propertiesSupports Expression Language: true (will be
evaluated using variable registry only)Kerberos Relogin Period4 hours<
/td>Period of time which should pass before attempting a
kerberos relogin.
+
+This property has been deprecated, and has no effect on processing. Relogins
now occur automatically.Supports Expression Language: true (will
be evaluated using variable registry only)Additional Classpath ResourcesA comma-separated list of paths
to files and/or directories that will be added to the classpath. When
specifying a directory, all files with in the directory will be added to the
classpath, but further sub-directories will not be included.HDFS Filename${path}/${filename}The name of the HDFS file to retrieveSupports
Expression Language: true (will be evaluated using flow file attributes and
variable registry)Compression
codecNONENONE DEFAULT BZIP GZIP LZ4 LZO SNAPPY AUTOMATIC No Description Provided.Relationships:
NameDescriptionsuccessFlowFiles
will be routed to this relationship once they have been updated with the
content of the HDFS filecomms.failureFlowFiles will
be routed to this relationship if the content of the HDFS file cannot be
retrieve due to a communications failure. This generally indicates that the
Fetch should be tried again.failureFlowFiles will be
routed to this relationship if the content of the HDFS file cannot be retrieved
and trying again will likely not be helpful. This would occur, for instance, if
the file is not found or i
f there is a permissions issueReads Attributes:
None specified.Writes Attributes: NameDescriptionhdfs.failure.reasonWhen
a FlowFile is routed to 'failure', this attribute is added indicating why the
file could not be fetched from HDFSState management:
This component does not store state.Restricted: Required
PermissionExplanationread
filesystemProvides operator the ability to retrieve any file that NiFi
has access to in HDFS or the local filesystem.Input
requirement: This component requires an incoming relationship.System
Resource Considerations:None specified.See Also:ListHDFS,
GetHDFS,
PutHDFS
\ No newline at end of file
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hadoop-nar/1.7.0/org.apache.nifi.processors.hadoop.GetHDFS/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hadoop-nar/1.7.0/org.apache.nifi.processors.hadoop.GetHDFS/index.html?rev=1834461=auto
==
---
svn commit: r1834461 [18/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-livy-nar/1.7.0/org.apache.nifi.controller.livy.LivySessionController/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-livy-nar/1.7.0/org.apache.nifi.controller.livy.LivySessionController/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-livy-nar/1.7.0/org.apache.nifi.controller.livy.LivySessionController/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-livy-nar/1.7.0/org.apache.nifi.controller.livy.LivySessionController/index.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1 @@
+LivySessionControllerwindow.onload =
function(){if(self==top) { document.getElementById('nameHeader').style.display
= "inherit"; } }LivySessionControllerDescription: Manages pool of Spark
sessions over HTTPTags: Livy, REST, Spark,
httpProperties: In the list below, the names of required
properties appear in bold. Any other properties (not in bold)
are considered optional. The table also indicates any default values, and
whether a property supports the NiFi Expression
Language.NameDefault
ValueAllowable ValuesDescription
Livy HostThe
hostname (or IP address) of the Livy server.Supports Expression
Language: true (will be evaluated using variable registry
only)Livy Port8998The port number for the Livy server.Supports
Expression Language: true (will be evaluated using variable registry
only)Session Pool
Size2Number of sessions to keep
openSupports Expression Language: true (will be evaluated using
variable registry only)Session
Typesparksparkpysp
arkpyspark3sparkrThe
type of Spark session to start (spark, pyspark, pyspark3, sparkr,
e.g.)Session Manager Status
Interval2 secThe amount of time to wait
between requesting session information updates.Supports Expression
Language: true (will be evaluated using variable registry
only)SSL Context ServiceController Service
API: SSLContextServiceImplementations: StandardRestrictedSSLContextServiceStandardSSLContextServ
iceThe SSL Context Service used to provide
client certificate information for TLS/SSL (https)
connections.Connection
Timeout5 secsMax wait time for connection to
remote service.Session JARsJARs to be used in the Spark session.Supports
Expression Language: true (will be evaluated using variable registry
only)Session FilesFiles to be used in the Spark session.Supports
Expression Language: true (will be evaluated using variable registry
only)Kerberos Credentials ServiceC
ontroller Service API:
KerberosCredentialsServiceImplementation:
KeytabCredentialsServiceSpecifies the Kerberos Credentials Controller Service that
should be used for authenticating with KerberosState
management: This component does not store state.Restricted: This
component is not restricted.System Resource Considerations:None
specified.
\ No newline at end of file
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-livy-nar/1.7.0/org.apache.nifi.processors.livy.ExecuteSparkInteractive/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-livy-nar/1.7.0/org.apache.nifi.processors.livy.ExecuteSparkInteractive/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-livy-nar/1.7.0/org.apache.nifi.processors.livy.ExecuteSparkInteractive/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-livy-nar/1.7.0/org.apache.nifi.processors.livy.ExecuteSparkInteractive/index.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1 @@
+ExecuteSparkInteractivewindow.onload =
function(){if(self==top) { document.getElementById('nameHeader').style.display
= "inherit"; } }ExecuteSparkInteractiveDescription: Execute Spark Code
over a Livy-managed HTTP session to a live Spark context. Supports cached RDD
sharing.Tags: spark, livy, http, executeProperties:
In the list below, the names of required properties appear in
bold. Any other properties (not in bold) are considered
optional. The table also indicates any default values, and whether a property
supports the NiFi
Expression Language.Name
Default ValueAllowable
ValuesDescriptionLivy Controller
ServiceController Service API:
LivySessionServiceImplementation: LivySessionControllerThe controller service to use for Livy-managed
session(s).CodeThe code to execute in the
session. This property can be empty, a constant value, or built from attributes
using Expression Language. If this property is specified, it will be used
regardless of the content of incoming flowfiles. If this property is empty, the
content of the incoming flow file is expected to contain valid code to be
issued by the processor to the session. Note that Expression Langua
svn commit: r1834461 [17/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-1-0-nar/1.7.0/org.apache.nifi.processors.kafka.pubsub.PublishKafkaRecord_1_0/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-1-0-nar/1.7.0/org.apache.nifi.processors.kafka.pubsub.PublishKafkaRecord_1_0/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-1-0-nar/1.7.0/org.apache.nifi.processors.kafka.pubsub.PublishKafkaRecord_1_0/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-kafka-1-0-nar/1.7.0/org.apache.nifi.processors.kafka.pubsub.PublishKafkaRecord_1_0/index.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1 @@
+PublishKafkaRecord_1_0window.onload =
function(){if(self==top) { document.getElementById('nameHeader').style.display
= "inherit"; } }PublishKafkaRecord_1_0Description: Sends the contents
of a FlowFile as individual records to Apache Kafka using the Kafka 1.0
Producer API. The contents of the FlowFile are expected to be record-oriented
data that can be read by the configured Record Reader. The complementary NiFi
processor for fetching messages is ConsumeKafkaRecord_1_0.Additional Details...Tags:
Apache, Kafka, Record, csv, json, avro, logs, Put, Send, Message,
PubSub, 1.0Properties: In the list below, the names of required
prope
rties appear in bold. Any other properties (not in bold) are
considered optional. The table also indicates any default values, and whether a
property supports the NiFi Expression
Language.NameDefault
ValueAllowable ValuesDescriptionKafka Brokerslocalhost:9092A comma-separated list of known Kafka Brokers in the format
host:portSupports Expression Language: true (will
be evaluated using variable registry only)Topic NameThe name of the Kafka Topic to
publish to.Supports Expression Language: true (will be evaluated
using flow file attribute
s and variable registry)Record
ReaderController Service API:
RecordReaderFactoryImplementations: ScriptedReaderGrokReaderJsonPathReaderJsonTreeReaderAvroReaderXMLReaderCSVReaderThe Record Reader to use for incoming
FlowFilesRecord WriterController Service
API: RecordSetWriterFactoryImplementations:
AvroRecordSetWriterCSVRecordSetWriterFreeFormTextRecordSetWriterJsonRecordSetWriterScriptedRecordSetWriterXMLRecordSetWriterThe Record Writer to use in order to serialize the data
before sending to KafkaUse
TransactionstruetruefalseSpecifies whether or not NiFi should provide Transactional
guarantees when communicating with Kafka. If there is a problem sending data to
Kafka, and this property is set to false, then the messages that have already
been sent to Kafka will continue on and be delivered to consumers. If this is
set to true, then the Kafka transaction will be rolled back so that those
messages are not available to
consumers. Setting this to true requires that the Delivery Guarantee
property be set to "Guarantee Replicated Delivery."Delivery Guarantee0Best Effort Guarantee Single Node
Delivery Guarantee
Replicated Delivery Specifies the
requirement for guaranteeing that a message is sent to Kafka. Corresponds to
Kafka's 'acks' property.Attributes to Send as
Headers (Regex)A Regu
lar Expression that is matched against all FlowFile attribute names. Any
attribute whose name matches the regex will be added to the Kafka messages as a
Header. If not specified, no FlowFile attributes will be added as
headers.Message Header EncodingUTF-8For any attribute that is added as a message header, as
configured via the Attributes to Send as Headers property, this
property indicates the Character Encoding to use for serializing the
headers.Security ProtocolPLAINTEXTPLAINTEXT
SSL SASL_PLAINTEXT SASL_SSL Protocol used to
communicate with brokers. Corresponds to Kafka's 'security.protocol'
property.Kerberos Credentials ServiceController Service
API: KerberosCredentialsServiceImplementation:
KeytabCredentialsServiceSpecifies the Kerberos Credentials Controller Service that
should be used for authenticating with KerberosKerberos Service NameThe Kerberos principal name
that Kafka runs as. This can be defined either in Kafka'
s JAAS config or in Kafka's config. Corresponds to Kafka's 'security.protocol'
property.It is ignored unless one of the SASL options of the Security
Protocol are selected.Supports Expression Language: true (will
be evaluated using variable registry only)Kerberos PrincipalThe Kerberos principal that
will be used to connect to brokers. If not set, it is expected to set a JAAS
configuration file in the JVM properties defined in the bootstrap.conf file.
This principal will be set into 'sasl.jaas.config' Kafka's
property.Supports Expression Language: true (will be evaluated
using variable registry only)Kerberos
KeytabThe Kerberos keytab that will be used to connect to brokers.
If
svn commit: r1834461 [11/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase-nar/1.7.0/org.apache.nifi.hbase.DeleteHBaseCells/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase-nar/1.7.0/org.apache.nifi.hbase.DeleteHBaseCells/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase-nar/1.7.0/org.apache.nifi.hbase.DeleteHBaseCells/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase-nar/1.7.0/org.apache.nifi.hbase.DeleteHBaseCells/index.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1 @@
+DeleteHBaseCellswindow.onload =
function(){if(self==top) { document.getElementById('nameHeader').style.display
= "inherit"; } }DeleteHBaseCellsDescription: This processor allows the
user to delete individual HBase cells by specifying one or more lines in the
flowfile content that are a sequence composed of row ID, column family, column
qualifier and associated visibility labels if visibility labels are enabled and
in use. A user-defined separator is used to separate each of these pieces of
data on each line, with being the default separator.Additional Details...Tags:
hbase, delete, cell, cells, visibilityProperties: In the
list below, the names of required properties appear in bold.
Any other properties (not in bold) are considered optional. The table also
indicates any default values, and whether a property supports the NiFi Expression
Language.NameDefault
ValueAllowable ValuesDescriptionHBase Client ServiceController Service
API: HBaseClientServiceImplementation: HBase_1_1_2_ClientServiceSpecifies the Controller Service to use for accessing
HBase.Table Name<
td id="description">The name of the HBase Table.Supports
Expression Language: true (will be evaluated using flow file attributes and
variable registry)SeparatorEach line of the flowfile
content is separated into components for building a delete using thisseparator.
It should be something other than a single colon or a comma because these are
values that are associated with columns and visibility labels respectively. To
delete a row with ID xyz, column family abc, column qualifier def and
visibility label PIIPHI, one would specify
xyzabcdefPIIPHI given the default valueSupports
Expression Language: true (will be evaluated using flow file attributes and
variable registry)Relationships: NameDescriptions
uccessA FlowFile is routed to this relationship after it has been
successfully stored in HBasefailureA FlowFile is
routed to this relationship if it cannot be sent to
HBaseReads Attributes: None specified.Writes
Attributes: NameDescriptionerror.lineThe
line number of the error.error.msgThe message
explaining the error.State management: This
component does not store state.Restricted: This component is not
restricted.Input requirement: This component requires an incoming
relationship.System Resource Considerations:None
specified.
\ No newline at end of file
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase-nar/1.7.0/org.apache.nifi.hbase.DeleteHBaseRow/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase-nar/1.7.0/org.apache.nifi.hbase.DeleteHBaseRow/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase-nar/1.7.0/org.apache.nifi.hbase.DeleteHBaseRow/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-hbase-nar/1.7.0/org.apache.nifi.hbase.DeleteHBaseRow/index.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1 @@
+DeleteHBaseRowwindow.onload =
function(){if(self==top) { document.getElementById('nameHeader').style.display
= "inherit"; } }DeleteHBaseRowDescription: Delete HBase records
individually or in batches. The input can be a single row ID in the flowfile
content, one ID per line, row IDs separated by a configurable separator
character (default is a comma). Tags: delete,
hbaseProperties: In the list below, the names of required
properties appear in bold. Any other properties (not in bold)
are considered optional. The table also indicates any default values, and
whether a property supports the NiFi Ex
pression Language.NameDefault
ValueAllowable ValuesDescriptionHBase Client ServiceController Service
API: HBaseClientServiceImplementation: HBase_1_1_2_ClientServiceSpecifies the Controller Service to use for accessing
HBase.Table NameThe
name of the HBase Table.Supports Expression Language: true (will
be evaluated using flow file attributes and variable
registry)Row IdentifierSpecifies the Row ID to use when deleting data into
HBaseSupports Expression Language: true (will be evaluated using
flow file attributes and variable registry)Row ID
svn commit: r1834461 [1/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache.
Author: alopresto Date: Wed Jun 27 00:37:46 2018 New Revision: 1834461 URL: http://svn.apache.org/viewvc?rev=1834461=rev Log: Added 1.7.0 docs to NiFi site. Added: nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache.nifi.reporting.ambari.AmbariReportingTask/ nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache.nifi.reporting.ambari.AmbariReportingTask/additionalDetails.html nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache.nifi.reporting.ambari.AmbariReportingTask/index.html nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-amqp-nar/1.7.0/ nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-amqp-nar/1.7.0/org.apache.nifi.amqp.processors.ConsumeAMQP/ nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-amqp-nar/1.7.0/org.apache.nifi.amqp.processors.ConsumeAMQP/additionalDetails.html nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-amqp-nar/1.7.0/org.apache.nifi.amqp.processors.ConsumeAMQP/index.html nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-amqp-nar/1.7.0/org.apache.nifi.amqp.processors.PublishAMQP/ nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-amqp-nar/1.7.0/org.apache.nifi.amqp.processors.PublishAMQP/additionalDetails.html nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-amqp-nar/1.7.0/org.apache.nifi.amqp.processors.PublishAMQP/index.html nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-avro-nar/1.7.0/ nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-avro-nar/1.7.0/org.apache.nifi.processors.avro.ConvertAvroToJSON/ nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-avro-nar/1.7.0/org.apache.nifi.processors.avro.ConvertAvroToJSON/index.html nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-avro-nar/1.7.0/org.apache.nifi.processors.avro.ExtractAvroMetadata/ nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-avro-nar/1.7.0/org.apache.nifi.processors.avro.ExtractAvroMetadata/index.html nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-avro-nar/1.7.0/org.apache.nifi.processors.avro.SplitAvro/ nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-avro-nar/1.7.0/org.apache.nifi.processors.avro.SplitAvro/index.html nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-aws-nar/1.7.0/ nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-aws-nar/1.7.0/org.apache.nifi.processors.aws.cloudwatch.PutCloudWatchMetric/ nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-aws-nar/1.7.0/org.apache.nifi.processors.aws.cloudwatch.PutCloudWatchMetric/index.html nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-aws-nar/1.7.0/org.apache.nifi.processors.aws.credentials.provider.service.AWSCredentialsProviderControllerService/ nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-aws-nar/1.7.0/org.apache.nifi.processors.aws.credentials.provider.service.AWSCredentialsProviderControllerService/index.html nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-aws-nar/1.7.0/org.apache.nifi.processors.aws.dynamodb.DeleteDynamoDB/ nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-aws-nar/1.7.0/org.apache.nifi.processors.aws.dynamodb.DeleteDynamoDB/index.html nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-aws-nar/1.7.0/org.apache.nifi.processors.aws.dynamodb.GetDynamoDB/ nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-aws-nar/1.7.0/org.apache.nifi.processors.aws.dynamodb.GetDynamoDB/index.html nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-aws-nar/1.7.0/org.apache.nifi.processors.aws.dynamodb.PutDynamoDB/ nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-aws-nar/1.7.0/org.apache.nifi.processors.aws.dynamodb.PutDynamoDB/index.html nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-aws-nar/1.7.0/org.apache.nifi.processors.aws.kinesis.firehose.PutKinesisFirehose/ nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-aws-nar/1.7.0/org.apache.nifi.processors.aws.kinesis.firehose.PutKinesisFirehose/index.html nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-aws-nar/1.7.0/org.apache.nifi.processors.aws.kinesis.stream.PutKinesisStream/ nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-aws-nar/1.7.0/org.apache.nifi.processors.aws.kinesis.stream.PutKinesisStream/index.html nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-aws-nar/1.7.0/org.apache.nifi.processors.aws.lambda.PutLambda/
svn commit: r1834461 [6/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache.
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-couchbase-nar/1.7.0/org.apache.nifi.processors.couchbase.GetCouchbaseKey/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-couchbase-nar/1.7.0/org.apache.nifi.processors.couchbase.GetCouchbaseKey/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-couchbase-nar/1.7.0/org.apache.nifi.processors.couchbase.GetCouchbaseKey/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-couchbase-nar/1.7.0/org.apache.nifi.processors.couchbase.GetCouchbaseKey/index.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1 @@
+GetCouchbaseKeywindow.onload =
function(){if(self==top) { document.getElementById('nameHeader').style.display
= "inherit"; } }GetCouchbaseKeyDescription: Get a document from
Couchbase Server via Key/Value access. The ID of the document to fetch may be
supplied by setting the Document Id property. NOTE: if the Document Id
property is not set, the contents of the FlowFile will be read to determine the
Document Id, which means that the contents of the entire FlowFile will be
buffered in memory.Tags: nosql, couchbase, database,
getProperties: In the list below, the names of required
properties appear in bold. Any other properties (not in bold)
are co
nsidered optional. The table also indicates any default values, and whether a
property supports the NiFi Expression
Language.NameDefault
ValueAllowable ValuesDescriptionCouchbase Cluster Controller ServiceController Service
API:
CouchbaseClusterControllerServiceImplementation:
CouchbaseClusterServiceA Couchbase Cluster Controller Service which manages
connections to a Couchbase cluster.Bucket
NamedefaultThe name of bucket to
access.Supports Expression Language: true (wil
l be evaluated using variable registry only)Document TypeJsonJsonBinaryThe type of contents.Document
IdA static, fixed Couchbase document id, or an expression to
construct the Couchbase document id.Supports Expression Language:
true (will be evaluated using flow file attributes and variable
registry)Put Value to AttributeIf
set, the retrieved value will be put into an attribute of the FlowFile instead
of a the content of the FlowFile. The attribute key to put to is determined by
evaluating value of this property.Supports Expression Language:
true (will be evaluate
d using flow file attributes and variable
registry)Relationships: NameDescriptionretryAll
FlowFiles failed to fetch from Couchbase Server but can be retried are routed
to this relationship.successValues retrieved from
Couchbase Server are written as outgoing FlowFiles content or put into an
attribute of the incoming FlowFile and routed to this
relationship.failureAll FlowFiles failed to fetch
from Couchbase Server and not retry-able are routed to this
relationship.originalThe original input FlowFile is
routed to this relationship when the value is retrieved from Couchbase Server
and routed to 'success'.Reads Attributes: None
specified.Writes Attributes: NameDescriptioncouchbase.clusterCluste
r where the document was retrieved
from.couchbase.bucketBucket where the document was
retrieved from.couchbase.doc.idId of the
document.couchbase.doc.casCAS of the
document.couchbase.doc.expiryExpiration of the
document.couchbase.exceptionIf Couchbase related
error occurs the CouchbaseException class name will be captured
here.State management: This component does not store
state.Restricted: This component is not restricted.Input
requirement: This component requires an incoming relationship.System
Resource Considerations:ResourceDescriptionMEMORYAn
instance of this component can cause high usage of this system resource.
Multiple instances or high concurrency settings may result a degradation of
performance.
\ No newline at end of file
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-couchbase-nar/1.7.0/org.apache.nifi.processors.couchbase.PutCouchbaseKey/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-couchbase-nar/1.7.0/org.apache.nifi.processors.couchbase.PutCouchbaseKey/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-couchbase-nar/1.7.0/org.apache.nifi.processors.couchbase.PutCouchbaseKey/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-couchbase-nar/1.7.0/org.apache.nifi.processors.couchbase.PutCouchbaseKey/index.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1 @@
+PutCouchbaseKeywindow.onload =
function(){if(self==top) { document.getElementById('nameHeader').style.display
= "inherit"; } }PutCouchbaseKeyDescription: Put a document to Couchbase
Server via Key/Value access.Tags:
svn commit: r1834461 [35/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.RouteText/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.RouteText/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.RouteText/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.RouteText/index.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1 @@
+RouteTextwindow.onload =
function(){if(self==top) { document.getElementById('nameHeader').style.display
= "inherit"; } }RouteTextDescription: Routes textual data based on a
set of user-defined rules. Each line in an incoming FlowFile is compared
against the values specified by user-defined Properties. The mechanism by which
the text is compared to these user-defined properties is defined by the
'Matching Strategy'. The data is then routed according to these rules, routing
each line of the text individually.Tags: attributes, routing,
text, regexp, regex, Regular Expression, Expression Language, csv, filter,
logs, delimitedProperties: In the list below, the names of
requir
ed properties appear in bold. Any other properties (not in
bold) are considered optional. The table also indicates any default
values.NameDefault
ValueAllowable ValuesDescriptionRouting StrategyRoute to
each matching Property NameRoute to each
matching Property Name Route to 'matched'
if line matches all conditions Route to 'matched' if
lines matches any condition Specifies how to determine
which Relationship(s) to use when evaluating the lines of incoming text against
the 'Matching Strategy' and user-defined properties.Matching StrategySatisfies Expression
Starts With Ends With Contains Equals Matches Regular Expression Contains Regular Expression Specifies how to evaluate each
line of incoming text against the user-defined properties.Character SetUTF-8The Character Set in which the incoming text is
encodedIgnore Leading/Trailing
WhitespacetrueIndicates whether or not the
whitespace at the beginning and end of the lines should be ignored when
evaluating the line.Ignore
CasefalsetruefalseIf true, capitalization will not be taken into account when
comparing values. E.g., matching against 'HELLO' or 'hello' will have the same
result. This property is ignored if the 'Matching Strategy' is set to
'Satisfies Expression'.Grouping Regular
ExpressionSpecifies a Regular Expression to evaluate against each line
to determine which Group the line should be placed in. The Regular Expression
must have at least one Capturing Group that defines the line's Group. If
multiple Capturing Groups exist in the Regular Expression, the values from all
Capturing Groups will be concatenated together. Two lines will not be placed
into the same FlowFile unless they both have the same value for the Group (or
neither line matches the Regular Expression). For example, to group
together all lines in a CSV File by the first column, we can set this value
to "(.*?),.*". Two lines that have the same Group but different Relationships
will never be placed into the same FlowFile.Dynamic
Properties: Dynamic Properties allow the user to specify both the name
and value of a property.NameValueDescriptionRelationship Namevalue to match
againstRoutes data that matches the value specified in the Dynamic
Property Value to the Relationship specified in the Dynamic Property
Key.Supports Expression Language: true (will be evaluated using
flow file attributes and variable
registry)Relationships: NameDescriptionoriginalThe
original input file will be routed to this destination when the lines have
been successfull
y routed to 1 or more relationshipsunmatchedData
that does not satisfy the required user-defined rules will be routed to this
RelationshipDynamic Relationships: A Dynamic
Relationship may be created based on how the user configures the
Processor.NameDescriptionName
from Dynamic PropertyFlowFiles that match the Dynamic Property's
valueReads Attributes: None specified.Writes
Attributes: NameDescriptionRouteText.RouteThe
name of the relationship to which the FlowFile was
routed.RouteText.GroupThe value captured by all
capturing groups in the 'Grouping Regular Expression' property. If this
property is not set or contains no capturing groups, this attribute will not be
added.State management: This component does not store state.Restricted: This component is
not restricted.Input requirement: This component requires an incoming
relationship.System Resource Considerations:None
specified.
\ No newline at end of file
Added:
svn commit: r1834461 [25/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-solr-nar/1.7.0/org.apache.nifi.processors.solr.QuerySolr/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-solr-nar/1.7.0/org.apache.nifi.processors.solr.QuerySolr/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-solr-nar/1.7.0/org.apache.nifi.processors.solr.QuerySolr/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-solr-nar/1.7.0/org.apache.nifi.processors.solr.QuerySolr/index.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1 @@
+QuerySolrwindow.onload =
function(){if(self==top) { document.getElementById('nameHeader').style.display
= "inherit"; } }QuerySolrDescription: Queries Solr and outputs the
results as a FlowFile in the format of XML or using a Record
WriterTags: Apache, Solr, Get, Query,
RecordsProperties: In the list below, the names of required
properties appear in bold. Any other properties (not in bold)
are considered optional. The table also indicates any default values, whether a
property supports the NiFi Expression
Language, 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 nifi.properties file has an entry for the property
nifi.sensitive.props.key.NameDefault ValueAllowable
ValuesDescriptionSolr
TypeStandardCloud Standard The type of Solr instance, Cloud or Standard.Solr LocationThe Solr url for a Solr Type of
Standard (ex: http://localhost:8984/solr/getting
started), or the ZooKeeper hosts for a Solr Type of Cloud (ex:
localhost:9983).Supports Expression Language: true (will be
evaluated using variable registry only)CollectionThe Solr collection name, only
used with a Solr Type of CloudSupports Expression Language: true
(will be evaluated using flow file attributes and variable
registry)Return
TypeXMLXMLRecordsOutput format of Solr results. Write Solr documents to
FlowFiles as XML or using a Record WriterRecord
WriterController Service API:
RecordSetWriterFactoryImplementations: AvroRecordSetWriterCSVRecordSetWriterFreeFormTextRecordSetWriterJsonRecordSetWriterScriptedRecordSetWriterXMLRecordSetWriterThe Record Writer to use in order to write Solr documents to
FlowFiles. Must be set if "Records" is used as return type.
Supports Expression Language: true (will be evaluated using flow file
attributes and variable registry)Solr Query*:*Solr Query, e. g.
field:valueSupports Expression Language: true (will be evaluated
using flow file attributes and variable registry)Request Handler/selectDefine a request handler here, e. g.
/querySupports Expression Language: true (will be evaluated using
flow file attributes and variable registry)Field ListComma separated list of fields
to be included into results, e. g. field1,field2Supports
Expression Language: true (will be e
valuated using flow file attributes and variable
registry)Sorting of result listComma separated sort clauses to define the sorting of results,
e. g. field1 asc, field2 descSupports Expression Language: true
(will be evaluated using flow file attributes and variable
registry)Start of resultsOffset of result setSupports Expression Language:
true (will be evaluated using flow file attributes and variable
registry)RowsNumber of results to be returned for a single
requestSupports Expression Language: true (will be evaluated using
flow file attributes and variable registry)Total amount of returned resultsid="default-value">return_only_top_resultsid="allowable-values">Entire resultsOnly top
>resultsTotal amount of Solr documents to
>be returned. If this property is set to "Only top results", only single
>requests will be sent to Solr and the results will be written into single
>FlowFiles. If it is set to "Entire results", all results matching to the
>query are retrieved via multiple Solr requests and returned in multiple
>FlowFiles. For both options, the number of Solr documents to be returned in a
>FlowFile depends on the configuration of the "Rows" propertyid="name">Kerberos Credentials Serviceid="allowable-values">Controller Service API:
>KerberosCredentialsServiceImplementation:
>href="../../../nifi-kerberos-credentials-service-nar/1.7.0/org.apache.nif
i.kerberos.KeytabCredentialsService/index.html">KeytabCredentialsServiceSpecifies the Kerberos Credentials Controller Service that
should be used for authenticating with KerberosUsernameThe username to use when Solr
is configured with basic authentication.Supports Expression
Language: true (will be evaluated using variable registry
only)PasswordThe
password to use when Solr is configured with basic
authentication.Sensitive Property:
trueSupports Expression Language: true (will be evaluated
using variable registry only)SSL
svn commit: r1834461 [29/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.GenerateTableFetch/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.GenerateTableFetch/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.GenerateTableFetch/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.GenerateTableFetch/index.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1,6 @@
+GenerateTableFetchwindow.onload =
function(){if(self==top) { document.getElementById('nameHeader').style.display
= "inherit"; } }GenerateTableFetchDescription: Generates SQL select
queries that fetch "pages" of rows from a table. The partition size property,
along with the table's row count, determine the size and number of pages and
generated FlowFiles. In addition, incremental fetching can be achieved by
setting Maximum-Value Columns, which causes the processor to track the columns'
maximum values, thus only fetching rows whose columns' values exceed the
observed maximums. This processor is intended to be run on the Primary Node
only.
+
+This processor can accept incoming connections; the behavior of the processor
is different whether incoming connections are provided:
+ - If no incoming connection(s) are specified, the processor will generate
SQL queries on the specified processor schedule. Expression Language is
supported for many fields, but no flow file attributes are available. However
the properties will be evaluated using the Variable Registry.
+ - If incoming connection(s) are specified and no flow file is available to a
processor task, no work will be performed.
+ - If incoming connection(s) are specified and a flow file is available to a
processor task, the flow file's attributes may be used in Expression Language
for such fields as Table Name and others. However, the Max-Value Columns and
Columns to Return fields must be empty or refer to columns that are available
in each specified table.Additional
Details...Tags: sql, select, jdbc, query, database, fetch,
generateProperties: In the list below, the names of required
properties appear in bold. Any other properties (not in bold)
are considered optional. The table also indicates any default values, and
whether a property supports the NiFi Expression
Language.NameDefault
ValueAllowable ValuesDescriptionDatabase Connection Pooling ServiceController Service API:
DBCPServiceImplementations: DBCPConnectionPoolLookupDBCPConnectionPoolHiveConnectionPoolThe Controller Service that is used to obtain a connection to
the database.Database TypeGenericGeneric Oracle Oracle 12+ MS SQL 2012+ MS SQL 2008 MySQL The type/flavor of database,
used for generating database-specific code. In many cases the Generic type
should suffice, but some databases (such as Oracle) requi
re custom SQL clauses. Table
NameThe name of the database table
to be queried.Supports Expression Language: true (will be
evaluated using flow file attributes and variable
registry)Columns to ReturnA
comma-separated list of column names to be used in the query. If your database
requires special treatment of the names (quoting, e.g.), each name should
include such treatment. If no column names are supplied, all columns in the
specified table will be returned. NOTE: It is important to use consistent
column names for a given table for incremental fetch to work
properly.Supports Expression Language: true (will be evaluated
using flow file attributes and variable registry)Maximu
m-value ColumnsA comma-separated list of
column names. The processor will keep track of the maximum value for each
column that has been returned since the processor started running. Using
multiple columns implies an order to the column list, and each column's values
are expected to increase more slowly than the previous columns' values. Thus,
using multiple columns implies a hierarchical structure of columns, which is
usually used for partitioning tables. This processor can be used to retrieve
only those rows that have been added/updated since the last retrieval. Note
that some JDBC types such as bit/boolean are not conducive to maintaining
maximum value, so columns of these types should not be listed in this property,
and will result in error(s) during processing. If no columns are provided, all
rows from the table will be considered, which could have a performance impact.
NOTE: It is important to
use consistent max-value column names for a given table for incremental fetch
to work properly.Supports Expression Language: true (will be
evaluated using flow file attributes and variable
svn commit: r1834461 [30/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.HashAttribute/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.HashAttribute/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.HashAttribute/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.HashAttribute/index.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1 @@
+HashAttributewindow.onload =
function(){if(self==top) { document.getElementById('nameHeader').style.display
= "inherit"; } }HashAttributeDescription: Hashes together the key/value
pairs of several FlowFile Attributes and adds the hash as a new attribute.
Optional properties are to be added such that the name of the property is the
name of a FlowFile Attribute to consider and the value of the property is a
regular expression that, if matched by the attribute value, will cause that
attribute to be used as part of the hash. If the regular expression contains a
capturing group, only the value of the capturing group will be
used.Tags: attributes, hashProperties: In the
list b
elow, the names of required properties appear in bold. Any
other properties (not in bold) are considered optional. The table also
indicates any default values.NameDefault ValueAllowable
ValuesDescriptionHash Value
Attribute KeyThe name of the FlowFile
Attribute where the hash value should be storedDynamic
Properties: Dynamic Properties allow the user to specify both the name
and value of a property.NameValueDescriptionA flowfile attribute key for attribute inspectionA Regular ExpressionThis regular expression is evaluated
against the flowfile attribute values. If the regular expression contains a
capturing group, the value of that group
will be used when comparing flow file attributes. Otherwise, the original
flow file attribute's value will be used if and only if the value matches the
given regular expression.Supports Expression Language:
falseRelationships: NameDescriptionsuccessUsed
for FlowFiles that have a hash value
addedfailureUsed for FlowFiles that are missing
required attributesReads Attributes: None
specified.Writes Attributes: NameDescriptionHash
Value Attribute KeyThis Processor adds an attribute whose value
is the result of Hashing the existing FlowFile attributes. The name of this
attribute is specified by the Hash Value Attribute Key
property.State management: This component does not
store state.R
estricted: This component is not restricted.Input requirement:
This component requires an incoming relationship.System Resource
Considerations:None specified.
\ No newline at end of file
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.HashContent/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.HashContent/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.HashContent/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.HashContent/index.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1 @@
+HashContentwindow.onload =
function(){if(self==top) { document.getElementById('nameHeader').style.display
= "inherit"; } }HashContentDescription: Calculates a hash value for the
Content of a FlowFile and puts that hash value on the FlowFile as an attribute
whose name is determined by the Hash Attribute Name
propertyTags: hash, content, MD5, SHA-1,
SHA-256Properties: In the list below, the names of required
properties appear in bold. Any other properties (not in bold)
are considered optional. The table also indicates any default values.NameDefault ValueAllowable
ValuesDescriptionHash Attribute Namehash.valueThe name of the FlowFile Attribute into which the Hash Value
should be written. If the value already exists, it will be
overwrittenHash AlgorithmMD5SHA-1SHA-384SKEIN-512-256SKEIN-1024-384BLAKE2B-160SHAKECCAK-288WHIRLPOOLSKEIN-512-384SHA-224SM3BLAKE2B-512GOST3411-2012-512KECCAK-256SKEIN-512-128BLAKE2B-384SKEIN-256-160OID.2.16.840.1.101.3.4.2.10DSTU7564-256SHA-256BLAKE2S-224SHA3-256KECCAK-384SKEIN-256-128DSTU7564-384KECCAK-224SKEIN-512-512SKEIN-1024-512SKEIN-512-160OID.
svn commit: r1834461 [42/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache
Modified: nifi/site/trunk/docs/robots.txt URL: http://svn.apache.org/viewvc/nifi/site/trunk/docs/robots.txt?rev=1834461=1834460=1834461=diff == --- nifi/site/trunk/docs/robots.txt (original) +++ nifi/site/trunk/docs/robots.txt Wed Jun 27 00:37:46 2018 @@ -2,25 +2,26 @@ - - - - -NiFi -http://localhost:8080/nifi/assets/reset.css/reset.css; type="text/css" /> -http://localhost:8080/nifi/css/common-ui.css; type="text/css" /> -http://localhost:8080/nifi/fonts/flowfont/flowfont.css; type="text/css" /> -http://localhost:8080/nifi/assets/font-awesome/css/font-awesome.min.css; type="text/css" /> -http://localhost:8080/nifi/css/message-pane.css; type="text/css" /> -http://localhost:8080/nifi/css/message-page.css; type="text/css" /> - - - - -Did you mean: http://localhost:8080/nifi/;>/nifi - -You may have mistyped... - - + + + +NiFi +http://localhost:8080/nifi/assets/reset.css/reset.css; type="text/css"/> +http://localhost:8080/nifi/css/common-ui.css; type="text/css"/> +http://localhost:8080/nifi/fonts/flowfont/flowfont.css; type="text/css"/> +http://localhost:8080/nifi/assets/font-awesome/css/font-awesome.min.css; type="text/css"/> +http://localhost:8080/nifi/css/message-pane.css; type="text/css"/> +http://localhost:8080/nifi/css/message-page.css; type="text/css"/> +http://localhost:8080/nifi/;> + + + + + +Did you mean: http://localhost:8080/nifi/;>/nifi + +You may have mistyped... but we'll try to redirect you in 5 seconds. + +
svn commit: r1834461 [13/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-influxdb-nar/1.7.0/org.apache.nifi.processors.influxdb.PutInfluxDB/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-influxdb-nar/1.7.0/org.apache.nifi.processors.influxdb.PutInfluxDB/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-influxdb-nar/1.7.0/org.apache.nifi.processors.influxdb.PutInfluxDB/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-influxdb-nar/1.7.0/org.apache.nifi.processors.influxdb.PutInfluxDB/index.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1 @@
+PutInfluxDBwindow.onload =
function(){if(self==top) { document.getElementById('nameHeader').style.display
= "inherit"; } }PutInfluxDBDescription: Processor to write the content
of a FlowFile in 'line protocol'. Please check details of the 'line protocol'
in InfluxDB documentation (https://www.influxdb.com/). The flow file can
contain single measurement point or multiple measurement points separated by
line seperator. The timestamp (last field) should be in nano-seconds
resolution.Tags: influxdb, measurement, insert, write, put,
timeseriesProperties: In the list below, the names of required
properties appear in bold. Any other properties (not in bold)
are considered optional. The table also indicates any default values, whether
a property supports the NiFi Expression
Language, 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 nifi.properties file has an entry for the
property nifi.sensitive.props.key.NameDefault ValueAllowable
ValuesDescriptionDatabase
NameInfluxDB database to connect
toSupports Expression Language: true (will be evaluated using flow
file attributes and variable registry)InfluxDB connection URLhttp://localhost:8086InfluxDB URL to connect to. Eg:
http://influxdb:8086Supports Expression Language: true (will be
evaluated using variable registry only)InfluxDB Max Connection Time Out (seconds)0 secondsThe maximum time for establishing connection to the
InfluxDBUsernameUsername for accessing InfluxDBSupports
Expression Language: true (will be evaluated using variable registry
only)PasswordPassword for userSensitive Property:
trueSupports Expression Language: true (will be evaluated
using variable registry only)
Character SetUTF-8Specifies the character set of the document
data.Supports Expression Language: true (will be evaluated using
flow file attributes and variable registry)Consistency LevelONEOne Any All Quorum InfluxDB consistency levelSupports Expression
Language: true (will be evaluated using flow file attributes and variable
registry)Retention
PolicyautogenRetention policy for the saving
the recordsSupports Expression Language: true (will be evaluated
using flow file attributes and variable registry)Max size of records1
MBMaximum size of
records allowed
to be posted in one batchSupports Expression Language: true
(will be evaluated using variable registry
only)Relationships: NameDescriptionfailure-max-sizeFlowFiles
exceeding max records size are routed to this
relationshipretryFlowFiles were not saved to
InfluxDB due to retryable exception are routed to this
relationshipsuccessSuccessful FlowFiles that are
saved to InfluxDB are routed to this
relationshipfailureFlowFiles were not saved to
InfluxDB are routed to this relationshipReads Attributes:
None specified.Writes Attributes: NameDescriptioninfluxdb.error.messageInfluxDB
error messageState management: This component does
not store state.Restric
ted: This component is not restricted.Input requirement: This
component requires an incoming relationship.System Resource
Considerations:None specified.
\ No newline at end of file
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-jms-processors-nar/1.7.0/org.apache.nifi.jms.cf.JMSConnectionFactoryProvider/additionalDetails.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-jms-processors-nar/1.7.0/org.apache.nifi.jms.cf.JMSConnectionFactoryProvider/additionalDetails.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-jms-processors-nar/1.7.0/org.apache.nifi.jms.cf.JMSConnectionFactoryProvider/additionalDetails.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-jms-processors-nar/1.7.0/org.apache.nifi.jms.cf.JMSConnectionFactoryProvider/additionalDetails.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1,56 @@
+
+
+
+
+
+JMSConnectionFactoryProvider
+
+
+
+
+Description:
+
+This ControllerService serves as a
svn commit: r1834461 [20/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-poi-nar/1.7.0/org.apache.nifi.processors.poi.ConvertExcelToCSVProcessor/additionalDetails.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-poi-nar/1.7.0/org.apache.nifi.processors.poi.ConvertExcelToCSVProcessor/additionalDetails.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-poi-nar/1.7.0/org.apache.nifi.processors.poi.ConvertExcelToCSVProcessor/additionalDetails.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-poi-nar/1.7.0/org.apache.nifi.processors.poi.ConvertExcelToCSVProcessor/additionalDetails.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1,97 @@
+
+
+
+
+
+ConvertExcelToCSVProcessor
+
+table {
+border-collapse: collapse;
+}
+
+table, th, td {
+border: 1px solid #ccc;
+}
+
+td.r {
+text-align: right;
+}
+
+td {
+width: 50px;
+padding: 5px;
+}
+
+
+
+
+
+How it extracts CSV data from a sheet
+
+ConvertExcelToCSVProcessor extracts CSV data with following rules:
+
+
+Find the fist cell which has a value in it (the FirstCell).
+Scan cells in the first row, starting from the FirstCell,
+until it reaches to a cell after which no cell with a value can not be
found in the row (the FirstRowLastCell).
+Process the 2nd row and later, from the column of FirstCell to the
column of FirstRowLastCell.
+If a row does not have any cell that has a value, then the row is
ignored.
+
+
+
+As an example, the sheet shown below will be:
+
+
+
+
+row
ABCDEFG
+ 1
+ 2
xyz
+ 3 1
+ 42 3
+ 5
4
+ 6
567
+ 7
8
+ 8
+ 9
9
+ 10
+ 11
+
+
+
+
+converted to following CSV:
+
+
+
+x,y,z
+1,,
+,3,
+,,4
+5,6,7
+,,9
+
+
+
+C2(x) is the FirstCell, and E2(z) is the FirstRowLastCell.
+A4(2) is ignored because it is out of range. So is F7(8).
+Row 7 and 8 are ignored because those do not have a valid cell.
+It is important to have a header row as shown in the example to define
data area,
+especially when a sheet includes empty cells.
+
+
+
+
\ No newline at end of file
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-poi-nar/1.7.0/org.apache.nifi.processors.poi.ConvertExcelToCSVProcessor/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-poi-nar/1.7.0/org.apache.nifi.processors.poi.ConvertExcelToCSVProcessor/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-poi-nar/1.7.0/org.apache.nifi.processors.poi.ConvertExcelToCSVProcessor/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-poi-nar/1.7.0/org.apache.nifi.processors.poi.ConvertExcelToCSVProcessor/index.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1 @@
+ConvertExcelToCSVProcessorwindow.onload =
function(){if(self==top) { document.getElementById('nameHeader').style.display
= "inherit"; } }ConvertExcelToCSVProcessorDescription: Consumes a
Microsoft Excel document and converts each worksheet to csv. Each sheet from
the incoming Excel document will generate a new Flowfile that will be output
from this processor. Each output Flowfile's contents will be formatted as a csv
file where the each row from the excel sheet is output as a newline in the csv
file. This processor is currently only capable of processing .xlsx (XSSF 2007
OOXML file format) Excel documents and not older .xls (HSSF '97(-2007) file
format) documents. This processor also expects well forma
tted CSV content and will not escape cell's containing invalid content such as
newlines or additional commas.Additional Details...Tags:
excel, csv, poiProperties: In the list below, the names
of required properties appear in bold. Any other properties
(not in bold) are considered optional. The table also indicates any default
values, and whether a property supports the NiFi Expression
Language.NameDefault
ValueAllowable ValuesDescriptionSheets to ExtractComma separated list of Excel
document sheet names that should be extracted from the excel document. If this
property is left blank then all of the sheets will be extracted from the Excel
document. The list
of names is case in-sensitive. Any sheets not specified in this value will be
ignored.Supports Expression Language: true (will be evaluated
using flow file attributes and variable registry)Number of Rows to Skip0The row number of the first row to start processing.Use this
to skip over rows of data at the top of your worksheet that are not part of the
dataset.Empty rows of data anywhere in the spreadsheet will always be
svn commit: r1834461 [4/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache.
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-aws-nar/1.7.0/org.apache.nifi.processors.aws.sns.PutSNS/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-aws-nar/1.7.0/org.apache.nifi.processors.aws.sns.PutSNS/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-aws-nar/1.7.0/org.apache.nifi.processors.aws.sns.PutSNS/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-aws-nar/1.7.0/org.apache.nifi.processors.aws.sns.PutSNS/index.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1 @@
+PutSNSwindow.onload =
function(){if(self==top) { document.getElementById('nameHeader').style.display
= "inherit"; } }PutSNSDescription: Sends the content of a FlowFile as a
notification to the Amazon Simple Notification ServiceTags:
amazon, aws, sns, topic, put, publish, pubsubProperties:
In the list below, the names of required properties appear in
bold. Any other properties (not in bold) are considered
optional. The table also indicates any default values, whether a property
supports the NiFi
Expression Language, and whether a property is considered "sensitive",
meaning that its value wil
l be encrypted. Before entering a value in a sensitive property, ensure that
the nifi.properties file has an entry for the property
nifi.sensitive.props.key.NameDefault ValueAllowable
ValuesDescriptionAmazon Resource
Name (ARN)The name of the resource to
which notifications should be publishedSupports Expression
Language: true (will be evaluated using flow file attributes and variable
registry)ARN TypeTopic ARNTopic ARN
Target ARN The type of Amazon
Resource Name that is being used.E-mail
SubjectThe optional subject to use for any subscribers that are
subscribed via E-mailSupports Expression Language: true (will be
evaluated using flow file attributes and variable
registry)Regionus-west-2AWS GovCloud
(US)US East (N. Virginia)US East (Ohio)US West (N.
California)US West (Oregon)EU (Ireland)EU
(London)EU (Paris)EU (Frankfurt)Asia Pacific
(Mumbai)Asia Pacific (Singapore)<
li>Asia Pacific (Sydney)Asia Pacific (Tokyo)Asia Pacific
(Seoul)South America (Sao Paulo)China (Beijing)China
(Ningxia)Canada (Central)No
Description Provided.Access KeyNo
Description Provided.Sensitive Property:
trueSupports Expression Language: true (will be evaluated
using variable registry only)Secret
KeyNo Description Provided.Sensitive Property:
trueSupports Expression Language: true (will be evaluated
using variable registry only)Credentials
FilePath to a file containi
ng AWS access key and secret key in properties file format.AWS Credentials Provider serviceController Service API:
AWSCredentialsProviderServiceImplementation:
AWSCredentialsProviderControllerServiceThe Controller Service that is used to obtain aws credentials
providerCommunications
Timeout30 secsNo Description
Provided.Use JSON
StructurefalsetruefalseIf true, the contents of the FlowFile must be JSON with a
top-level ele
ment named 'default'. Additional elements can be used to send different
messages to different protocols. See the Amazon SNS Documentation for more
information.Character SetUTF-8The character set in which the FlowFile's content is
encodedSupports Expression Language: true (will be evaluated using
flow file attributes and variable registry)Proxy HostProxy host name or
IPSupports Expression Language: true (will be evaluated using
variable registry only)Proxy Host
PortProxy host portSupports Expression Language: true
(will be evaluated using variable registry only)Proxy UsernameProxy
usernameSupports Expression Language: true (undefined
scope)Proxy PasswordProxy passwordSensitive Property:
trueSupports Expression Language: true (undefined
scope)Relationships: NameDescriptionsuccessFlowFiles
are routed to success relationshipfailureFlowFiles
are routed to failure relationshipReads Attributes:
None specified.Writes Attributes: None specified.State
management: This component does not store state.Restricted: This
component is not restricted.Input requirement: This component requires
a
n incoming relationship.System Resource Considerations:None
specified.See Also:GetSQS, PutSQS
\ No newline at end of file
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-aws-nar/1.7.0/org.apache.nifi.processors.aws.sqs.DeleteSQS/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-aws-nar/1.7.0/org.apache.nifi.processors.aws.sqs.DeleteSQS/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-aws-nar/1.7.0/org.apache.nifi.processors.aws.sqs.DeleteSQS/index.html
(added)
+++
svn commit: r1834461 [28/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.ExtractText/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.ExtractText/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.ExtractText/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.ExtractText/index.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1,2 @@
+ExtractTextwindow.onload =
function(){if(self==top) { document.getElementById('nameHeader').style.display
= "inherit"; } }ExtractTextDescription: Evaluates one or more Regular
Expressions against the content of a FlowFile. The results of those Regular
Expressions are assigned to FlowFile Attributes. Regular Expressions are
entered by adding user-defined properties; the name of the property maps to the
Attribute Name into which the result will be placed. The first capture group,
if any found, will be placed into that attribute name.But all capture groups,
including the matching string sequence itself will also be provided at that
attribute name with an index value provided, with the exception of a ca
pturing group that is optional and does not match - for example, given the
attribute name "regex" and expression "abc(def)?(g)" we would add an attribute
"regex.1" with a value of "def" if the "def" matched. If the "def" did not
match, no attribute named "regex.1" would be added but an attribute named
"regex.2" with a value of "g" will be added regardless.The value of the
property must be a valid Regular Expressions with one or more capturing groups.
If the Regular Expression matches more than once, only the first match will be
used unless the property enabling repeating capture group is set to true. If
any provided Regular Expression matches, the FlowFile(s) will be routed to
'matched'. If no provided Regular Expression matches, the FlowFile will be
routed to 'unmatched' and no attributes will be applied to the
FlowFile.Tags: evaluate, extract, Text, Regular Expression,
regexProperties: In the list below, the names of required
properties appear in bold. Any other properties (not in bold) are considered
optional. The table also indicates any default values.NameDefault ValueAllowable
ValuesDescriptionCharacter
SetUTF-8The Character Set in which the
file is encodedMaximum Buffer
Size1 MBSpecifies the maximum amount of
data to buffer (per file) in order to apply the regular expressions. Files
larger than the specified maximum will not be fully evaluated.Maximum Capture Group Length1024Specifies the maximum number of
characters a given capture group value can have. Any characters beyond
the max will be truncated.Enable Canonical
EquivalencefalsetruefalseIndicates that two characters match only when their full
canonical decompositions match.Enable
Case-insensitive MatchingfalsetruefalseIndicates that two characters match even if they are in a
different case. Can also be specified via the embedded flag
(?i).Permit Whitespace and Comments in
PatternfalsetruefalseIn this mode, whitespace is ignored, and embedded comments
starting with # are ignored until the end of a line. Can also be specified via
the em
bedded flag (?x).Enable DOTALL
ModefalsetruefalseIndicates that the expression '.' should match any character,
including a line terminator. Can also be specified via the embedded flag
(?s).Enable Literal Parsing of the
PatternfalsetruefalseIndicates that Metacharacters and escape characters should be
given no special meaning.Enable Multiline
ModefalsetruefalseIndicates that '^' and '$' should match just after and just
before a line terminator or end of sequence, instead of only the beginning or
end of the entire input.
Can also be specified via the embeded flag (?m).Enable Unicode-aware Case FoldingfalsetruefalseWhen used with 'Enable Case-insensitive Matching', matches in
a manner consistent with the Unicode Standard. Can also be specified via the
embedded flag (?u).Enable Unicode
Predefined Character ClassesfalsetruefalseSpecifies conformance with the Unicode Technical Standard #18:
Unicode Regular Expression Annex C: Compatibility Properties. Can also be
specified via the embedded flag (?U).Enable
Unix Lines ModefalsetruefalseInd
icates that only the '
+' line terminator is recognized in the behavior of '.', '^', and '$'. Can
also be specified via the embedded flag (?d).Include Capture Group 0truetruefalseIndicates that Capture Group 0 should be included as an
attribute. Capture Group 0 represents the entirety of the regular expression
match, is typically not used, and could have
svn commit: r1834461 [8/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache.
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-elasticsearch-restapi-nar/1.7.0/org.apache.nifi.processors.elasticsearch.DeleteByQueryElasticsearch/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-elasticsearch-restapi-nar/1.7.0/org.apache.nifi.processors.elasticsearch.DeleteByQueryElasticsearch/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-elasticsearch-restapi-nar/1.7.0/org.apache.nifi.processors.elasticsearch.DeleteByQueryElasticsearch/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-elasticsearch-restapi-nar/1.7.0/org.apache.nifi.processors.elasticsearch.DeleteByQueryElasticsearch/index.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1 @@
+DeleteByQueryElasticsearchwindow.onload =
function(){if(self==top) { document.getElementById('nameHeader').style.display
= "inherit"; } }DeleteByQueryElasticsearchDescription: Delete from an
ElasticSearch index using a query. The query can be loaded from a flowfile body
or from the Query parameter.Tags: elastic, elasticsearch,
delete, queryProperties: In the list below, the names of
required properties appear in bold. Any other properties (not
in bold) are considered optional. The table also indicates any default values,
and whether a property supports the NiFi Expression
Language.NameDefault ValueAllowable
ValuesDescriptionQueryA
query in JSON syntax, not Lucene syntax. Ex:
{"query":{"match":{"somefield":"somevalue"}}}. If this parameter is not set,
the query will be read from the flowfile content.Supports
Expression Language: true (will be evaluated using flow file attributes and
variable registry)Query AttributeIf
set, the executed query will be set on each result flowfile in the specified
attribute.Supports Expression Language: true (will be evaluated
using flow file attributes and variable registry)IndexThe na
me of the index to use.Supports Expression Language: true (will
be evaluated using flow file attributes and variable
registry)TypeThe
type of this document (used by Elasticsearch for indexing and
searching)Supports Expression Language: true (will be evaluated
using flow file attributes and variable registry)Client ServiceController Service API:
ElasticSearchClientServiceImplementation:
ElasticSearchClientServiceImplAn ElasticSearch client service to use for running
queries.Relationships: NameDescriptionsuccessIf
the delete by query succeeds, and a flowfile was read, it will be sent to this
relationship.failureIf the delete by query fails,
and a flowfile was read, it will be sent to this
relationship.Reads Attributes: None
specified.Writes Attributes: NameDescriptionelasticsearch.delete.tookThe
amount of time that it took to complete the delete operation in
ms.elasticsearch.delete.errorThe error message
provided by ElasticSearch if there is an error running the
delete.State management: This component does not
store state.Restricted: This component is not restricted.Input
requirement: This component allows an incoming relationship.System
Resource Considerations:None specified.
\ No newline at end of file
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-elasticsearch-restapi-nar/1.7.0/org.apache.nifi.processors.elasticsearch.JsonQueryElasticsearch/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-elasticsearch-restapi-nar/1.7.0/org.apache.nifi.processors.elasticsearch.JsonQueryElasticsearch/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-elasticsearch-restapi-nar/1.7.0/org.apache.nifi.processors.elasticsearch.JsonQueryElasticsearch/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-elasticsearch-restapi-nar/1.7.0/org.apache.nifi.processors.elasticsearch.JsonQueryElasticsearch/index.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1 @@
+JsonQueryElasticsearchwindow.onload =
function(){if(self==top) { document.getElementById('nameHeader').style.display
= "inherit"; } }JsonQueryElasticsearchDescription: A processor that
allows the user to run a query (with aggregations) written with the
ElasticSearch JSON DSL. It does not automatically paginate queries for the
user. If an incoming relationship is added to this processor, it will use the
flowfile's content for the query. Care should be taken on the size of the query
because the entire response from ElasticSearch will be loaded into memory all
at once and converted into the resulting flowfiles.Tags:
elasticsearch, elasticsearch 5, query, read, get,
jsonProperties:
In the list below, the names of required properties appear in
bold. Any other properties (not in bold) are considered
optional.
svn commit: r1834461 [9/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache.
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-flume-nar/1.7.0/org.apache.nifi.processors.flume.ExecuteFlumeSource/additionalDetails.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-flume-nar/1.7.0/org.apache.nifi.processors.flume.ExecuteFlumeSource/additionalDetails.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-flume-nar/1.7.0/org.apache.nifi.processors.flume.ExecuteFlumeSource/additionalDetails.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-flume-nar/1.7.0/org.apache.nifi.processors.flume.ExecuteFlumeSource/additionalDetails.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1,114 @@
+
+
+
+
+
+ExecuteFlumeSource
+
+
+
+
+Data Model
+
+This processor executes an Apache Flume source. Each Flume Event is turned
into
+a FlowFile. The content of the FlowFile is set to the body of the Event and
+the Event headers become FlowFile attributes.
+
+Configuration Details
+
+This processor is designed to execute arbitrary Flume sources. Most of the
details
+of configuring the source is deferred to Flume's built-in configuration
system.
+For details on the available settings for each source type, refer to the
Flume
+http://flume.apache.org/FlumeUserGuide.html#flume-sources;>User
Guide.
+Configuring the Flume source is a four step process:
+
+
+Set the Source Type property to a valid Flume source type.
+
+Set the Agent Name property to the name of the agent in your
+Flume configuration. This is the prefix of the properties in the Flume
+configuration file. Example: tier1
+
+
+Set the Source Name property to the name of the source in your Flume
+configuration. If Agent Name is tier1, then the Source
Name
+is the value of the tier1.sources property. Example:
src-1
+
+
+Copy and paste the configuration for the source from your Flume
configuration
+file into the Flume Configuration property. Assuming you're using
+the same Agent Name and Source Name as in the examples above, this
will be all
+of the properties that start with tier1.sources.src-1.
+Do not copy the tier1.sources.src-1.type or
+tier1.sources.src-1.channel properties.
+
+
+Usage Example
+
+Assuming you had the following existing Flume configuration file:
+
+
+a1.sources = r1
+a1.sinks = k1
+a1.channels = c1
+
+a1.sources.r1.type = multiport_syslogtcp
+a1.sources.r1.channels = c1
+a1.sources.r1.host = 0.0.0.0
+a1.sources.r1.ports = 10001 10002 10003
+a1.sources.r1.portHeader = port
+
+a1.sinks.k1.type = logger
+
+a1.channels.c1.type = memory
+a1.channels.c1.capacity = 1000
+a1.channels.c1.transactionCapacity = 100
+
+a1.sources.r1.channels = c1
+a1.sinks.k1.channel = c1
+
+Then you'd configure the ExecuteFlumeSource as follows:
+
+
+
+Property
+Value
+
+
+Source Type
+multiport_syslogtcp
+
+
+Agent Name
+a1
+
+
+Source Name
+r1
+
+
+Flume Configuration
+
+
+a1.sources.r1.host = 0.0.0.0
+a1.sources.r1.ports = 10001 10002 10003
+a1.sources.r1.portHeader = port
+
+
+
+
+
+
\ No newline at end of file
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-flume-nar/1.7.0/org.apache.nifi.processors.flume.ExecuteFlumeSource/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-flume-nar/1.7.0/org.apache.nifi.processors.flume.ExecuteFlumeSource/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-flume-nar/1.7.0/org.apache.nifi.processors.flume.ExecuteFlumeSource/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-flume-nar/1.7.0/org.apache.nifi.processors.flume.ExecuteFlumeSource/index.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1 @@
+ExecuteFlumeSourcewindow.onload =
function(){if(self==top) { document.getElementById('nameHeader').style.display
= "inherit"; } }ExecuteFlumeSourceDescription: Execute a Flume source.
Each Flume Event is sent to the success relationship as a FlowFileAdditional Details...Tags:
flume, hadoop, get, sourceProperties: In the list
below, the names of required properties appear in bold. Any
other properties (not in bold) are considered optional. The table also
indicates any default values.NameDefault ValueAllowable
ValuesDescriptionSource TypeThe component type name for the
source. For some sources, this is a short, symbolic name (e.g. spooldir). For
others, it's the fully-qualified name of the Source class.
svn commit: r1834461 [7/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache.
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-elasticsearch-5-nar/1.7.0/org.apache.nifi.processors.elasticsearch.PutElasticsearch5/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-elasticsearch-5-nar/1.7.0/org.apache.nifi.processors.elasticsearch.PutElasticsearch5/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-elasticsearch-5-nar/1.7.0/org.apache.nifi.processors.elasticsearch.PutElasticsearch5/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-elasticsearch-5-nar/1.7.0/org.apache.nifi.processors.elasticsearch.PutElasticsearch5/index.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1 @@
+PutElasticsearch5window.onload =
function(){if(self==top) { document.getElementById('nameHeader').style.display
= "inherit"; } }PutElasticsearch5Description: Writes the contents of a
FlowFile to Elasticsearch, using the specified parameters such as the index to
insert into and the type of the document. If the cluster has been configured
for authorization and/or secure transport (SSL/TLS), and the X-Pack plugin is
available, secure connections can be made. This processor supports
Elasticsearch 5.x clusters.Tags: elasticsearch, elasticsearch
5, insert, update, write, putProperties: In the list below, the
names of required properties appear in bold. Any oth
er properties (not in bold) are considered optional. The table also indicates
any default values, whether a property supports the NiFi Expression
Language, 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 nifi.properties file has an entry for the
property nifi.sensitive.props.key.NameDefault ValueAllowable
ValuesDescriptionCluster
NameelasticsearchName of the ES cluster (for
example, elasticsearch_brew). Defaults to 'elasticsearch'Supports
Expression Language: true (will be evaluated using variable registry
only)ElasticSearch HostsElasticSearch Hosts, which should be comma separated and colon
for hostname/port host1:port,host2:port, For example testcluster:9300.
This processor uses the Transport Client to connect to hosts. The default
transport client port is 9300.Supports Expression Language: true
(will be evaluated using variable registry only)SSL Context ServiceController Service API:
SSLContextServiceImplementations: StandardRestrictedSSLContextServiceStandardSSLContextServiceThe SSL Context Ser
vice used to provide client certificate information for TLS/SSL connections.
This service only applies if the Elasticsearch endpoint(s) have been secured
with TLS/SSL.X-Pack Transport LocationSpecifies the path to the JAR(s) for the Elasticsearch X-Pack
Transport feature. If the Elasticsearch cluster has been secured with the
X-Pack plugin, then the X-Pack Transport JARs must also be available to this
processor. Note: Do NOT place the X-Pack JARs into NiFi's lib/ directory, doing
so will prevent the X-Pack Transport JARs from being
loaded.Supports Expression Language: true (will be evaluated using
variable registry only)UsernameUsername to access the Elasticsearch
clusterSupports Expression Language: true (will be evaluated us
ing variable registry only)PasswordPassword to access the
Elasticsearch clusterSensitive Property:
trueElasticSearch Ping
Timeout5sThe ping timeout used to
determine when a node is unreachable. For example, 5s (5 seconds). If non-local
recommended is 30sSupports Expression Language: true (will be
evaluated using variable registry only)Sampler Interval5sHow often to sample / ping the nodes listed and connected. For
example, 5s (5 seconds). If non-local recommended is 30s.Supports
Expression Language: true (will be evaluated using variable registry only)
Identifier
AttributeThe name of the attribute
containing the identifier for each FlowFileIndexThe name of the index to insert
intoSupports Expression Language: true (will be evaluated using
flow file attributes and variable registry)TypeThe type of this document (used
by Elasticsearch for indexing and searching)Supports Expression
Language: true (will be evaluated using flow file attributes and variable
registry)Character
SetUTF-8Specifies the character set of the document
data.Supports Expression Language: true (will be evaluated using
flow file attributes and variable registry)Batch Size100The preferred number of
FlowFiles to put to the database in a single transactionSupports
Expression Language: true (will be evaluated using variable registry
only)Index
OperationindexThe type of the operation used
to index (index, update, upsert)Supports Expression Language: true
(will be evaluated using flow file attributes and variable
registry)Relationships: NameDescriptionretryA
FlowFile is r
outed to this
svn commit: r1834461 [40/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache
Modified: nifi/site/trunk/docs/nifi-docs/index.html URL: http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/index.html?rev=1834461=1834460=1834461=diff == --- nifi/site/trunk/docs/nifi-docs/index.html (original) +++ nifi/site/trunk/docs/nifi-docs/index.html Wed Jun 27 00:37:46 2018 @@ -63,13 +63,13 @@ org.apache.nifi nifi-stateful-analysis-nar -1.6.0 +1.7.0 org.apache.nifi.processors.stateful.analysis.AttributeRollingWindow - + - AttributeRollingWindow 1.6.0 + AttributeRollingWindow 1.7.0 @@ -80,13 +80,30 @@ org.apache.nifi nifi-standard-nar -1.6.0 +1.7.0 +org.apache.nifi.processors.standard.AttributesToCSV + + + + +AttributesToCSV 1.7.0 + + + + + + + + +org.apache.nifi +nifi-standard-nar +1.7.0 org.apache.nifi.processors.standard.AttributesToJSON - + -AttributesToJSON 1.6.0 +AttributesToJSON 1.7.0 @@ -97,13 +114,30 @@ org.apache.nifi nifi-standard-nar -1.6.0 +1.7.0 org.apache.nifi.processors.standard.Base64EncodeContent - + + + + + Base64EncodeContent 1.7.0 + + + + + + + + +org.apache.nifi +nifi-standard-nar +1.7.0 +org.apache.nifi.processors.standard.CalculateRecordStats +
svn commit: r1834461 [2/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache.
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache.nifi.reporting.ambari.AmbariReportingTask/additionalDetails.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache.nifi.reporting.ambari.AmbariReportingTask/additionalDetails.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache.nifi.reporting.ambari.AmbariReportingTask/additionalDetails.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache.nifi.reporting.ambari.AmbariReportingTask/additionalDetails.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1,57 @@
+
+
+
+
+
+AmbariReportingTask
+
+
+
+
+AmbariReportingTask
+
+This ReportingTask sends the following metrics to Ambari:
+
+FlowFilesReceivedLast5Minutes
+BytesReceivedLast5Minutes
+FlowFilesSentLast5Minutes
+BytesSentLast5Minutes
+FlowFilesQueued
+BytesQueued
+BytesReadLast5Minutes
+BytesWrittenLast5Minutes
+ActiveThreads
+TotalTaskDurationSeconds
+jvm.uptime
+jvm.heap_used
+jvm.heap_usage
+jvm.non_heap_usage
+jvm.thread_states.runnable
+jvm.thread_states.blocked
+jvm.thread_states.timed_waiting
+jvm.thread_states.terminated
+jvm.thread_count
+jvm.daemon_thread_count
+jvm.file_descriptor_usage
+jvm.gc.runs
+jvm.gc.time
+
+
+In order to make use of these metrics in Ambari, a NIFI service
must be created and installed
+in Ambari. Please consult the Ambari and NiFi documentation for
further details.
+
+
+
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache.nifi.reporting.ambari.AmbariReportingTask/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache.nifi.reporting.ambari.AmbariReportingTask/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache.nifi.reporting.ambari.AmbariReportingTask/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache.nifi.reporting.ambari.AmbariReportingTask/index.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1 @@
+AmbariReportingTaskwindow.onload =
function(){if(self==top) { document.getElementById('nameHeader').style.display
= "inherit"; } }AmbariReportingTaskDescription: Publishes metrics from
NiFi to Ambari Metrics Service (AMS). Due to how the Ambari Metrics Service
works, this reporting task should be scheduled to run every 60 seconds. Each
iteration it will send the metrics from the previous iteration, and calculate
the current metrics to be sent on next iteration. Scheduling this reporting
task at a frequency other than 60 seconds may produce unexpected
results.Additional
Details...Tags: reporting, ambari,
metricsProperties: In th
e list below, the names of required properties appear in
bold. Any other properties (not in bold) are considered
optional. The table also indicates any default values, and whether a property
supports the NiFi
Expression Language.NameDefault
ValueAllowable ValuesDescriptionMetrics Collector URLhttp://localhost:6188/ws/v1/timeline/metricsThe URL of the Ambari Metrics
Collector ServiceSupports Expression Language: true (will be
evaluated using variable registry only)Application IDnifiThe Application ID to be included in the metrics sent to
AmbariSupports
Expression Language: true (will be evaluated using variable registry
only)Hostname${hostname(true)}The Hostname of this NiFi instance to be included in the
metrics sent to AmbariSupports Expression Language: true (will be
evaluated using variable registry only)Process Group IDIf specified, the reporting
task will send metrics about this process group only. If not, the root process
group is used and global metrics are sent.Supports Expression
Language: true (will be evaluated using variable registry
only)State management: This component does
not store state.Restricted: This component is not
restricted.System Resource Considerations:None specified.
\ No newline at end of file
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-amqp-nar/1.7.0/org.apache.nifi.amqp.processors.ConsumeAMQP/additionalDetails.html
URL:
svn commit: r1834461 [33/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.PartitionRecord/index.html
URL:
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.PartitionRecord/index.html?rev=1834461=auto
==
---
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.PartitionRecord/index.html
(added)
+++
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.PartitionRecord/index.html
Wed Jun 27 00:37:46 2018
@@ -0,0 +1 @@
+PartitionRecordwindow.onload =
function(){if(self==top) { document.getElementById('nameHeader').style.display
= "inherit"; } }PartitionRecordDescription: Receives Record-oriented
data (i.e., data that can be read by the configured Record Reader) and
evaluates one or more RecordPaths against the each record in the incoming
FlowFile. Each record is then grouped with other "like records" and a FlowFile
is created for each group of "like records." What it means for two records to
be "like records" is determined by user-defined properties. The user is
required to enter at least one user-defined property whose value is a
RecordPath. Two records are considered alike if they have the same value for
all configu
red RecordPaths. Because we know that all records in a given output FlowFile
have the same value for the fields that are specified by the RecordPath, an
attribute is added for each field. See Additional Details on the Usage page for
more information and examples.Additional Details...Tags:
record, partition, recordpath, rpath, segment, split, group, bin,
organizeProperties: In the list below, the names of required
properties appear in bold. Any other properties (not in bold)
are considered optional. The table also indicates any default values.NameDefault ValueAllowable
ValuesDescriptionRecord
ReaderController Service API:
RecordReaderFactoryImplementations: ScriptedReaderGrokReaderJsonPathReaderJsonTreeReaderAvroReaderXMLReaderCSVReaderSpecifies the Controller Service to use for reading incoming
dataRecord WriterController Service API:
RecordSetWriterFactoryImplementations: AvroRecordSetWriterCSVRecordSetWriterFreeFormTextRecordSetWriterJsonRecordSetWriterScriptedRecordSetWriterXMLRecordSetWriterSpecifies
the Controller Service to use for writing out the
recordsDynamic Properties: Dynamic Properties
allow the user to specify both the name and value of a property.NameValueDescriptionThe name given to the dynamic property is the name of the attribute
that will be used to denote the value of the associted RecordPath.A RecordPath that points to a field in the Record.Each
dynamic property represents a RecordPath that will be evaluated against each
record in an incoming FlowFile. When the value of the RecordPath is determined
for a Record, an attribute is added to the outgoing FlowFile. The name of the
attribute is the same as the name of this property. The value of the attribute
is the same as the value of the field in the Record that the RecordPath points
to. Note that
no attribute will be added if the value returned for the RecordPath is null or
is not a scalar value (i.e., the value is an Array, Map, or
Record).Supports Expression Language: true (will be evaluated
using flow file attributes and variable
registry)Relationships: NameDescriptionsuccessFlowFiles
that are successfully partitioned will be routed to this
relationshipfailureIf a FlowFile cannot be
partitioned from the configured input format to the configured output format,
the unchanged FlowFile will be routed to this
relationshiporiginalOnce all records in an incoming
FlowFile have been partitioned, the original FlowFile is routed to this
relationship.Reads Attributes: None
specified.Writes Attributes: NameDescriptionrecord.countThe number of records in an outgoing
FlowFilemime.typeThe MIME Type that the configured
Record Writer indicates is appropriatedynamic property
nameFor each dynamic property that is added, an attribute may be
added to the FlowFile. See the description for Dynamic Properties for more
information.State management: This component does
not store state.Restricted: This component is not restricted.Input
requirement: This component requires an incoming relationship.System
Resource Considerations:None specified.See Also:ConvertRecord,
SplitRecord,
UpdateRecord,
QueryRecord
\ No newline at end of file
Added:
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.7.0/org.apache.nifi.processors.standard.PostHTTP/index.html
URL:
svn commit: r1834461 [21/42] - in /nifi/site/trunk/docs: ./ nifi-docs/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/ nifi-docs/components/org.apache.nifi/nifi-ambari-nar/1.7.0/org.apache
Added: nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-record-serialization-services-nar/1.7.0/org.apache.nifi.grok.GrokReader/additionalDetails.html URL: http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-record-serialization-services-nar/1.7.0/org.apache.nifi.grok.GrokReader/additionalDetails.html?rev=1834461&view=auto == --- nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-record-serialization-services-nar/1.7.0/org.apache.nifi.grok.GrokReader/additionalDetails.html (added) +++ nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-record-serialization-services-nar/1.7.0/org.apache.nifi.grok.GrokReader/additionalDetails.html Wed Jun 27 00:37:46 2018 @@ -0,0 +1,405 @@ + + + + + +GrokReader + + + + ++ The GrokReader Controller Service provides a means for parsing and structuring input that is + made up of unstructured text, such as log files. Grok allows users to add a naming construct to + Regular Expressions such that they can be composed in order to create expressions that are easier + to manage and work with. This Controller Service consists of one Required Property and a few Optional + Properties. The is named
+ +Grok Pattern Fileproperty specifies the filename of + a file that contains Grok Patterns that can be used for parsing log data. If not specified, a default + patterns file will be used. Its contents are provided below. There are also properties for specifying + the schema to use when parsing data. The schema is not required. However, when data is parsed + a Record is created that contains all of the fields present in the Grok Expression (explained below), + and all fields are of type String. If a schema is chosen, the field can be declared to be a different, + compatible type, such as number. Additionally, if the schema does not contain one of the fields in the + parsed data, that field will be ignored. This can be used to filter out fields that are not of interest. ++ The Required Property is named
+ +Grok Expressionand specifies how to parse each + incoming record. This is done by providing a Grok Expression such as: +%{TIMESTAMP_ISO8601:timestamp} %{LOGLEVEL:level} \[%{DATA:thread}\] %{DATA:class} %{GREEDYDATA:message}. + This Expression will parse Apache NiFi log messages. This is accomplished by specifying that a line begins + with theTIMESTAMP_ISO8601pattern (which is a Regular Expression defined in the default + Grok Patterns File). The value that matches this pattern is then given the nametimestamp. As a result, + the value that matches this pattern will be assigned to a field namedtimestampin the Record that + produced by this Controller Service. ++ If a line is encountered in the FlowFile that does not match the configured Grok Expression, it is assumed that the line + is part of the previous message. If the line is the start of a stack trace, then the entire stack trace is read in and assigned + to a field named
STACK_TRACE. Otherwise,
svn commit: r1834460 - in /nifi/site/trunk: ./ minifi/
Author: alopresto Date: Tue Jun 26 23:28:44 2018 New Revision: 1834460 URL: http://svn.apache.org/viewvc?rev=1834460=rev Log: Changed copyright year to 2018. Modified: nifi/site/trunk/developer-guide.html nifi/site/trunk/docs.html nifi/site/trunk/download.html nifi/site/trunk/faq.html nifi/site/trunk/fds-release-guide.html nifi/site/trunk/fds.html nifi/site/trunk/index.html nifi/site/trunk/licensing-guide.html nifi/site/trunk/mailing_lists.html nifi/site/trunk/minifi/download.html nifi/site/trunk/minifi/faq.html nifi/site/trunk/minifi/getting-started.html nifi/site/trunk/minifi/index.html nifi/site/trunk/minifi/minifi-java-agent-quick-start.html nifi/site/trunk/minifi/minifi-toolkit.html nifi/site/trunk/minifi/system-admin-guide.html nifi/site/trunk/people.html nifi/site/trunk/powered-by-nifi.html nifi/site/trunk/quickstart.html nifi/site/trunk/registry.html nifi/site/trunk/release-guide.html nifi/site/trunk/security.html nifi/site/trunk/videos.html Modified: nifi/site/trunk/developer-guide.html URL: http://svn.apache.org/viewvc/nifi/site/trunk/developer-guide.html?rev=1834460=1834459=1834460=diff == --- nifi/site/trunk/developer-guide.html (original) +++ nifi/site/trunk/developer-guide.html Tue Jun 26 23:28:44 2018 @@ -117,7 +117,7 @@ https://www.apache.org/events/current-event-234x60.png; style="margin:0px 10px" /> -Copyright 2017 The Apache Software Foundation, Licensed under the Copyright 2018 The Apache Software Foundation, Licensed under the https://www.apache.org/licenses/LICENSE-2.0;>Apache License, Version 2.0.Apache, the Apache feather logo, NiFi, Apache NiFi and the project logo are trademarks of The Apache Software Foundation. Modified: nifi/site/trunk/docs.html URL: http://svn.apache.org/viewvc/nifi/site/trunk/docs.html?rev=1834460=1834459=1834460=diff == --- nifi/site/trunk/docs.html (original) +++ nifi/site/trunk/docs.html Tue Jun 26 23:28:44 2018 @@ -117,7 +117,7 @@ https://www.apache.org/events/current-event-234x60.png; style="margin:0px 10px" /> -Copyright 2017 The Apache Software Foundation, Licensed under the Copyright 2018 The Apache Software Foundation, Licensed under the https://www.apache.org/licenses/LICENSE-2.0;>Apache License, Version 2.0.Apache, the Apache feather logo, NiFi, Apache NiFi and the project logo are trademarks of The Apache Software Foundation. Modified: nifi/site/trunk/download.html URL: http://svn.apache.org/viewvc/nifi/site/trunk/download.html?rev=1834460=1834459=1834460=diff == --- nifi/site/trunk/download.html (original) +++ nifi/site/trunk/download.html Tue Jun 26 23:28:44 2018 @@ -199,7 +199,7 @@ https://www.apache.org/events/current-event-234x60.png; style="margin:0px 10px" /> -Copyright 2017 The Apache Software Foundation, Licensed under the Copyright 2018 The Apache Software Foundation, Licensed under the https://www.apache.org/licenses/LICENSE-2.0;>Apache License, Version 2.0.Apache, the Apache feather logo, NiFi, Apache NiFi and the project logo are trademarks of The Apache Software Foundation. Modified: nifi/site/trunk/faq.html URL: http://svn.apache.org/viewvc/nifi/site/trunk/faq.html?rev=1834460=1834459=1834460=diff == --- nifi/site/trunk/faq.html (original) +++ nifi/site/trunk/faq.html Tue Jun 26 23:28:44 2018 @@ -148,7 +148,7 @@ https://www.apache.org/events/current-event-234x60.png; style="margin:0px 10px" /> -Copyright 2017 The Apache Software Foundation, Licensed under the Copyright 2018 The Apache Software Foundation, Licensed under the https://www.apache.org/licenses/LICENSE-2.0;>Apache License, Version 2.0.Apache, the Apache feather logo, NiFi, Apache NiFi and the project logo are trademarks of The Apache Software Foundation. Modified: nifi/site/trunk/fds-release-guide.html URL: http://svn.apache.org/viewvc/nifi/site/trunk/fds-release-guide.html?rev=1834460=1834459=1834460=diff == --- nifi/site/trunk/fds-release-guide.html (original) +++ nifi/site/trunk/fds-release-guide.html Tue Jun 26 23:28:44 2018 @@ -516,7 +516,7 @@ The Apache NiFi team
[jira] [Commented] (MINIFI-450) PullHttpChangeIngestor needs to properly close OkHttp response
[ https://issues.apache.org/jira/browse/MINIFI-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524123#comment-16524123 ] ASF GitHub Bot commented on MINIFI-450: --- Github user asfgit closed the pull request at: https://github.com/apache/nifi-minifi/pull/129 > PullHttpChangeIngestor needs to properly close OkHttp response > --- > > Key: MINIFI-450 > URL: https://issues.apache.org/jira/browse/MINIFI-450 > Project: Apache NiFi MiNiFi > Issue Type: Bug >Reporter: Joseph Percivall >Assignee: Aldrin Piri >Priority: Major > Fix For: 0.5.0 > > > Same as NIFI-5085 and NIFI-5086, PullHttpChangeIngestor does not close the > response as it should[1] > > [1] > https://github.com/apache/nifi-minifi/blob/master/minifi-bootstrap/src/main/java/org/apache/nifi/minifi/bootstrap/configuration/ingestors/PullHttpChangeIngestor.java#L253 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[nifi-minifi] Git Push Summary
Repository: nifi-minifi Updated Tags: refs/tags/nifi-minifi-0.5.0-RC1 [created] f5c15eb6e
[nifi-minifi] Git Push Summary
Repository: nifi-minifi Updated Branches: refs/heads/MINIFI-458-RC1 [created] 7bac01ee1
nifi-minifi git commit: MINIFI-450 Handling closing of HTTP response in PullHttpChangeIngestor.
Repository: nifi-minifi
Updated Branches:
refs/heads/master ec6227246 -> 7bac01ee1
MINIFI-450 Handling closing of HTTP response in PullHttpChangeIngestor.
This closes #129
Signed-off-by: Jeremy Dyer
Project: http://git-wip-us.apache.org/repos/asf/nifi-minifi/repo
Commit: http://git-wip-us.apache.org/repos/asf/nifi-minifi/commit/7bac01ee
Tree: http://git-wip-us.apache.org/repos/asf/nifi-minifi/tree/7bac01ee
Diff: http://git-wip-us.apache.org/repos/asf/nifi-minifi/diff/7bac01ee
Branch: refs/heads/master
Commit: 7bac01ee1758da618974851af99c6dd72a5c4689
Parents: ec62272
Author: Aldrin Piri
Authored: Mon Jun 4 14:18:15 2018 -0400
Committer: Jeremy Dyer
Committed: Tue Jun 26 12:39:46 2018 -0400
--
.../ingestors/PullHttpChangeIngestor.java | 60 +---
1 file changed, 27 insertions(+), 33 deletions(-)
--
http://git-wip-us.apache.org/repos/asf/nifi-minifi/blob/7bac01ee/minifi-bootstrap/src/main/java/org/apache/nifi/minifi/bootstrap/configuration/ingestors/PullHttpChangeIngestor.java
--
diff --git
a/minifi-bootstrap/src/main/java/org/apache/nifi/minifi/bootstrap/configuration/ingestors/PullHttpChangeIngestor.java
b/minifi-bootstrap/src/main/java/org/apache/nifi/minifi/bootstrap/configuration/ingestors/PullHttpChangeIngestor.java
index f7add36..f363dcd 100644
---
a/minifi-bootstrap/src/main/java/org/apache/nifi/minifi/bootstrap/configuration/ingestors/PullHttpChangeIngestor.java
+++
b/minifi-bootstrap/src/main/java/org/apache/nifi/minifi/bootstrap/configuration/ingestors/PullHttpChangeIngestor.java
@@ -17,7 +17,6 @@
package org.apache.nifi.minifi.bootstrap.configuration.ingestors;
-import okhttp3.Call;
import okhttp3.Credentials;
import okhttp3.HttpUrl;
import okhttp3.OkHttpClient;
@@ -44,7 +43,6 @@ import javax.net.ssl.SSLSocketFactory;
import javax.net.ssl.TrustManager;
import javax.net.ssl.TrustManagerFactory;
import javax.net.ssl.X509TrustManager;
-
import java.io.File;
import java.io.FileInputStream;
import java.io.IOException;
@@ -148,7 +146,7 @@ public class PullHttpChangeIngestor extends
AbstractPullChangeIngestor {
queryReference.set(query);
final String useEtagString = (String)
properties.getOrDefault(USE_ETAG_KEY, "false");
-if ("true".equalsIgnoreCase(useEtagString) ||
"false".equalsIgnoreCase(useEtagString)){
+if ("true".equalsIgnoreCase(useEtagString) ||
"false".equalsIgnoreCase(useEtagString)) {
useEtag = Boolean.parseBoolean(useEtagString);
} else {
throw new IllegalArgumentException("Property, " + USE_ETAG_KEY +
", to specify whether to use the ETag header, must either be a value boolean
value (\"true\" or \"false\") or left to " +
@@ -156,7 +154,7 @@ public class PullHttpChangeIngestor extends
AbstractPullChangeIngestor {
}
final String overrideSecurityProperties = (String)
properties.getOrDefault(OVERRIDE_SECURITY, "false");
-if ("true".equalsIgnoreCase(overrideSecurityProperties) ||
"false".equalsIgnoreCase(overrideSecurityProperties)){
+if ("true".equalsIgnoreCase(overrideSecurityProperties) ||
"false".equalsIgnoreCase(overrideSecurityProperties)) {
overrideSecurity =
Boolean.parseBoolean(overrideSecurityProperties);
} else {
throw new IllegalArgumentException("Property, " +
OVERRIDE_SECURITY + ", to specify whether to override security properties must
either be a value boolean value (\"true\" or \"false\")" +
@@ -222,36 +220,31 @@ public class PullHttpChangeIngestor extends
AbstractPullChangeIngestor {
@Override
public void run() {
-try {
-logger.debug("Attempting to pull new config");
-HttpUrl.Builder builder = new HttpUrl.Builder()
-.host(hostReference.get())
-.port(portReference.get())
-.encodedPath(pathReference.get());
-String query = queryReference.get();
-if (!StringUtil.isNullOrEmpty(query)) {
-builder = builder.encodedQuery(query);
-}
-final HttpUrl url = builder
-.scheme(connectionScheme)
-.build();
-
-
-final Request.Builder requestBuilder = new Request.Builder()
-.get()
-.url(url);
-
-if (useEtag) {
-requestBuilder.addHeader("If-None-Match", lastEtag);
-}
+logger.debug("Attempting to pull new config");
+HttpUrl.Builder builder = new HttpUrl.Builder()
+.host(hostReference.get())
+.port(portReference.get())
+.encodedPath(pathReference.get());
+final String query = queryReference.get();
+if
[jira] [Commented] (MINIFI-459) Upgrade NiFi dependencies to 1.7.0
[ https://issues.apache.org/jira/browse/MINIFI-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523949#comment-16523949 ] ASF GitHub Bot commented on MINIFI-459: --- Github user asfgit closed the pull request at: https://github.com/apache/nifi-minifi/pull/131 > Upgrade NiFi dependencies to 1.7.0 > -- > > Key: MINIFI-459 > URL: https://issues.apache.org/jira/browse/MINIFI-459 > Project: Apache NiFi MiNiFi > Issue Type: Task >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Blocker > Fix For: 0.5.0 > > > Once NiFi 1.7.0 is successfully released we should integrate this new version > into MiNiFi before starting the 0.5.0 release process. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
nifi git commit: NIFI-5336: Exclude hbase-server from Hive 3 bundle
Repository: nifi Updated Branches: refs/heads/master a274918dc -> 921403ff5 NIFI-5336: Exclude hbase-server from Hive 3 bundle This closes #2811 Signed-off-by: Mike Thomsen Project: http://git-wip-us.apache.org/repos/asf/nifi/repo Commit: http://git-wip-us.apache.org/repos/asf/nifi/commit/921403ff Tree: http://git-wip-us.apache.org/repos/asf/nifi/tree/921403ff Diff: http://git-wip-us.apache.org/repos/asf/nifi/diff/921403ff Branch: refs/heads/master Commit: 921403ff558a7922210db6107ff33dff4c879483 Parents: a274918 Author: Matthew Burgess Authored: Mon Jun 25 15:07:05 2018 -0400 Committer: Mike Thomsen Committed: Tue Jun 26 05:33:07 2018 -0400 -- nifi-nar-bundles/nifi-hive-bundle/nifi-hive3-processors/pom.xml | 4 1 file changed, 4 insertions(+) -- http://git-wip-us.apache.org/repos/asf/nifi/blob/921403ff/nifi-nar-bundles/nifi-hive-bundle/nifi-hive3-processors/pom.xml -- diff --git a/nifi-nar-bundles/nifi-hive-bundle/nifi-hive3-processors/pom.xml b/nifi-nar-bundles/nifi-hive-bundle/nifi-hive3-processors/pom.xml index e4b218a..f213b47 100644 --- a/nifi-nar-bundles/nifi-hive-bundle/nifi-hive3-processors/pom.xml +++ b/nifi-nar-bundles/nifi-hive-bundle/nifi-hive3-processors/pom.xml @@ -80,6 +80,10 @@ org.json json + +org.apache.hbase +hbase-server +
