Processors

Table of Contents

AppendHostInfo

Description

Appends host information such as IP address and hostname as an attribute to incoming flowfiles.

Properties

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
Hostname Attributesource.hostnameFlowfile attribute to used to record the agent's hostname
IP Attributesource.ipv4Flowfile attribute to used to record the agent's IP address
Network Interface Nameeth0Network interface from which to read an IP v4 address

Relationships

NameDescription
successsuccess operational on the flow record

ApplyTemplate

Description

Applies the mustache template specified by the “Template” property and writes the output to the flow file content. FlowFile attributes are used as template parameters.

Properties

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
TemplatePath to the input mustache template file

Relationships

NameDescription
successsuccess operational on the flow record

BinFiles

Description

Bins flow files into buckets based on the number of entries or size of entries

Properties

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
Max Bin AgeThe maximum age of a Bin that will trigger a Bin to be complete. Expected format is
Maximum Group SizeThe maximum size for the bundle. If not specified, there is no maximum.
Maximum Number of EntriesThe maximum number of files to include in a bundle. If not specified, there is no maximum.
Maximum number of Bins100Specifies the maximum number of bins that can be held in memory at any one time
Minimum Group Size0The minimum size of for the bundle
Minimum Number of Entries1The minimum number of files to include in a bundle

Relationships

NameDescription
failureIf the bundle cannot be created, all FlowFiles that would have been used to create the bundle will be transferred to failure
originalThe FlowFiles that were used to create the bundle

CapturePacket

Description

CapturePacket captures and writes one or more packets into a PCAP file that will be used as the content of a flow file. Configuration options exist to adjust the batching of PCAP files. PCAP batching will place a single PCAP into a flow file. A regular expression selects network interfaces. Bluetooth network interfaces can be selected through a separate option.

Properties

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
Base Directory/tmp/Scratch directory for PCAP files
Batch Size50The number of packets to combine within a given PCAP
Capture BluetoothfalseTrue indicates that we support bluetooth interfaces
Network Controllers.*Regular expression of the network controller(s) to which we will attach

Relationships

NameDescription
successAll files are routed to success

CaptureRTSPFrame

Description

Captures a frame from the RTSP stream at specified intervals.

Properties

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
Image Encoding.jpgThe encoding that should be applied the the frame images captured from the RTSP stream
RTSP HostnameHostname of the RTSP stream we are trying to connect to
RTSP PasswordPassword used to connect to the RTSP stream
RTSP PortPort that should be connected to to receive RTSP Frames
RTSP URIURI that should be appended to the RTSP stream hostname
RTSP UsernameThe username for connecting to the RTSP stream

Relationships

NameDescription
failureFailures to capture RTSP frame
successSuccessful capture of RTSP frame

CompressContent

Description

Compresses or decompresses the contents of FlowFiles using a user-specified compression algorithm and updates the mime.type attribute as appropriate

Properties

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
Compression Formatuse mime.type attributeThe compression format to use.
Compression Level1The compression level to use; this is valid only when using GZIP compression.
ModecompressIndicates whether the processor should compress content or decompress content.
Update FilenamefalseDetermines if filename extension need to be updated

Relationships

NameDescription
failureFlowFiles will be transferred to the failure relationship if they fail to compress/decompress
successFlowFiles will be transferred to the success relationship after successfully being compressed or decompressed

ConsumeKafka

Description

Consumes messages from Apache Kafka and transform them into MiNiFi FlowFiles. The application should make sure that the processor is triggered at regular intervals, even if no messages are expected, to serve any queued callbacks waiting to be called. Rebalancing can also only happen on trigger.

Properties

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
Duplicate Header HandlingKeep LatestComma-separated Merge
Keep First
Keep Latest
For headers to be added as attributes, this option specifies how to handle cases where multiple headers are present with the same key. For example in case of receiving these two headers: “Accept: text/html” and “Accept: application/xml” and we want to attach the value of “Accept” as a FlowFile attribute:
- “Keep First” attaches: “Accept -> text/html”
- “Keep Latest” attaches: “Accept -> application/xml”
- “Comma-separated Merge” attaches: “Accept -> text/html, application/xml”
Group IDA Group ID is used to identify consumers that are within the same consumer group. Corresponds to Kafka's ‘group.id’ property.
Supports Expression Language: true
Headers To Add As AttributesA comma separated list to match against all message headers. Any message header whose name matches an item from the list will be added to the FlowFile as an Attribute. If not specified, no Header values will be added as FlowFile attributes. The behaviour on when multiple headers of the same name are present is set using the DuplicateHeaderHandling attribute.
Honor TransactionstrueSpecifies whether or not MiNiFi 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, MiNiFi 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.
Kafka Brokerslocalhost:9092A comma-separated list of known Kafka Brokers in the format :.
Supports Expression Language: true
Key Attribute EncodingUTF-8Hex
UTF-8
FlowFiles that are emitted have an attribute named ‘kafka.key’. This property dictates how the value of the attribute should be encoded.
Max Poll Records10000Specifies the maximum number of records Kafka should return when polling each time the processor is triggered.
Max Poll Time4 secondsSpecifies the maximum amount of time the consumer can use for polling data from the brokers. Polling is a blocking operation, so the upper limit of this value is specified in 4 seconds.
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.
Supports Expression Language: true
Message Header EncodingUTF-8Hex
UTF-8
Any message header that is found on a Kafka message will be added to the outbound FlowFile as an attribute. This property indicates the Character Encoding to use for deserializing the headers.
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.
Security ProtocolPLAINTEXTPLAINTEXT
This property is currently not supported. Protocol used to communicate with brokers. Corresponds to Kafka's ‘security.protocol’ property.
Session Timeout60 secondsClient group session and failure detection timeout. The consumer sends periodic heartbeats to indicate its liveness to the broker. If no hearts are received by the broker for a group member within the session timeout, the broker will remove the consumer from the group and trigger a rebalance. The allowed range is configured with the broker configuration properties group.min.session.timeout.ms and group.max.session.timeout.ms.
Topic Name FormatNamesNames
Patterns
Specifies whether the Topic(s) provided are a comma separated list of names or a single regular expression.
Topic NamesThe name of the Kafka Topic(s) to pull from. Multiple topic names are supported as a comma separated list.
Supports Expression Language: true

Properties

NameDescription
successIncoming kafka messages as flowfiles. Depending on the demarcation strategy, this can be one or multiple flowfiles per message.

ConsumeMQTT

Description

This Processor gets the contents of a FlowFile from a MQTT broker for a specified topic. The the payload of the MQTT message becomes content of a FlowFile

Properties

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
Broker URIThe URI to use to connect to the MQTT broker
Client IDMQTT client ID to use
Connection Timeout30 secMaximum time interval the client will wait for the network connection to the MQTT server
Keep Alive Interval60 secDefines the maximum time interval between messages sent or received
Max Flow Segment SizeMaximum flow content payload segment size for the MQTT record
PasswordPassword to use when connecting to the broker
Quality of ServiceMQTT_QOS_0The Quality of Service(QoS) to send the message with. Accepts three values ‘0’, ‘1’ and ‘2’
Queue Max MessageMaximum number of messages allowed on the received MQTT queue
Session statetrueWhether to start afresh or resume previous flows. See the allowable value descriptions for more details
TopicThe topic to publish the message to
UsernameUsername to use when connecting to the broker

Relationships

NameDescription
successFlowFiles that are sent successfully to the destination are transferred to this relationship

DeleteS3Object

Description

Deletes FlowFiles on an Amazon S3 Bucket. If attempting to delete a file that does not exist, FlowFile is routed to success.

