File Cleanup Policies
The commons configuration for Connect File Pulse.
The connector can be configured with a specific FileCleanupPolicy implementation.
The cleanup policy can be configured with the below connect property :
Configuration | Description | Type | Default | Importance |
---|---|---|---|---|
fs.cleanup.policy.class | The fully qualified name of the class which is used to cleanup files | class | - | high |
Available Cleanup Policies
DeleteCleanPolicy
This policy deletes all files regardless of their final status (completed or failed).
To enable this policy, the property fs.cleanup.policy.class
must be configured to :
io.streamthoughts.kafka.connect.filepulse.fs.clean.DeleteCleanupPolicy
LogCleanPolicy
This policy prints into logs some information after files completion.
To enable this policy, the property fs.cleanup.policy.class
must be configured to :
io.streamthoughts.kafka.connect.filepulse.fs.clean.LogCleanupPolicy
LocalMoveCleanupPolicy
This policy attempts to move atomically files to configurable target directories.
To enable this policy, the property fs.cleanup.policy.class
must be configured to :
io.streamthoughts.kafka.connect.filepulse.fs.clean.LocalMoveCleanupPolicy
Usage
This policy only works when using theLocalFSDirectoryListing
.Configuration
Configuration | Description | Type | Default | Importance |
---|---|---|---|---|
cleaner.output.failed.path | Target directory for file proceed with failure | string | .failure | high |
cleaner.output.succeed.path | Target directory for file proceed successfully | string | .success | high |
Implementing your own policy
Last modified March 2, 2022: docs: fix missing archive (ffdb9ab7)