Polling
polling inbound wraps another inbound and re-scans it on an interval, emitting only the entries that changed since the previous scan.
Use polling on top of any one-shot inbound to turn it into a live source. It works over every backend, including local filesystems and remote stores such as s3 and sftp, and is the only way to watch filesystems that do not deliver native notifications such as NFS, SMB and FUSE mounts.
Point polling at an inbound that finishes a full scan and stops, such as local, s3 or sftp. Wrapping a live inbound such as fswatch has no effect, since a live inbound never completes a scan.
Structure
Fields
inbound
Required
The tag of the inbound to poll. That inbound is not run on its own; polling drives it.
interval
Required
The interval between scans. The first scan runs immediately and emits every entry as a create; each later scan compares the upstream against the previous one and emits a create for a new entry, an update for a changed entry, and a delete for a vanished entry. Change is detected by type, size, mode and modification time.
Change Events
See Change Events for the event types emitted and how deletions are handled.