@Karl Fredrickson The normal behavior of the ListSFTP processor is the first listing, meaning it has no state yet, will get a listing of all current files in the remote directory. The subsequent listings will get all new files, written since the last time stamp listed in the processor, except for the last one or two files. These one or two files will be listed in the next listing the processor creates and any additional new files based on the updated state for the processor, except for again the latest one or two files and so on as the processor runs. The ListSFTP processor doesn't use the file name in anyway. If you want files to be listed closer to the time they are being written to the directory, then set the processor to run more often than every 10 minutes. ... View more

@Narasimma varman If you change your regex to this ".*app_2017.*\.log" it should match only the nifi-app_2017 log files. ... View more

@xav webmaster Have you looked at using the ScanContent processor for this use case? ... View more

@dhieru singh Please post a snapshot of the section covering content repository configuration in the nifi.properties file. Specifically these properties # Content Repository nifi.content.repository.implementation=org.apache.nifi.controller.repository.FileSystemRepository nifi.content.claim.max.appendable.size=10 MB nifi.content.claim.max.flow.files=100 nifi.content.repository.directory.default=./content_repository nifi.content.repository.archive.max.retention.period=12 hours nifi.content.repository.archive.max.usage.percentage=50% nifi.content.repository.archive.enabled=true nifi.content.repository.always.sync=false nifi.content.viewer.url=/nifi-content-viewer/ ... View more

@dhieru singh What are the average sizes of the flow files coming out of the ListenUDP processor? ... View more

@sally sally Does this answer your question? ... View more