org.apache.nifinifi-dropbox-processors-nar2.0.0org.apache.nifinifi-dropbox-services-api-nar2.0.02.0.0HEADUNKNOWN2f13b60org.apache.nifi.processors.dropbox.FetchDropboxPROCESSORFetches files from Dropbox. Designed to be used in tandem with ListDropbox.dropboxstoragefetchdropbox-credential-serviceDropbox Credential ServiceController Service used to obtain Dropbox credentials (App Key, App Secret, Access Token, Refresh Token). See controller service's Additional Details for more information.org.apache.nifi.dropbox.credentials.service.DropboxCredentialServiceorg.apache.nifinifi-dropbox-services-api-nar2.0.0truefalsefalseNONEfalsefalsefileFileThe Dropbox identifier or path of the Dropbox file to fetch. The 'File' should match the following regular expression pattern: /.*|id:.* . When ListDropbox is used for input, either '${dropbox.id}' (identifying files by Dropbox id) or '${path}/${filename}' (identifying files by path) can be used as 'File' value.${dropbox.id}truefalsetrueFLOWFILE_ATTRIBUTESfalsefalseproxy-configuration-serviceProxy Configuration ServiceSpecifies the Proxy Configuration Controller Service to proxy network requests. Supported proxies: HTTP + AuthNorg.apache.nifi.proxy.ProxyConfigurationServiceorg.apache.nifinifi-standard-services-api-nar2.0.0falsefalsefalseNONEfalsefalsesuccessA FlowFile will be routed here for each successfully fetched File.falsefailureA FlowFile will be routed here for each File for which fetch was attempted but failed.falseerror.messageThe error message returned by Dropboxdropbox.idThe Dropbox identifier of the filepathThe folder path where the file is locatedfilenameThe name of the filedropbox.sizeThe size of the filedropbox.timestampThe server modified time of the filedropbox.revisionRevision of the fileINPUT_REQUIREDorg.apache.nifi.processors.dropbox.PutDropboxorg.apache.nifi.processors.dropbox.ListDropboxorg.apache.nifi.processors.dropbox.ListDropboxPROCESSORRetrieves a listing of files from Dropbox (shortcuts are ignored). Each listed file may result in one FlowFile, the metadata being written as FlowFile attributes. When the 'Record Writer' property is set, the entire result is written as records to a single FlowFile. 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.dropboxstoragedropbox-credential-serviceDropbox Credential ServiceController Service used to obtain Dropbox credentials (App Key, App Secret, Access Token, Refresh Token). See controller service's Additional Details for more information.org.apache.nifi.dropbox.credentials.service.DropboxCredentialServiceorg.apache.nifinifi-dropbox-services-api-nar2.0.0truefalsefalseNONEfalsefalsefolderFolderThe Dropbox identifier or path of the folder from which to pull list of files. 'Folder' should match the following regular expression pattern: /.*|id:.* . Example for folder identifier: id:odTlUvbpIEAAAAAAAAAGGQ. Example for folder path: /Team1/Task1./truefalsetrueENVIRONMENTfalsefalserecursive-searchSearch RecursivelyIndicates whether to list files from subfolders of the Dropbox folder.truetruetruefalsefalsetruefalsefalseNONEfalsefalsemin-ageMinimum File AgeThe minimum age a file must be in order to be considered; any files newer than this will be ignored.0 sectruefalsefalseNONEfalsefalselisting-strategyListing StrategySpecify how to determine new/updated entities. See each strategy descriptions for detail.timestampsTracking TimestampstimestampsThis strategy tracks the latest timestamp of listed entity to determine new/updated entities. Since it only tracks few timestamps, it can manage listing state efficiently. However, any newly added, or updated entity having timestamp older than the tracked latest timestamp can not be picked by this strategy. For example, such situation can happen in a file system if a file with old timestamp is copied or moved into the target directory without its last modified timestamp being updated. Also may miss files when multiple subdirectories are being written at the same time while listing is running.Tracking EntitiesentitiesThis strategy tracks information of all the listed entities within the latest 'Entity Tracking Time Window' to determine new/updated entities. This strategy can pick entities having old timestamp that can be missed with 'Tracking Timestamps'. Works even when multiple subdirectories are being written at the same time while listing is running. However additional DistributedMapCache controller service is required and more JVM heap memory is used. See the description of 'Entity Tracking Time Window' property for further details on how it works.Time Windowtime-windowThis strategy uses a sliding time window. The window starts where the previous window ended and ends with the 'current time'. One cycle will list files with modification time falling within the time window. Works even when multiple subdirectories are being written at the same time while listing is running. IMPORTANT: This strategy works properly only if the time on both the system hosting NiFi and the one hosting the files are accurate.No TrackingnoneThis strategy lists an entity without any tracking. The same entity will be listed each time on executing this processor. It is recommended to change the default run schedule value. Any property that related to the persisting state will be disregarded.truefalsefalseNONEfalsefalseet-state-cacheEntity Tracking State CacheListed 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.org.apache.nifi.distributed.cache.client.DistributedMapCacheClientorg.apache.nifinifi-standard-services-api-nar2.0.0falsefalsefalseNONEfalsefalselisting-strategyListing Strategyentitieset-time-windowEntity 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.3 hoursfalsefalsetrueENVIRONMENTfalsefalselisting-strategyListing Strategyentitieset-initial-listing-targetEntity Tracking Initial Listing TargetSpecify how initial listing should be handled. Used by 'Tracking Entities' strategy.allTracking Time WindowwindowIgnore entities having timestamp older than the specified 'Tracking Time Window' at the initial listing activity.All AvailableallRegardless of entities timestamp, all existing entities will be listed at the initial listing activity.falsefalsefalseNONEfalsefalselisting-strategyListing Strategyentitiesrecord-writerRecord WriterSpecifies 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.org.apache.nifi.serialization.RecordSetWriterFactoryorg.apache.nifinifi-standard-services-api-nar2.0.0falsefalsefalseNONEfalsefalseproxy-configuration-serviceProxy Configuration ServiceSpecifies the Proxy Configuration Controller Service to proxy network requests. Supported proxies: HTTP + AuthNorg.apache.nifi.proxy.ProxyConfigurationServiceorg.apache.nifinifi-standard-services-api-nar2.0.0falsefalsefalseNONEfalsefalsesuccessAll FlowFiles that are received are routed to successfalsedropbox.idThe Dropbox identifier of the filepathThe folder path where the file is locatedfilenameThe name of the filedropbox.sizeThe size of the filedropbox.timestampThe server modified time of the filedropbox.revisionRevision of the filetruetrueThe processor stores necessary data to be able to keep track what files have been listed already. What exactly needs to be stored depends on the 'Listing Strategy'.CLUSTERINPUT_FORBIDDENorg.apache.nifi.processors.dropbox.FetchDropboxorg.apache.nifi.processors.dropbox.PutDropboxTIMER_DRIVEN1 min1org.apache.nifi.processors.dropbox.PutDropboxPROCESSORPuts content to a Dropbox folder.dropboxstorageputdropbox-credential-serviceDropbox Credential ServiceController Service used to obtain Dropbox credentials (App Key, App Secret, Access Token, Refresh Token). See controller service's Additional Details for more information.org.apache.nifi.dropbox.credentials.service.DropboxCredentialServiceorg.apache.nifinifi-dropbox-services-api-nar2.0.0truefalsefalseNONEfalsefalsefolderFolderThe path of the Dropbox folder to upload files to. The folder will be created if it does not exist yet./truefalsetrueFLOWFILE_ATTRIBUTESfalsefalsefile-nameFilenameThe full name of the file to upload.${filename}truefalsetrueFLOWFILE_ATTRIBUTESfalsefalseconflict-resolution-strategyConflict Resolution StrategyIndicates what should happen when a file with the same name already exists in the specified Dropbox folder.failfailfailHandle file conflict as failure.ignoreignoreIgnore conflict, do not change the original file.replacereplaceReplace existing file in case of conflict.truefalsefalseNONEfalsefalsechunked-upload-thresholdChunked Upload ThresholdThe maximum size of the content which is uploaded at once. FlowFiles larger than this threshold are uploaded in chunks. Maximum allowed value is 150 MB.150 MBfalsefalsefalseNONEfalsefalsechunked-upload-sizeChunked Upload SizeDefines the size of a chunk. Used when a FlowFile's size exceeds 'Chunked Upload Threshold' and content is uploaded in smaller chunks. It is recommended to specify chunked upload size smaller than 'Chunked Upload Threshold' and as multiples of 4 MB. Maximum allowed value is 150 MB.8 MBfalsefalsefalseNONEfalsefalseproxy-configuration-serviceProxy Configuration ServiceSpecifies the Proxy Configuration Controller Service to proxy network requests. Supported proxies: HTTP + AuthNorg.apache.nifi.proxy.ProxyConfigurationServiceorg.apache.nifinifi-standard-services-api-nar2.0.0falsefalsefalseNONEfalsefalsesuccessFiles that have been successfully written to Dropbox are transferred to this relationship.falsefailureFiles that could not be written to Dropbox for some reason are transferred to this relationship.falsefilenameUses the FlowFile's filename as the filename for the Dropbox object.error.messageThe error message returned by Dropboxdropbox.idThe Dropbox identifier of the filepathThe folder path where the file is locatedfilenameThe name of the filedropbox.sizeThe size of the filedropbox.timestampThe server modified time of the filedropbox.revisionRevision of the fileINPUT_REQUIREDorg.apache.nifi.processors.dropbox.ListDropboxorg.apache.nifi.processors.dropbox.FetchDropbox