Properties

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
Object KeyThe key of the S3 object. If none is given the filename attribute will be used by default.
Supports Expression Language: true
BucketThe S3 bucket
Supports Expression Language: true
Access KeyAWS account access key
Supports Expression Language: true
Secret KeyAWS account secret key
Supports Expression Language: true
Credentials FilePath to a file containing AWS access key and secret key in properties file format. Properties used: accessKey and secretKey
AWS Credentials Provider serviceThe name of the AWS Credentials Provider controller service that is used to obtain AWS credentials.
Regionus-west-2af-south-1
ap-east-1
ap-northeast-1
ap-northeast-2
ap-northeast-3
ap-south-1
ap-southeast-1
ap-southeast-2
ca-central-1
cn-north-1
cn-northwest-1
eu-central-1
eu-north-1
eu-south-1
eu-west-1
eu-west-2
eu-west-3
me-south-1
sa-east-1
us-east-1
us-east-2
us-gov-east-1
us-gov-west-1
us-west-1
us-west-2
AWS Region
Communications Timeout30 secSets the timeout of the communication between the AWS server and the client
Endpoint Override URLEndpoint URL to use instead of the AWS default including scheme, host, port, and path. The AWS libraries select an endpoint URL based on the AWS region, but this property overrides the selected endpoint URL, allowing use with other S3-compatible endpoints.
Supports Expression Language: true
Proxy HostProxy host name or IP
Supports Expression Language: true
Proxy PortThe port number of the proxy host
Supports Expression Language: true
Proxy UsernameUsername to set when authenticating against proxy
Supports Expression Language: true
Proxy PasswordPassword to set when authenticating against proxy
Supports Expression Language: true
VersionThe Version of the Object to delete
Supports Expression Language: true

Relationships

NameDescription
failureFlowFiles are routed to failure relationship
successFlowFiles are routed to success relationship

ExecuteProcess

Description

Runs an operating system command specified by the user and writes the output of that command to a FlowFile. If the command is expected to be long-running,the Processor can output the partial data on a specified interval. When this option is used, the output is expected to be in textual format,as it typically does not make sense to split binary data on arbitrary time-based intervals.

Properties

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
Batch Duration0 secIf the process is expected to be long-running and produce textual output, a batch duration can be specified.
CommandSpecifies the command to be executed; if just the name of an executable is provided, it must be in the user's environment PATH.
Supports Expression Language: true
Command ArgumentsThe arguments to supply to the executable delimited by white space. White space can be escaped by enclosing it in double-quotes.
Supports Expression Language: true
Redirect Error StreamfalseIf true will redirect any error stream output of the process to the output stream.
Working DirectoryThe directory to use as the current working directory when executing the command
Supports Expression Language: true

Relationships

NameDescription
successAll created FlowFiles are routed to this relationship.

ExecutePythonProcessor

Description

Executes a script given the flow file and a process session. The script is responsible for handling the incoming flow file (transfer to SUCCESS or remove, e.g.) as well as any flow files created by the script. If the handling is incomplete or incorrect, the session will be rolled back. Scripts must define an onTrigger function which accepts NiFi Context and Property objects. For efficiency, scripts are executed once when the processor is run, then the onTrigger method is called for each incoming flowfile. This enables scripts to keep state if they wish, although there will be a script context per concurrent task of the processor. In order to, e.g., compute an arithmetic sum based on incoming flow file information, set the concurrent tasks to 1. The python script files are expected to contain describe(procesor) and onTrigger(context, session).

Properties

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
Script FilePath to script file to execute. Only one of Script File or Script Body may be used
Script BodyScript to execute

Relationships

NameDescription
failureScript failures
successScript successes

ExecuteSQL

Description

Execute provided SQL query. Query result rows will be outputted as new flow files with attribute keys equal to result column names and values equal to result values. There will be one output FlowFile per result row. This processor can be scheduled to run using the standard timer-based scheduling methods, or it can be triggered by an incoming FlowFile. If it is triggered by an incoming FlowFile, then attributes of that FlowFile will be available when evaluating the query.

Properties

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
DB Controller ServiceDatabase Controller Service.
Max Rows Per Flow File0The maximum number of result rows that will be included in a single FlowFile. This will allow you to break up very large result sets into multiple FlowFiles. If the value specified is zero, then all rows are returned in a single FlowFile.
Output FormatJSON-PrettyJSON
JSON-Pretty
Set the output format type.
SQL select queryThe SQL select query to execute. The query 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 select query, to be issued by the processor to the database.

Relationships

NameDescription
successSuccessfully created FlowFile from SQL query result set.

ExecuteScript

Description

Executes a script given the flow file and a process session. The script is responsible for handling the incoming flow file (transfer to SUCCESS or remove, e.g.) as well as any flow files created by the script. If the handling is incomplete or incorrect, the session will be rolled back. Scripts must define an onTrigger function which accepts NiFi Context and Property objects. For efficiency, scripts are executed once when the processor is run, then the onTrigger method is called for each incoming flowfile. This enables scripts to keep state if they wish, although there will be a script context per concurrent task of the processor. In order to, e.g., compute an arithmetic sum based on incoming flow file information, set the concurrent tasks to 1.

Properties

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
Module DirectoryComma-separated list of paths to files and/or directories which contain modules required by the script
Script BodyBody of script to execute. Only one of Script File or Script Body may be used
Script EnginepythonThe engine to execute scripts (python, lua)
Script FilePath to script file to execute. Only one of Script File or Script Body may be used

Relationships

NameDescription
failureScript failures
successScript successes

ExtractText

Description

Extracts the content of a FlowFile and places it into an attribute.

Properties

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
AttributeAttribute to set from content
Enable Case-insensitive MatchingfalseIndicates that two characters match even if they are in a different case.
Enable repeating capture groupfalsef set to true, every string matching the capture groups will be extracted. Otherwise, if the Regular Expression matches more than once, only the first match will be extracted.
Include Capture Group 0trueIndicates 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 considerable length.
Maximum Capture Group Length1024Specifies the maximum number of characters a given capture group value can have. Any characters beyond the max will be truncated.
Regex ModefalseSet this to extract parts of flowfile content using regular experssions in dynamic properties
Size Limit2097152Maximum number of bytes to read into the attribute. 0 for no limit. Default is 2MB.

Relationships

NameDescription
successsuccess operational on the flow record

FetchOPCProcessor

Description

Fetches OPC-UA node

Properties

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
Application URIApplication URI of the client in the format ‘urn:unconfigured:application’. Mandatory, if using Secure Channel and must match the URI included in the certificate's Subject Alternative Names.
Certificate pathPath to the DER-encoded cert file
Key pathPath to the DER-encoded key file
Lazy modeOffOff
On
Only creates flowfiles from nodes with new timestamp from the server.
Max depth0Specifiec the max depth of browsing. 0 means unlimited.
Namespace index0The index of the namespace. Used only if node ID type is not path.
Node IDSpecifies the ID of the root node to traverse
Node ID typeInt
Path
String
Specifies the type of the provided node ID
OPC server endpointSpecifies the address, port and relative path of an OPC endpoint
PasswordPassword to log in with. Providing this requires cert and key to be provided as well, credentials are always sent encrypted.
Trusted server certificate pathPath to the DER-encoded trusted server certificate
UsernameUsername to log in with.

Relationships

NameDescription
failureRetrieved OPC-UA nodes where value cannot be extracted (only if enabled)
successSuccessfully retrieved OPC-UA nodes

FetchS3Object

Description

Retrieves the contents of an S3 Object and writes it to the content of a FlowFile

