[NIFI-12594] ListS3 minimum object age filter not observed when entity state tracking is used

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.24.0, 2.0.0-M2
• Fix Version/s: 1.25.0, 2.0.0-M2
• Component/s: Extensions
• Environment: Docker, on-prem S3
• Assignee: Peter Kimberley
• Reporter: Peter Kimberley
• Created: 10/Jan/24 10:40
• Updated: 15/Jan/24 12:06
• Resolved: 15/Jan/24 12:06

Description

When ListS3 is configured to use the Tracking Entities listing strategy, the following is observed:

1. Configure ListS3 with a Minimum Object Age of 1 hour. Ensure processor is stopped.
2. Create a new FlowFile with GenerateFlowFile and run once
3. Put the FlowFile to an S3 bucket with PutS3
4. Open ListS3 configuration
5. Click Verify. UI reports: Successfully listed contents of bucket <bucket name>, finding 0 objects matching the filter.
6. Run ListS3 once. Flowfile is retrieved, even though the 1 hour interval 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.

Issue Links

• links to: GitHub Pull Request #8231