Writes the content of the incoming FlowFiles to the configured Azure Queue Storage.
azure, microsoft, cloud, storage, queue, enqueue
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 Name | Queue Name | Name of the Azure Storage Queue Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) | ||
| Endpoint Suffix | storage-endpoint-suffix | queue.core.windows.net | Storage accounts in public Azure always use a common FQDN suffix. Override this endpoint suffix with a different suffix in certain circumstances (like Azure Stack or non-public Azure regions). | |
| Credentials Service | Credentials Service | Controller Service API: AzureStorageCredentialsService_v12 Implementations: AzureStorageCredentialsControllerServiceLookup_v12 AzureStorageCredentialsControllerService_v12 | Controller Service used to obtain Azure Storage Credentials. | |
| Message Time To Live | Message Time To Live | 7 days | Maximum time to allow the message to be in the queue | |
| Visibility Timeout | Visibility Timeout | 30 secs | The length of time during which the message will be invisible after it is read. If the processing unit fails to delete the message after it is read, then the message will reappear in the queue. | |
| Request Timeout | Request Timeout | 10 secs | The timeout for read or write requests to Azure Queue Storage. Defaults to 1 second. | |
| Proxy Configuration Service | proxy-configuration-service | Controller Service API: ProxyConfigurationService Implementation: StandardProxyConfigurationService | Specifies the Proxy Configuration Controller Service to proxy network requests. Supported proxies: HTTP, SOCKS In case of SOCKS, it is not guaranteed that the selected SOCKS Version will be used by the processor. |
| Name | Description |
|---|---|
| success | All successfully processed FlowFiles are routed to this relationship |
| failure | Unsuccessful operations will be transferred to the failure relationship. |