Properties

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
Object KeyThe key of the S3 object. If none is given the filename attribute will be used by default.
Supports Expression Language: true
BucketThe S3 bucket
Supports Expression Language: true
Access KeyAWS account access key
Supports Expression Language: true
Secret KeyAWS account secret key
Supports Expression Language: true
Credentials FilePath to a file containing AWS access key and secret key in properties file format. Properties used: accessKey and secretKey
AWS Credentials Provider serviceThe name of the AWS Credentials Provider controller service that is used to obtain AWS credentials.
Regionus-west-2af-south-1
ap-east-1
ap-northeast-1
ap-northeast-2
ap-northeast-3
ap-south-1
ap-southeast-1
ap-southeast-2
ca-central-1
cn-north-1
cn-northwest-1
eu-central-1
eu-north-1
eu-south-1
eu-west-1
eu-west-2
eu-west-3
me-south-1
sa-east-1
us-east-1
us-east-2
us-gov-east-1
us-gov-west-1
us-west-1
us-west-2
AWS Region
Communications Timeout30 secSets the timeout of the communication between the AWS server and the client
Endpoint Override URLEndpoint URL to use instead of the AWS default including scheme, host, port, and path. The AWS libraries select an endpoint URL based on the AWS region, but this property overrides the selected endpoint URL, allowing use with other S3-compatible endpoints.
Supports Expression Language: true
Proxy HostProxy host name or IP
Supports Expression Language: true
Proxy PortThe port number of the proxy host
Supports Expression Language: true
Proxy UsernameUsername to set when authenticating against proxy
Supports Expression Language: true
Proxy PasswordPassword to set when authenticating against proxy
Supports Expression Language: true
VersionThe Version of the Object to download
Supports Expression Language: true
Requester PaysfalseIf true, indicates that the requester consents to pay any charges associated with retrieving objects from the S3 bucket. This sets the ‘x-amz-request-payer’ header to ‘requester’.

Relationships

NameDescription
failureFlowFiles are routed to failure relationship
successFlowFiles are routed to success relationship

FetchSFTP

Description

Fetches the content of a file from a remote SFTP server and overwrites the contents of an incoming FlowFile with the content of the remote file.

Properties

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
Completion StrategyNoneDelete File
Move File
None
Specifies what to do with the original file on the server once it has been pulled into NiFi. If the Completion Strategy fails, a warning will be logged but the data will still be transferred.
Connection Timeout30 secAmount of time to wait before timing out while creating a connection
Create DirectoryfalseSpecifies whether or not the remote directory should be created if it does not exist.
Data Timeout30 secWhen transferring a file between the local and remote system, this value specifies how long is allowed to elapse without any data being transferred between systems
Disable Directory ListingfalseControl how ‘Move Destination Directory’ is created when ‘Completion Strategy’ is ‘Move File’ and ‘Create Directory’ is enabled. If set to ‘true’, directory listing is not performed prior to create missing directories. By default, this processor executes a directory listing command to see target directory existence before creating missing directories. However, there are situations that you might need to disable the directory listing such as the following. Directory listing might fail with some permission setups (e.g. chmod 100) on a directory. Also, if any other SFTP client created the directory after this processor performed a listing and before a directory creation request by this processor is finished, then an error is returned because the directory already exists.
Host Key FileIf supplied, the given file will be used as the Host Key; otherwise, no use host key file will be used
HostnameThe fully qualified hostname or IP address of the remote system
Supports Expression Language: true
Http Proxy PasswordHttp Proxy Password
Supports Expression Language: true
Http Proxy UsernameHttp Proxy Username
Supports Expression Language: true
Move Destination DirectoryThe directory on the remote server to move the original file to once it has been ingested into NiFi. This property is ignored unless the Completion Strategy is set to ‘Move File’. The specified directory must already exist on the remote system if ‘Create Directory’ is disabled, or the rename will fail.
Supports Expression Language: true
PasswordPassword for the user account
Supports Expression Language: true
PortThe port that the remote system is listening on for file transfers
Supports Expression Language: true
Private Key PassphrasePassword for the private key
Supports Expression Language: true
Private Key PathThe fully qualified path to the Private Key file
Supports Expression Language: true
Proxy HostThe fully qualified hostname or IP address of the proxy server
Supports Expression Language: true
Proxy PortThe port of the proxy server
Supports Expression Language: true
Proxy TypeDIRECTDIRECT
HTTP
SOCKS
Specifies the Proxy Configuration Controller Service to proxy network requests. If set, it supersedes proxy settings configured per component. Supported proxies: HTTP + AuthN, SOCKS + AuthN
Remote FileThe fully qualified filename on the remote system
Supports Expression Language: true
Send Keep Alive On TimeouttrueIndicates whether or not to send a single Keep Alive message when SSH socket times out
Strict Host Key CheckingfalseIndicates whether or not strict enforcement of hosts keys should be applied
Use CompressionfalseIndicates whether or not ZLIB compression should be used when transferring files
UsernameUsername
Supports Expression Language: true

Relationships

NameDescription
comms.failureAny FlowFile that could not be fetched from the remote server due to a communications failure will be transferred to this Relationship.
not.foundAny FlowFile for which we receive a ‘Not Found’ message from the remote server will be transferred to this Relationship.
permission.deniedAny FlowFile that could not be fetched from the remote server due to insufficient permissions will be transferred to this Relationship.
successAll FlowFiles that are received are routed to success

FocusArchiveEntry

Description

Allows manipulation of entries within an archive (e.g. TAR) by focusing on one entry within the archive at a time. When an archive entry is focused, that entry is treated as the content of the FlowFile and may be manipulated independently of the rest of the archive. To restore the FlowFile to its original state, use UnfocusArchiveEntry.

Properties

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
PathThe path within the archive to focus (“/” to focus the total archive)

Relationships

NameDescription
successsuccess operational on the flow record

GenerateFlowFile

Description

This processor creates FlowFiles with random data or custom content. GenerateFlowFile is useful for load testing, configuration, and simulation.

Properties

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
Batch Size1The number of FlowFiles to be transferred in each invocation
Data FormatBinaryText
Binary
Specifies whether the data should be Text or Binary
File Size1 kBThe size of the file that will be used
Unique FlowFilestrueIf true, each FlowFile that is generated will be unique. If false, a random value will be generated and all FlowFiles

Relationships

NameDescription
successsuccess operational on the flow record

GetFile

Description

Creates FlowFiles from files in a directory. MiNiFi will ignore files for which it doesn't have read permissions.

Properties

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
Batch Size10The maximum number of files to pull in each iteration
File Filter[^.].*Only files whose names match the given regular expression will be picked up
Ignore Hidden FilestrueIndicates whether or not hidden files should be ignored
Input DirectoryThe input directory from which to pull files
Supports Expression Language: true
Keep Source FilefalseIf true, the file is not deleted after it has been copied to the Content Repository
Maximum File Age0 secThe maximum age that a file must be in order to be pulled; any file older than this amount of time (according to last modification date) will be ignored
Maximum File Size0 BThe maximum size that a file can be in order to be pulled
Minimum File Age0 secThe minimum age that a file must be in order to be pulled; any file younger than this amount of time (according to last modification date) will be ignored
Minimum File Size0 BThe minimum size that a file can be in order to be pulled
Polling Interval0 secIndicates how long to wait before performing a directory listing
Recurse SubdirectoriestrueIndicates whether or not to pull files from subdirectories

Relationships

NameDescription
successAll files are routed to success

GetGPS

Description

Obtains GPS coordinates from the GPSDHost and port.

Properties

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
GPSD HostlocalhostThe host running the GPSD daemon
GPSD Port2947The GPSD daemon port
GPSD Wait Time50000000Timeout value for waiting for data from the GPSD instance

Relationships

NameDescription
successAll files are routed to success

GetTCP

Description

Establishes a TCP Server that defines and retrieves one or more byte messages from clients

Properties

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
SSL Context ServiceSSL Context Service Name
Stay ConnectedtrueDetermines if we keep the same socket despite having no data
concurrent-handler-count1Number of concurrent handlers for this session
connection-attempt-timeout3Maximum number of connection attempts before attempting backup hosts, if configured
end-of-message-byte13Byte value which denotes end of message. Must be specified as integer within the valid byte range (-128 thru 127). For example, ‘13’ = Carriage return and ‘10’ = New line. Default ‘13’.
endpoint-listA comma delimited list of the endpoints to connect to. The format should be <server_address>:.
receive-buffer-size16 MBThe size of the buffer to receive data in. Default 16384 (16MB).

