Supports Expression Language: true
|Ignore Hidden Files||false||If true and the final component of the path associated with a given event starts with a '.' then that event will not be processed.|
|Event Types to Filter On||append, close, create, metadata, rename, unlink||A comma-separated list of event types to process. Valid event types are: append, close, create, metadata, rename, and unlink. Case does not matter.|
|IOException Retries During Event Polling||3||According to the HDFS admin API for event polling it is good to retry at least a few times. This number defines how many times the poll will be retried if it throws an IOException.|
|success||A flow file with updated information about a specific event will be sent to this relationship.|
Reads Attributes: None specified.
|mime.type||This is always application/json.|
|hdfs.inotify.event.type||This will specify the specific HDFS notification event type. Currently there are six types of events (append, close, create, metadata, rename, and unlink).|
|hdfs.inotify.event.path||The specific path that the event is tied to.|
|CLUSTER||The last used transaction id is stored. This is used |
Restricted: This component is not restricted.
Input requirement: This component does not allow an incoming relationship.
GetHDFS, FetchHDFS, PutHDFS, ListHDFS