Peter Kimberley created NIFI-12594:
--------------------------------------
Summary: ListS3 minimum object age filter not observed when entity
state tracking is used
Key: NIFI-12594
URL: https://issues.apache.org/jira/browse/NIFI-12594
Project: Apache NiFi
Issue Type: Bug
Components: Extensions
Affects Versions: 1.24.0
Environment: Docker, on-prem S3
Reporter: Peter Kimberley
When ListS3 is configured to use the {{Tracking Entities}} listing strategy,
the following is observed:
# Configure ListS3 with a Minimum Object Age of {{1 hour.}} Ensure processor
is stopped.
# Create a new FlowFile with GenerateFlowFile and run once
# Put the FlowFile to an S3 bucket with PutS3
# Open ListS3 configuration
# Click Verify. UI reports: ??Successfully listed contents of bucket <bucket
name>, finding 0 objects matching the filter.??
# Run ListS3 once. Flowfile is retrieved, even though the 1 hour has not yet
elapsed.
The issue is the ListS3 {{Minimum Object Age}} property is not being observed
when using the Tracking Entities listing strategy. When using {{{}Tracking
Timestamps{}}}, the processor behaves as expected.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