Relationships

NameDescription
partialIndicates an incomplete message as a result of encountering the end of message byte trigger
successAll files are routed to success

GetUSBCamera

Description

Gets images from USB Video Class (UVC)-compatible devices. Outputs one flow file per frame at the rate specified by the FPS property in the format specified by the Format property.

Properties

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
FPS1Frames per second to capture from USB camera
FormatPNGFrame format (currently only PNG and RAW are supported; RAW is a binary pixel buffer of RGB values)
HeightTarget height of image to capture from USB camera
USB Product ID0x0USB Product ID of camera device, in hexadecimal format
USB Serial No.USB Serial No. of camera device
USB Vendor ID0x0USB Vendor ID of camera device, in hexadecimal format
WidthTarget width of image to capture from USB camera

Relationships

NameDescription
failureFailures sent here
successSucessfully captured images sent here

HashContent

Description

HashContent calculates the checksum of the content of the flowfile and adds it as an attribute. Configuration options exist to select hashing algorithm and set the name of the attribute.

Properties

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
Hash AlgorithmSHA256Name of the algorithm used to generate checksum
Hash AttributeChecksumAttribute to store checksum to

Properties

NameDescription
failurefailure operational on the flow record
successsuccess operational on the flow record

InvokeHTTP

Description

An HTTP client processor which can interact with a configurable HTTP Endpoint. The destination URL and HTTP Method are configurable. FlowFile attributes are converted to HTTP headers and the FlowFile contents are included as the body of the request (if the HTTP Method is PUT, POST or PATCH).

Properties

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
Always Output ResponsefalseWill force a response FlowFile to be generated and routed to the ‘Response’ relationship regardless of what the server status code received is
Attributes to SendRegular expression that defines which attributes to send as HTTP headers in the request. If not defined, no attributes are sent as headers.
Connection Timeout5 secsMax wait time for connection to remote service.
Content-typeapplication/octet-streamThe Content-Type to specify for when content is being transmitted through a PUT, POST or PATCH. In the case of an empty value after evaluating an expression language expression, Content-Type defaults to
Disable Peer VerificationfalseDisables peer verification for the SSL session
Follow RedirectstrueFollow HTTP redirects issued by remote server.
HTTP MethodGETHTTP request method (GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS). Arbitrary methods are also supported. Methods other than POST, PUT and PATCH will be sent without a message body.
Include Date HeadertrueInclude an RFC-2616 Date header in the request.
invokehttp-proxy-passwordPassword to set when authenticating against proxy
invokehttp-proxy-usernameUsername to set when authenticating against proxy
Penalize on “No Retry”falseEnabling this property will penalize FlowFiles that are routed to the “No Retry” relationship.
Proxy HostThe fully qualified hostname or IP address of the proxy server
Proxy PortThe port of the proxy server
Put Response Body in AttributeIf set, the response body received back will be put into an attribute of the original FlowFile instead of a separate FlowFile. The attribute key to put to is determined by evaluating value of this property.
Read Timeout15 secsMax wait time for response from remote service.
Remote URLRemote URL which will be connected to, including scheme, host, port, path.
Supports Expression Language: true
send-message-bodytrueDEPRECATED. Only kept for backwards compatibility, no functionality is included.
Send Message BodytrueIf true, sends the HTTP message body on POST/PUT/PATCH requests (default). If false, suppresses the message body and content-type header for these requests.
SSL Context ServiceThe SSL Context Service used to provide client certificate information for TLS/SSL (https) connections.
Use Chunked EncodingfalseWhen POST‘ing, PUT’ing or PATCH'ing content set this property to true in order to not pass the ‘Content-length’ header and instead send ‘Transfer-Encoding’ with a value of ‘chunked’. This will enable the data transfer mechanism which was introduced in HTTP 1.1 to pass data of unknown lengths in chunks.

Relationships

NameDescription
successAll files are routed to success

ListSFTP

Description

Performs a listing of the files residing on an SFTP server. For each file that is found on the remote server, a new FlowFile will be created with the filename attribute set to the name of the file on the remote server. This can then be used in conjunction with FetchSFTP in order to fetch those files.

Properties

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
Connection Timeout30 secAmount of time to wait before timing out while creating a connection
Data Timeout30 secWhen transferring a file between the local and remote system, this value specifies how long is allowed to elapse without any data being transferred between systems
Entity Tracking Initial Listing TargetAll AvailableAll Available
Tracking Time Window
Specify how initial listing should be handled. Used by ‘Tracking Entities’ strategy.
Entity Tracking Time WindowSpecify how long this processor should track already-listed entities. ‘Tracking Entities’ strategy can pick any entity whose timestamp is inside the specified time window. For example, if set to ‘30 minutes’, any entity having timestamp in recent 30 minutes will be the listing target when this processor runs. A listed entity is considered ‘new/updated’ and a FlowFile is emitted if one of following condition meets: 1. does not exist in the already-listed entities, 2. has newer timestamp than the cached entity, 3. has different size than the cached entity. If a cached entity's timestamp becomes older than specified time window, that entity will be removed from the cached already-listed entities. Used by ‘Tracking Entities’ strategy.
File Filter RegexProvides a Java Regular Expression for filtering Filenames; if a filter is supplied, only files whose names match that Regular Expression will be fetched
Follow symlinkfalseIf true, will pull even symbolic files and also nested symbolic subdirectories; otherwise, will not read symbolic files and will not traverse symbolic link subdirectories
Host Key FileIf supplied, the given file will be used as the Host Key; otherwise, no use host key file will be used
HostnameThe fully qualified hostname or IP address of the remote system
Supports Expression Language: true
Http Proxy PasswordHttp Proxy Password
Supports Expression Language: true
Http Proxy UsernameHttp Proxy Username
Supports Expression Language: true
Ignore Dotted FilestrueIf true, files whose names begin with a dot (“.”) will be ignored
Listing StrategyTracking TimestampsTracking Entities
Tracking Timestamps
Specify how to determine new/updated entities. See each strategy descriptions for detail.
Maximum File AgeThe maximum age that a file must be in order to be pulled; any file older than this amount of time (according to last modification date) will be ignored
Maximum File SizeThe maximum size that a file must be in order to be pulled
Minimum File Age0 secThe minimum age that a file must be in order to be pulled; any file younger than this amount of time (according to last modification date) will be ignored
Minimum File Size0 BThe minimum size that a file must be in order to be pulled
PasswordPassword for the user account
Supports Expression Language: true
Path Filter RegexWhen Search Recursively is true, then only subdirectories whose path matches the given Regular Expression will be scanned
PortThe port that the remote system is listening on for file transfers
Supports Expression Language: true
Private Key PassphrasePassword for the private key
Supports Expression Language: true
Private Key PathThe fully qualified path to the Private Key file
Supports Expression Language: true
Proxy HostThe fully qualified hostname or IP address of the proxy server
Supports Expression Language: true
Proxy PortThe port of the proxy server
Supports Expression Language: true
Proxy TypeDIRECTDIRECT
HTTP
SOCKS
Specifies the Proxy Configuration Controller Service to proxy network requests. If set, it supersedes proxy settings configured per component. Supported proxies: HTTP + AuthN, SOCKS + AuthN
Remote PathThe fully qualified filename on the remote system
Supports Expression Language: true
Search RecursivelyfalseIf true, will pull files from arbitrarily nested subdirectories; otherwise, will not traverse subdirectories
Send Keep Alive On TimeouttrueIndicates whether or not to send a single Keep Alive message when SSH socket times out
State FileListSFTPSpecifies the file that should be used for storing state about what data has been ingested so that upon restart MiNiFi can resume from where it left off
Strict Host Key CheckingfalseIndicates whether or not strict enforcement of hosts keys should be applied
Target System Timestamp PrecisionAuto DetectAuto Detect
Milliseconds
Minutes
Seconds
Specify timestamp precision at the target system. Since this processor uses timestamp of entities to decide which should be listed, it is crucial to use the right timestamp precision.
UsernameUsername
Supports Expression Language: true

