Please be aware this processor is deprecated and may be removed in the near future.
Please consider using one the following alternatives: PutAzureQueueStorage_v12
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 |
|---|---|---|---|---|
| Storage Credentials | storage-credentials-service | Controller Service API: AzureStorageCredentialsService Implementations: AzureStorageCredentialsControllerServiceLookup AzureStorageCredentialsControllerService AzureStorageEmulatorCredentialsControllerService | The Controller Service used to obtain Azure Storage Credentials. Instead of the processor level properties, the credentials can be configured here through a common/shared controller service, which is the preferred way. The 'Lookup' version of the service can also be used to select the credentials dynamically at runtime based on a FlowFile attribute (if the processor has FlowFile input). | |
| Storage Account Name | storage-account-name | The storage account name. There are certain risks in allowing the account name to be stored as a flowfile attribute. While it does provide for a more flexible flow by allowing the account name to be fetched dynamically from a flowfile attribute, care must be taken to restrict access to the event provenance data (e.g., by strictly controlling the policies governing provenance for this processor). In addition, the provenance repositories may be put on encrypted disk partitions. Instead of defining the Storage Account Name, Storage Account Key and SAS Token properties directly on the processor, the preferred way is to configure them through a controller service specified in the Storage Credentials property. The controller service can provide a common/shared configuration for multiple/all Azure processors. Furthermore, the credentials can also be looked up dynamically with the 'Lookup' version of the service. Sensitive Property: true Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) | ||
| Storage Account Key | storage-account-key | The storage account key. This is an admin-like password providing access to every container in this account. It is recommended one uses Shared Access Signature (SAS) token instead for fine-grained control with policies. There are certain risks in allowing the account key to be stored as a flowfile attribute. While it does provide for a more flexible flow by allowing the account key to be fetched dynamically from a flowfile attribute, care must be taken to restrict access to the event provenance data (e.g., by strictly controlling the policies governing provenance for this processor). In addition, the provenance repositories may be put on encrypted disk partitions. Sensitive Property: true Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) | ||
| SAS Token | storage-sas-token | Shared Access Signature token, including the leading '?'. Specify either SAS token (recommended) or Account Key. There are certain risks in allowing the SAS token to be stored as a flowfile attribute. While it does provide for a more flexible flow by allowing the SAS token to be fetched dynamically from a flowfile attribute, care must be taken to restrict access to the event provenance data (e.g., by strictly controlling the policies governing provenance for this processor). In addition, the provenance repositories may be put on encrypted disk partitions. Sensitive Property: true Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) | ||
| Common Storage Account Endpoint Suffix | storage-endpoint-suffix | 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). The preferred way is to configure them through a controller service specified in the Storage Credentials property. The controller service can provide a common/shared configuration for multiple/all Azure processors. Furthermore, the credentials can also be looked up dynamically with the 'Lookup' version of the service. Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) | ||
| TTL | time-to-live | 7 days | Maximum time to allow the message to be in the queue. If left empty, the default value of 7 days will be used. | |
| Queue Name | storage-queue-name | Name of the Azure Storage Queue Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) | ||
| Visibility Delay | visibility-delay | 0 secs | The length of time during which the message will be invisible, starting when it is added to the queue. This value must be greater than or equal to 0 and less than the TTL value. | |
| 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. |