Consumes AMQP Messages from an AMQP Broker using the AMQP 0.9.1 protocol. Each message that is received from the AMQP Broker will be emitted as its own FlowFile to the 'success' relationship.
amqp, rabbit, get, message, receive, consume
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.
| Display Name | API Name | Default Value | Allowable Values | Description |
|---|---|---|---|---|
| Queue | Queue | The name of the existing AMQP Queue from which messages will be consumed. Usually pre-defined by AMQP administrator. | ||
| Auto-Acknowledge Messages | auto.acknowledge | false |
| If false (Non-Auto-Acknowledge), the messages will be acknowledged by the processor after transferring the FlowFiles to success and committing the NiFi session. Non-Auto-Acknowledge mode provides 'at-least-once' delivery semantics. If true (Auto-Acknowledge), messages that are delivered to the AMQP Client will be auto-acknowledged by the AMQP Broker just after sending them out. This generally will provide better throughput but will also result in messages being lost upon restart/crash of the AMQP Broker, NiFi or the processor. Auto-Acknowledge mode provides 'at-most-once' delivery semantics and it is recommended only if loosing messages is acceptable. |
| Batch Size | batch.size | 10 | The maximum number of messages that should be processed in a single session. Once this many messages have been received (or once no more messages are readily available), the messages received will be transferred to the 'success' relationship and the messages will be acknowledged to the AMQP Broker. Setting this value to a larger number could result in better performance, particularly for very small messages, but can also result in more messages being duplicated upon sudden restart of NiFi. | |
| Remove Curly Braces | remove.curly.braces | False |
| If true Remove Curly Braces, Curly Braces in the header will be automatically remove. |
| Header Separator | header.separator | , | The character that is used to separate key-value for header in String. The value must only one character.Otherwise you will get an error message | |
| Brokers | Brokers | A comma-separated list of known AMQP Brokers in the format <host>:<port> (e.g., localhost:5672). If this is set, Host Name and Port are ignored. Only include hosts from the same AMQP cluster. Supports Expression Language: true (will be evaluated using variable registry only) | ||
| Host Name | Host Name | localhost | Network address of AMQP broker (e.g., localhost). If Brokers is set, then this property is ignored. Supports Expression Language: true (will be evaluated using variable registry only) | |
| Port | Port | 5672 | Numeric value identifying Port of AMQP broker (e.g., 5671). If Brokers is set, then this property is ignored. Supports Expression Language: true (will be evaluated using variable registry only) | |
| Virtual Host | Virtual Host | Virtual Host name which segregates AMQP system for enhanced security. Supports Expression Language: true (will be evaluated using variable registry only) | ||
| User Name | User Name | User Name used for authentication and authorization. Supports Expression Language: true (will be evaluated using variable registry only) | ||
| Password | Password | Password used for authentication and authorization. Sensitive Property: true | ||
| AMQP Version | AMQP Version | 0.9.1 |
| AMQP Version. Currently only supports AMQP v0.9.1. |
| SSL Context Service | ssl-context-service | Controller Service API: SSLContextService Implementations: StandardRestrictedSSLContextService StandardSSLContextService | The SSL Context Service used to provide client certificate information for TLS/SSL connections. | |
| Use Client Certificate Authentication | cert-authentication | false |
| Authenticate using the SSL certificate rather than user name/password. |
| Client Auth | ssl-client-auth | NONE |
| The property has no effect and therefore deprecated. |
| Name | Description |
|---|---|
| success | All FlowFiles that are received from the AMQP queue are routed to this relationship |
| Name | Description |
|---|---|
| amqp$appId | The App ID field from the AMQP Message |
| amqp$contentEncoding | The Content Encoding reported by the AMQP Message |
| amqp$contentType | The Content Type reported by the AMQP Message |
| amqp$headers | The headers present on the AMQP Message |
| amqp$deliveryMode | The numeric indicator for the Message's Delivery Mode |
| amqp$priority | The Message priority |
| amqp$correlationId | The Message's Correlation ID |
| amqp$replyTo | The value of the Message's Reply-To field |
| amqp$expiration | The Message Expiration |
| amqp$messageId | The unique ID of the Message |
| amqp$timestamp | The timestamp of the Message, as the number of milliseconds since epoch |
| amqp$type | The type of message |
| amqp$userId | The ID of the user |
| amqp$clusterId | The ID of the AMQP Cluster |
| amqp$routingKey | The routingKey of the AMQP Message |
| amqp$exchange | The exchange from which AMQP Message was received |