Relationships

NameDescription
successAll FlowFiles that are received are routed to success

ListenHTTP

Description

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, POST, and GET requests are supported. PUT, and DELETE will result in an error and the HTTP response status code 405. The response body text for all requests, by default, is empty (length of 0). A static response body can be set for a given URI by sending input files to ListenHTTP with the http.type attribute set to response_body. The response body FlowFile filename attribute is appended to the Base Path property (separated by a /) when mapped to incoming requests. The mime.type attribute of the response body FlowFile is used for the Content-type header in responses. Response body content can be cleared by sending an empty (size 0) FlowFile for a given URI mapping.

Properties

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
Authorized 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.
Base PathcontentListenerBase path for incoming connections
Batch Size0Maximum number of buffered requests to be processed in a single batch. If set to zero all buffered requests are processed.
Buffer Size0Maximum number of HTTP Requests allowed to be buffered before processing them when the processor is triggered. If the buffer full, the request is refused. If set to zero the buffer is unlimited.
HTTP Headers to receive as Attributes (Regex)Specifies the Regular Expression that determines the names of HTTP Headers that should be passed along as FlowFile attributes
Listening Port80The Port to listen on for incoming connections. 0 means port is going to be selected randomly.
SSL CertificateFile containing PEM-formatted file including TLS/SSL certificate and key
SSL Certificate AuthorityFile containing trusted PEM-formatted certificates
SSL Minimum VersionTLS1.2TLS1.2
Minimum TLS/SSL version allowed (TLS1.2)
SSL Verify Peernono
yes
Whether or not to verify the client's certificate (yes/no)

Relationships

NameDescription
successAll files are routed to success

ListenSyslog

Description

Listens for Syslog messages being sent to a given port over TCP or UDP. Incoming messages are checked against regular expressions for RFC5424 and RFC3164 formatted messages. The format of each message is: ()(VERSION )(TIMESTAMP) (HOSTNAME) (BODY) where version is optional. The timestamp can be an RFC5424 timestamp with a format of “yyyy-MM-dd‘T’HH:mm:ss.SZ” or “yyyy-MM-dd‘T’HH:mm:ss.S+hh:mm”, or it can be an RFC3164 timestamp with a format of “MMM d HH:mm:ss”. If an incoming messages matches one of these patterns, the message will be parsed and the individual pieces will be placed in FlowFile attributes, with the original message in the content of the FlowFile. If an incoming message does not match one of these patterns it will not be parsed and the syslog.valid attribute will be set to false with the original message in the content of the FlowFile. Valid messages will be transferred on the success relationship, and invalid messages will be transferred on the invalid relationship.

Properties

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
Max Batch Size1The maximum number of Syslog events to add to a single FlowFile.
Max Number of TCP Connections2The maximum number of concurrent connections to accept Syslog messages in TCP mode.
Max Size of Socket Buffer1 MBThe maximum size of the socket buffer that should be used.
Message Delimiter\nSpecifies the delimiter to place between Syslog messages when multiple messages are bundled together (see core::Property).
Parse MessagesfalseIndicates if the processor should parse the Syslog messages. If set to false, each outgoing FlowFile will only.
Port514The port for Syslog communication
ProtocolUDPUDP
TCP
The protocol for Syslog communication.
Receive Buffer Size65507 BThe size of each buffer used to receive Syslog messages.

Relationships

NameDescription
invalidSysLog message format invalid
successAll files are routed to success

ListS3

Description

Retrieves a listing of objects from an S3 bucket. For each object that is listed, creates a FlowFile that represents the object so that it can be fetched in conjunction with FetchS3Object.

Properties

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
BucketThe S3 bucket
Supports Expression Language: true
Access KeyAWS account access key
Supports Expression Language: true
Secret KeyAWS account secret key
Supports Expression Language: true
Credentials FilePath to a file containing AWS access key and secret key in properties file format. Properties used: accessKey and secretKey
AWS Credentials Provider serviceThe name of the AWS Credentials Provider controller service that is used to obtain AWS credentials.
Regionus-west-2af-south-1
ap-east-1
ap-northeast-1
ap-northeast-2
ap-northeast-3
ap-south-1
ap-southeast-1
ap-southeast-2
ca-central-1
cn-north-1
cn-northwest-1
eu-central-1
eu-north-1
eu-south-1
eu-west-1
eu-west-2
eu-west-3
me-south-1
sa-east-1
us-east-1
us-east-2
us-gov-east-1
us-gov-west-1
us-west-1
us-west-2
AWS Region
Communications Timeout30 secSets the timeout of the communication between the AWS server and the client
Endpoint Override URLEndpoint URL to use instead of the AWS default including scheme, host, port, and path. The AWS libraries select an endpoint URL based on the AWS region, but this property overrides the selected endpoint URL, allowing use with other S3-compatible endpoints.
Supports Expression Language: true
Proxy HostProxy host name or IP
Supports Expression Language: true
Proxy PortThe port number of the proxy host
Supports Expression Language: true
Proxy UsernameUsername to set when authenticating against proxy
Supports Expression Language: true
Proxy PasswordPassword to set when authenticating against proxy
Supports Expression Language: true
DelimiterThe string used to delimit directories within the bucket. Please consult the AWS documentation for the correct use of this field.
PrefixThe prefix used to filter the object list. In most cases, it should end with a forward slash (‘/’).
Use VersionsfalseSpecifies whether to use S3 versions, if applicable. If false, only the latest version of each object will be returned.
Minimum Object Age0 secThe minimum age that an S3 object must be in order to be considered; any object younger than this amount of time (according to last modification date) will be ignored.
Write Object TagsfalseIf set to ‘true’, the tags associated with the S3 object will be written as FlowFile attributes.
Write User MetadatafalseIf set to ‘true’, the user defined metadata associated with the S3 object will be added to FlowFile attributes/records.
Requester PaysfalseIf true, indicates that the requester consents to pay any charges associated with listing the S3 bucket. This sets the ‘x-amz-request-payer’ header to ‘requester’. Note that this setting is only used if Write User Metadata is true.

Relationships

NameDescription
successFlowFiles are routed to success relationship

LogAttribute

Description

Logs attributes of flow files in the MiNiFi application log.

Properties

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
Attributes to IgnoreA comma-separated list of Attributes to ignore. If not specified, no attributes will be ignored.
Attributes to LogA comma-separated list of Attributes to Log. If not specified, all attributes will be logged.
FlowFiles To Log1Number of flow files to log. If set to zero all flow files will be logged. Please note that this may block other threads from running if not used judiciously.
Hexencode PayloadfalseIf true, the FlowFile's payload will be logged in a hexencoded format
Log Leveldebug
error
info
trace
warn
The Log Level to use when logging the Attributes
Log PayloadfalseIf true, the FlowFile's payload will be logged, in addition to its attributes.otherwise, just the Attributes will be logged
Log PrefixLog prefix appended to the log lines. It helps to distinguish the output of multiple LogAttribute processors.
Maximum Payload Line Length80The logged payload will be broken into lines this long. 0 means no newlines will be added.

Relationships

NameDescription
successsuccess operational on the flow record

ManipulateArchive

Description

Performs an operation which manipulates an archive without needing to split the archive into multiple FlowFiles.

Properties

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
AfterFor operations which result in new entries, places the new entry after the entry specified by this property.
BeforeFor operations which result in new entries, places the new entry before the entry specified by this property.
DestinationDestination for operations (touch, move or copy) which result in new entries.
OperationOperation to perform on the archive (touch, remove, copy, move).
TargetAn existing entry within the archive to perform the operation on.

Relationships

