Lists blobs in an Azure Blob Storage container. Listing details are attached to an empty FlowFile for use with FetchAzureBlobStorage. This Processor is designed to run on Primary Node only in a cluster. If the primary node changes, the new Primary Node will pick up where the previous node left off without duplicating all of the data. The processor uses Azure Blob Storage client library v12.
| Display Name | API Name | Default Value | Allowable Values | Description |
|---|
| Storage Credentials | storage-credentials-service | | Controller Service API:
AzureStorageCredentialsService_v12
Implementations: AzureStorageCredentialsControllerService_v12
AzureStorageCredentialsControllerServiceLookup_v12 | Controller Service used to obtain Azure Blob Storage Credentials. |
| Container Name | container-name | | | Name of the Azure storage container. In case of PutAzureBlobStorage processor, container can be created if it does not exist.
Supports Expression Language: true (will be evaluated using variable registry only) |
| Blob Name Prefix | blob-name-prefix | | | Search prefix for listing
Supports Expression Language: true (will be evaluated using variable registry only) |
| Record Writer | record-writer | | Controller Service API:
RecordSetWriterFactory
Implementations: JsonRecordSetWriter
RecordSetWriterLookup
AvroRecordSetWriter
XMLRecordSetWriter
FreeFormTextRecordSetWriter
CSVRecordSetWriter
ParquetRecordSetWriter
ScriptedRecordSetWriter | Specifies the Record Writer to use for creating the listing. If not specified, one FlowFile will be created for each entity that is listed. If the Record Writer is specified, all entities will be written to a single FlowFile instead of adding attributes to individual FlowFiles. |
| Listing Strategy | listing-strategy | Tracking Timestamps | - Tracking Timestamps
 - Tracking Entities
- No Tracking
| Specify how to determine new/updated entities. See each strategy descriptions for detail. |
| Entity Tracking State Cache | et-state-cache | | Controller Service API:
DistributedMapCacheClient
Implementations: CassandraDistributedMapCache
SimpleRedisDistributedMapCacheClientService
CouchbaseMapCacheClient
HBase_2_ClientMapCacheService
DistributedMapCacheClientService
RedisDistributedMapCacheClientService
HazelcastMapCacheClient | Listed entities are stored in the specified cache storage so that this processor can resume listing across NiFi restart or in case of primary node change. 'Tracking Entities' strategy require tracking information of all listed entities within the last 'Tracking Time Window'. To support large number of entities, the strategy uses DistributedMapCache instead of managed state. Cache key format is 'ListedEntities::{processorId}(::{nodeId})'. If it tracks per node listed entities, then the optional '::{nodeId}' part is added to manage state separately. E.g. cluster wide cache key = 'ListedEntities::8dda2321-0164-1000-50fa-3042fe7d6a7b', per node cache key = 'ListedEntities::8dda2321-0164-1000-50fa-3042fe7d6a7b::nifi-node3' The stored cache content is Gzipped JSON string. The cache key will be deleted when target listing configuration is changed. Used by 'Tracking Entities' strategy.
This Property is only considered if the [Listing Strategy] Property has a value of "Tracking Entities". |
| Entity Tracking Time Window | et-time-window | 3 hours | | Specify 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.
Supports Expression Language: true (will be evaluated using variable registry only)
This Property is only considered if the [Listing Strategy] Property has a value of "Tracking Entities". |
| Entity Tracking Initial Listing Target | et-initial-listing-target | All Available | - Tracking Time Window
- All Available
| Specify how initial listing should be handled. Used by 'Tracking Entities' strategy.
This Property is only considered if the [Listing Strategy] Property has a value of "Tracking Entities". |
| Minimum File Age | Minimum File Age | 0 sec | | The 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 |
| Maximum File Age | Maximum File Age | | | The 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 |
| Minimum File Size | Minimum File Size | 0 B | | The minimum size that a file must be in order to be pulled |
| Maximum File Size | Maximum File Size | | | The maximum size that a file can be in order to be pulled |
| 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. |