GetFile 2.3.0

BUNDLE

org.apache.nifi | nifi-standard-nar

DESCRIPTION

Creates FlowFiles from files in a directory. NiFi will ignore files it doesn’t have at least read permissions for.

TAGS

files, filesystem, get, ingest, ingress, input, local, source

INPUT REQUIREMENT

FORBIDDEN

Supports Sensitive Dynamic Properties

false

PROPERTIES

Property

Description

Batch Size

The maximum number of files to pull in each invocation of the processor

File Filter

Only files whose names match the given regular expression will be picked up

Ignore Hidden Files

Indicates whether or not hidden files should be ignored

Input Directory

The input directory from which to pull files

Keep Source File

If true, the file is not deleted after it has been copied to the Content Repository; this causes the file to be picked up continually and is useful for testing purposes. If not keeping original NiFi will need write permissions on the directory it is pulling from otherwise it will ignore the file.

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

Maximum File Size

The maximum size that a file can be in order to be pulled

Minimum File Age

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

Minimum File Size

The minimum size that a file must be in order to be pulled

Path Filter

When Recurse Subdirectories is true, then only subdirectories whose path matches the given regular expression will be scanned

Polling Interval

Indicates how long to wait before performing a directory listing

Recurse Subdirectories

Indicates whether or not to pull files from subdirectories

RESTRICTIONS

REQUIRED PERMISSION

EXPLANATION

read filesystem

Provides operator the ability to read from any file that NiFi has access to.

write filesystem

Provides operator the ability to delete any file that NiFi has access to.

RELATIONSHIPS

NAME

DESCRIPTION

success

All files are routed to success

WRITES ATTRIBUTES

NAME

DESCRIPTION

filename

The filename is set to the name of the file on disk

path

The path is set to the relative path of the file’s directory on disk. For example, if the <Input Directory> property is set to /tmp, files picked up from /tmp will have the path attribute set to ./. If the <Recurse Subdirectories> property is set to true and a file is picked up from /tmp/abc/1/2/3, then the path attribute will be set to abc/1/2/3

file.creationTime

The date and time that the file was created. May not work on all file systems

file.lastModifiedTime

The date and time that the file was last modified. May not work on all file systems

file.lastAccessTime

The date and time that the file was last accessed. May not work on all file systems

file.owner

The owner of the file. May not work on all file systems

file.group

The group owner of the file. May not work on all file systems

file.permissions

The read/write/execute permissions of the file. May not work on all file systems

absolute.path

The full/absolute path from where a file was picked up. The current ‘path’ attribute is still populated, but may be a relative path

SEE ALSO

Language: English