NameDescription
failureFlowFiles will be transferred to the failure relationship if the operation fails.
successFlowFiles will be transferred to the success relationship if the operation succeeds.

MergeContent

Description

Merges a Group of FlowFiles together based on a user-defined strategy and packages them into a single FlowFile. MergeContent should be configured with only one incoming connection as it won't create grouped Flow Files.This processor updates the mime.type attribute as appropriate.

Properties

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
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 (in which case neither, or none, of the conflicting attributes will be kept). 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 NameCorrelation Attribute Name
Delimiter StrategyFilenameDetermines if Header, Footer, and Demarcator should point to files
Demarcator FileFilename specifying the demarcator to use
Footer FileFilename specifying the footer to use
Header FileFilename specifying the header to use
Keep PathfalseIf using the Zip or Tar Merge Format, specifies whether or not the FlowFiles' paths should be included in their entry
Max Bin AgeThe maximum age of a Bin that will trigger a Bin to be complete. Expected format is
Maximum Group SizeThe maximum size for the bundle. If not specified, there is no maximum.
Maximum Number of EntriesThe maximum number of files to include in a bundle. If not specified, there is no maximum.
Maximum number of Bins100Specifies the maximum number of bins that can be held in memory at any one time
Merge FormatBinary ConcatenationMerge Format
Merge StrategyDefragmentDefragment or Bin-Packing Algorithm
Minimum Group Size0The minimum size of for the bundle
Minimum Number of Entries1The minimum number of files to include in a bundle

Relationships

NameDescription
failureIf the bundle cannot be created, all FlowFiles that would have been used to created the bundle will be transferred to failure
mergedThe FlowFile containing the merged content
originalThe FlowFiles that were used to create the bundle

MotionDetector

Description

Detect motion from captured images.

Properties

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
Dilate iteration10For image processing, if an object is detected as 2 separate objects, increase this value
Image Encoding.jpg.jpg
.png
The encoding that should be applied to the output
Minimum Area100We only consider the movement regions with area greater than this.
Path to background frameIf not provided then the processor will take the first input frame as background
Threshold for segmentation42Pixel greater than this will be white, otherwise black.

Relationships

NameDescription
failureFailure to detect motion
successSuccessful to detect motion

PublishKafka

Description

This Processor puts the contents of a FlowFile to a Topic in Apache Kafka. The content of a FlowFile becomes the contents of a Kafka message. This message is optionally assigned a key by using the Property.

Properties

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
Attributes to Send as HeadersAny attribute whose name matches the regex will be added to the Kafka messages as a Header
Batch Size10Maximum number of messages batched in one MessageSet
Client NameClient Name to use when communicating with Kafka
Supports Expression Language: true
Compress Codecnonecompression codec to use for compressing message sets
Debug contextsA comma-separated list of debug contexts to enable.Including: generic, broker, topic, metadata, feature, queue, msg, protocol, cgrp, security, fetch, interceptor, plugin, consumer, admin, eos, all
Delivery Guarantee1Specifies the requirement for guaranteeing that a message is sent to Kafka. Valid values are 0 (do not wait for acks), -1 or all (block until message is committed by all in sync replicas) or any concrete number of nodes.
Supports Expression Language: true
Kerberos Keytab PathThe path to the location on the local filesystem where the kerberos keytab is located. Read permission on the file is required.
Kerberos PrincipalKeberos Principal
Kerberos Service NameKerberos Service Name
Known BrokersA comma-separated list of known Kafka Brokers in the format :
Supports Expression Language: true
Max Flow Segment Size0 BMaximum flow content payload segment size for the kafka record. 0 B means unlimited.
Max Request SizeMaximum Kafka protocol request message size
Kafka KeyThe key to use for the message. If not specified, the UUID of the flow file is used as the message key.
Supports Expression Language: true
Message Key FieldDEPRECATED, does not work -- use Kafka Key instead
Message Timeout30 secThe total time sending a message could take
Queue Buffering Max TimeDelay to wait for messages in the producer queue to accumulate before constructing message batches
Queue Max Buffer SizeMaximum total message size sum allowed on the producer queue
Queue Max MessageMaximum number of messages allowed on the producer queue
Request Timeout10 secThe ack timeout of the producer request
Security CAFile or directory path to CA certificate(s) for verifying the broker's key
Security CertPath to client's public key (PEM) used for authentication
Security Pass PhrasePrivate key passphrase
Security Private KeyPath to client's private key (PEM) used for authentication
Security ProtocolProtocol used to communicate with brokers
Target Batch Payload Size512 KBThe target total payload size for a batch. 0 B means unlimited (Batch Size is still applied).
Topic NameThe Kafka Topic of interest
Supports Expression Language: true

Relationships

NameDescription
failureAny FlowFile that cannot be sent to Kafka will be routed to this Relationship
successAny FlowFile that is successfully sent to Kafka will be routed to this Relationship

PublishMQTT

Description

PublishMQTT serializes FlowFile content as an MQTT payload, sending the message to the configured topic and broker.

Properties

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
Broker URIThe URI to use to connect to the MQTT broker
Client IDMQTT client ID to use
Connection Timeout30 secMaximum time interval the client will wait for the network connection to the MQTT server
Keep Alive Interval60 secDefines the maximum time interval between messages sent or received
Max Flow Segment SizeMaximum flow content payload segment size for the MQTT record
PasswordPassword to use when connecting to the broker
Quality of ServiceMQTT_QOS_0The Quality of Service(QoS) to send the message with. Accepts three values ‘0’, ‘1’ and ‘2’
RetainfalseRetain MQTT published record in broker
Session statetrueWhether to start afresh or resume previous flows. See the allowable value descriptions for more details
TopicThe topic to publish the message to
UsernameUsername to use when connecting to the broker

Relationships

NameDescription
failureFlowFiles that failed to send to the destination are transferred to this relationship
successFlowFiles that are sent successfully to the destination are transferred to this relationship

PutAzureBlobStorage

Description

Puts content into an Azure Storage Blob

Properties

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
Container NameName of the Azure storage container. In case of PutAzureBlobStorage processor, container can be created if it does not exist.
Supports Expression Language: true
Storage Account Name
Storage Account Key
SAS Token
Common Storage Account Endpoint Suffix
Connection String
Azure Storage Credentials ServiceName of the Azure Storage Credentials Service used to retrieve the connection string from.
BlobThe filename of the blob.
Supports Expression Language: true
Create ContainerfalseSpecifies whether to check if the container exists and to automatically create it if it does not. Permission to list containers is required. If false, this check is not made, but the Put operation will fail if the container does not exist.

Relationships

NameDescription
failureUnsuccessful operations will be transferred to the failure relationship
successAll successfully processed FlowFiles are routed to this relationship

PutFile

Description

Writes the contents of a FlowFile to the local file system

Properties

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
Conflict Resolution Strategyfailfail
ignore
replace
Indicates what should happen when a file with the same name already exists in the output directory
Create Missing DirectoriestrueIf true, then missing destination directories will be created. If false, flowfiles are penalized and sent to failure.
Directory.The output directory to which to put files
Supports Expression Language: true
Maximum File Count-1Specifies the maximum number of files that can exist in the output directory
PermissionsSets the permissions on the output file to the value of this attribute. Must be an octal number (e.g. 644 or 0755). Not supported on Windows systems.
Directory PermissionsSets the permissions on the directories being created if ‘Create Missing Directories’ property is set. Must be an octal number (e.g. 644 or 0755). Not supported on Windows systems.

Relationships

NameDescription
failureFailed files (conflict, write failure, etc.) are transferred to failure
successAll files are routed to success

PutOPCProcessor

Description

Creates/updates OPC nodes

Properties

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
Application URIApplication URI of the client in the format ‘urn:unconfigured:application’. Mandatory, if using Secure Channel and must match the URI included in the certificate's Subject Alternative Names.
Certificate pathPath to the DER-encoded cert file
Key pathPath to the DER-encoded key file
OPC server endpointSpecifies the address, port and relative path of an OPC endpoint
Parent node IDSpecifies the ID of the root node to traverse
Parent node ID typeInt
Path
String
Specifies the type of the provided node ID
Parent node namespace index0The index of the namespace. Used only if node ID type is not path.
PasswordPassword to log in with. Providing this requires cert and key to be provided as well, credentials are always sent encrypted.
Target node IDID of target node.
Supports Expression Language: true
Target node ID typeID type of target node. Allowed values are: Int, String.
Supports Expression Language: true
Target node browse nameBrowse name of target node. Only used when new node is created.
Supports Expression Language: true
Target node namespace indexThe index of the namespace. Used only if node ID type is not path.
Supports Expression Language: true
Trusted server certificate pathPath to the DER-encoded trusted server certificate
UsernameUsername to log in with.
Value typeBoolean
Double
Float
Int32
Int64
String
UInt32
UInt64
Set the OPC value type of the created nodes

Relationships

NameDescription
failureFailed to put OPC-UA node
successSuccessfully put OPC-UA node

PutS3Object

Description

Puts FlowFiles to an Amazon S3 Bucket. The upload uses either the PutS3Object method. The PutS3Object method send the file in a single synchronous call, but it has a 5GB size limit. Larger files sent using the multipart upload methods are currently not supported. The AWS libraries select an endpoint URL based on the AWS region, but this can be overridden with the ‘Endpoint Override URL’ property for use with other S3-compatible endpoints. The S3 API specifies that the maximum file size for a PutS3Object upload is 5GB.

Properties

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
Object KeyThe key of the S3 object. If none is given the filename attribute will be used by default.
Supports Expression Language: true
BucketThe S3 bucket
Supports Expression Language: true
Content TypeSets the Content-Type HTTP header indicating the type of content stored in the associated object. The value of this header is a standard MIME type. If no content type is provided the default content type “application/octet-stream” will be used.
Supports Expression Language: true
Use Default CredentialsfalseIf true, uses the Default Credential chain to obtain AWS credentials, including EC2 instance profiles or roles, environment variables, default user credentials, etc.
Access KeyAWS account access key
Supports Expression Language: true
Secret KeyAWS account secret key
Supports Expression Language: true
Credentials FilePath to a file containing AWS access key and secret key in properties file format. Properties used: accessKey and secretKey
AWS Credentials Provider serviceThe name of the AWS Credentials Provider controller service that is used to obtain AWS credentials.
Storage ClassStandardStandard
ReducedRedundancy
StandardIA
OnezoneIA
IntelligentTiering
Glacier
DeepArchive
AWS S3 Storage Class
Regionus-west-2af-south-1
ap-east-1
ap-northeast-1
ap-northeast-2
ap-northeast-3
ap-south-1
ap-southeast-1
ap-southeast-2
ca-central-1
cn-north-1
cn-northwest-1
eu-central-1
eu-north-1
eu-south-1
eu-west-1
eu-west-2
eu-west-3
me-south-1
sa-east-1
us-east-1
us-east-2
us-gov-east-1
us-gov-west-1
us-west-1
us-west-2
AWS Region
Communications Timeout30 secSets the timeout of the communication between the AWS server and the client
FullControl User ListA comma-separated list of Amazon User ID's or E-mail addresses that specifies who should have Full Control for an object.
Supports Expression Language: true
Read Permission User ListA comma-separated list of Amazon User ID's or E-mail addresses that specifies who should have Read Access for an object.
Supports Expression Language: true
Read ACL User ListA comma-separated list of Amazon User ID's or E-mail addresses that specifies who should have permissions to read the Access Control List for an object.
Supports Expression Language: true
Write ACL User ListA comma-separated list of Amazon User ID's or E-mail addresses that specifies who should have permissions to change the Access Control List for an object.
Supports Expression Language: true
Endpoint Override URLEndpoint URL to use instead of the AWS default including scheme, host, port, and path. The AWS libraries select an endpoint URL based on the AWS region, but this property overrides the selected endpoint URL, allowing use with other S3-compatible endpoints.
Supports Expression Language: true
Server Side EncryptionNoneNone
AES256
aws_kms
Specifies the algorithm used for server side encryption.
Proxy HostProxy host name or IP
Supports Expression Language: true
Proxy PortThe port number of the proxy host
Supports Expression Language: true
Proxy UsernameUsername to set when authenticating against proxy
Supports Expression Language: true
Proxy PasswordPassword to set when authenticating against proxy
Supports Expression Language: true

Relationships

NameDescription
failureFlowFiles are routed to failure relationship
successFlowFiles are routed to success relationship

PutSFTP

Description

Sends FlowFiles to an SFTP Server

Properties

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
Batch Size500The maximum number of FlowFiles to send in a single connection
Conflict ResolutionNONEFAIL
IGNORE
NONE
REJECT
RENAME
REPLACE
Determines how to handle the problem of filename collisions
Connection Timeout30 secAmount of time to wait before timing out while creating a connection
Create DirectoryfalseSpecifies whether or not the remote directory should be created if it does not exist.
Data Timeout30 secWhen transferring a file between the local and remote system, this value specifies how long is allowed to elapse without any data being transferred between systems
Disable Directory ListingfalseIf set to ‘true’, directory listing is not performed prior to create missing directories. By default, this processor executes a directory listing command to see target directory existence before creating missing directories. However, there are situations that you might need to disable the directory listing such as the following. Directory listing might fail with some permission setups (e.g. chmod 100) on a directory. Also, if any other SFTP client created the directory after this processor performed a listing and before a directory creation request by this processor is finished, then an error is returned because the directory already exists.
Dot RenametrueIf true, then the filename of the sent file is prepended with a “.” and then renamed back to the original once the file is completely sent. Otherwise, there is no rename. This property is ignored if the Temporary Filename property is set.
Host Key FileIf supplied, the given file will be used as the Host Key; otherwise, no use host key file will be used
HostnameThe fully qualified hostname or IP address of the remote system
Supports Expression Language: true
Http Proxy PasswordHttp Proxy Password
Supports Expression Language: true
Http Proxy UsernameHttp Proxy Username
Supports Expression Language: true
Last Modified TimeThe lastModifiedTime to assign to the file after transferring it. If not set, the lastModifiedTime will not be changed. Format must be yyyy-MM-dd‘T’HH:mm:ssZ. You may also use expression language such as ${file.lastModifiedTime}. If the value is invalid, the processor will not be invalid but will fail to change lastModifiedTime of the file.
Supports Expression Language: true
PasswordPassword for the user account
Supports Expression Language: true
PermissionsThe permissions to assign to the file after transferring it. Format must be either UNIX rwxrwxrwx with a - in place of denied permissions (e.g. rw-r--r--) or an octal number (e.g. 644). If not set, the permissions will not be changed. You may also use expression language such as ${file.permissions}. If the value is invalid, the processor will not be invalid but will fail to change permissions of the file.
Supports Expression Language: true
PortThe port that the remote system is listening on for file transfers
Supports Expression Language: true
Private Key PassphrasePassword for the private key
Supports Expression Language: true
Private Key PathThe fully qualified path to the Private Key file
Supports Expression Language: true
Proxy HostThe fully qualified hostname or IP address of the proxy server
Supports Expression Language: true
Proxy PortThe port of the proxy server
Supports Expression Language: true
Proxy TypeDIRECTDIRECT
HTTP
SOCKS
Specifies the Proxy Configuration Controller Service to proxy network requests. If set, it supersedes proxy settings configured per component. Supported proxies: HTTP + AuthN, SOCKS + AuthN
Reject Zero-Byte FilestrueDetermines whether or not Zero-byte files should be rejected without attempting to transfer
Remote GroupInteger value representing the Group ID to set on the file after transferring it. If not set, the group will not be set. You may also use expression language such as ${file.group}. If the value is invalid, the processor will not be invalid but will fail to change the group of the file.
Supports Expression Language: true
Remote OwnerInteger value representing the User ID to set on the file after transferring it. If not set, the owner will not be set. You may also use expression language such as ${file.owner}. If the value is invalid, the processor will not be invalid but will fail to change the owner of the file.
Supports Expression Language: true
Remote PathThe path on the remote system from which to pull or push files
Supports Expression Language: true
Send Keep Alive On TimeouttrueIndicates whether or not to send a single Keep Alive message when SSH socket times out
Strict Host Key CheckingfalseIndicates whether or not strict enforcement of hosts keys should be applied
Temporary FilenameIf set, the filename of the sent file will be equal to the value specified during the transfer and after successful completion will be renamed to the original filename. If this value is set, the Dot Rename property is ignored.
Supports Expression Language: true
Use CompressionfalseIndicates whether or not ZLIB compression should be used when transferring files
UsernameUsername
Supports Expression Language: true

Relationships

NameDescription
failureFlowFiles that failed to send to the remote system; failure is usually looped back to this processor
rejectFlowFiles that were rejected by the destination system
successFlowFiles that are successfully sent will be routed to success

PutSQL

Description

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 ? character to bind 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 content of the FlowFile is expected to be in UTF-8 format.

Properties

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
DB Controller ServiceDatabase Controller Service.
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.

Relationships

NameDescription
successAfter a successful SQL update operation, the incoming FlowFile sent here

QueryDatabaseTable

Description

Fetches all rows of a table, whose values in the specified Maximum-value Columns are larger than the previously-seen maxima. If that property is not provided, all rows are returned. The rows are grouped according to the value of Max Rows Per Flow File property and formatted as JSON.

Properties

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
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.
DB Controller ServiceDatabase Controller Service.
Max Rows Per Flow File0The maximum number of result rows that will be included in a single FlowFile. This will allow you to break up very large result sets into multiple FlowFiles. If the value specified is zero, then all rows are returned in a single FlowFile.
Maximum-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.
Output FormatJSON-PrettyJSON
JSON-Pretty
Set the output format type.
Table NameThe name of the database table to be queried.
Where ClauseA custom clause to be added in the WHERE condition when building SQL queries.

Relationships

NameDescription
successSuccessfully created FlowFile from SQL query result set.

Dynamic Properties:

NameValueDescription
initial.maxvalue.<max_value_column>Initial maximum value for the specified columnSpecifies an initial max value for max value column(s). Properties should be added in the format initial.maxvalue.<max_value_column>. This value is only used the first time the table is accessed (when a Maximum Value Column is specified).
Supports Expression Language: true

RetryFlowFile

Description

FlowFiles passed to this Processor have a ‘Retry Attribute’ value checked against a configured ‘Maximum Retries’ value. If the current attribute value is below the configured maximum, the FlowFile is passed to a retry relationship. The FlowFile may or may not be penalized in that condition. If the FlowFile's attribute value exceeds the configured maximum, the FlowFile will be passed to a ‘retries_exceeded’ relationship. WARNING: If the incoming FlowFile has a non-numeric value in the configured ‘Retry Attribute’ attribute, it will be reset to ‘1’. You may choose to fail the FlowFile instead of performing the reset. Additional dynamic properties can be defined for any attributes you wish to add to the FlowFiles transferred to ‘retries_exceeded’. These attributes support attribute expression language.

Properties

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
Retry Attribute“flowfile.retries”The name of the attribute that contains the current retry count for the FlowFile. WARNING: If the name matches an attribute already on the FlowFile that does not contain a numerical value, the processor will either overwrite that attribute with ‘1’ or fail based on configuration.
Supports Expression Language: true
Maximum Retries3The maximum number of times a FlowFile can be retried before being passed to the ‘retries_exceeded’ relationship.
Supports Expression Language: true
Penalize Retriestrue"If set to ‘true’, this Processor will penalize input FlowFiles before passing them to the ‘retry’ relationship. This does not apply to the ‘retries_exceeded’ relationship.
Fail on Non-numerical OverwritefalseIf the FlowFile already has the attribute defined in ‘Retry Attribute’ that is not a number, fail the FlowFile instead of resetting that value to ‘1’.
Reuse Mode“Fail on Reuse”“Fail on Reuse”
“Warn on Reuse”
“Reset Reuse”
Defines how the Processor behaves if the retry FlowFile has a different retry UUID than the instance that received the FlowFile. This generally means that the attribute was not reset after being successfully retried by a previous instance of this processor. Warn on reuse and Fail on Reuse both resets the retry property value to 1 and marks the flowfile to be last retried by this processor.

Relationships

NameDescription
retryInput FlowFile has not exceeded the configured maximum retry count, pass this relationship back to the input Processor to create a limited feedback loop.
retries_exceededInput FlowFile has exceeded the configured maximum retry count, do not pass this relationship back to the input Processor to terminate the limited feedback loop.
failureThe processor is configured such that a non-numerical value on ‘Retry Attribute’ results in a failure instead of resetting that value to ‘1’. This will immediately terminate the limited feedback loop. Might also include when ‘Maximum Retries’ contains attribute expression language that does not resolve to an Integer.

Dynamic Properties:

NameValueDescription
Exceeded FlowFile Attribute KeyThe value of the attribute added to the FlowFileOne or more dynamic properties can be used to add attributes to FlowFiles passed to the ‘retries_exceeded’ relationship.
Supports Expression Language: true

Writes Attributes:

NameDescription
Retry AttributeUser defined retry attribute is updated with the current retry count
Retry Attribute .uuidUser defined retry attribute with .uuid that determines what processor retried the FlowFile last

RouteOnAttribute

Description

Routes FlowFiles based on their Attributes using the Attribute Expression Language.

Properties

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

Relationships

NameDescription
failureFailed files are transferred to failure
unmatchedFiles which do not match any expression are routed here

TailFile

Description

“Tails” a file, or a list of files, ingesting data from the file as it is written to the file. The file is expected to be textual. Data is ingested only when a new line is encountered (carriage return or new-line character or combination). If the file to tail is periodically “rolled over”, as is generally the case with log files, an optional Rolling Filename Pattern can be used to retrieve data from files that have rolled over, even if the rollover occurred while NiFi was not running (provided that the data still exists upon restart of NiFi). It is generally advisable to set the Run Schedule to a few seconds, rather than running with the default value of 0 secs, as this Processor will consume a lot of resources if scheduled very aggressively. At this time, this Processor does not support ingesting files that have been compressed when ‘rolled over’.

Properties

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
File to TailFully-qualified filename of the file that should be tailed when using single file mode, or a file regex when using multifile mode
Input DelimiterSpecifies the character that should be used for delimiting the data being tailedfrom the incoming file.If none is specified, data will be ingested as it becomes available.
State FileTailFileStateSpecifies the file that should be used for storing state about what data has been ingested so that upon restart NiFi can resume from where it left off
tail-base-directory
tail-modeSingle fileSingle file
Multiple file
Specifies the tail file mode. In ‘Single file’ mode only a single file will be watched. In ‘Multiple file’ mode a regex may be used. Note that in multiple file mode we will still continue to watch for rollover on the initial set of watched files. The Regex used to locate multiple files will be run during the schedule phrase. Note that if rotated files are matched by the regex, those files will be tailed.

Relationships

NameDescription
successAll files are routed to success

UnfocusArchiveEntry

Description

Restores a FlowFile which has had an archive entry focused via FocusArchiveEntry to its original state.

Properties

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

Relationships

NameDescription
successsuccess operational on the flow record

UpdateAttribute

Description

This processor updates the attributes of a FlowFile using properties that are added by the user. This allows you to set default attribute changes that affect every FlowFile going through the processor, equivalent to the “basic” usage in Apache NiFi.

Properties

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

Relationships

NameDescription
failureFailed files are transferred to failure
successAll files are routed to success