[
https://issues.apache.org/jira/browse/NIFI-12594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17806696#comment-17806696
]
ASF subversion and git services commented on NIFI-12594:
--------------------------------------------------------
Commit 3ebad40fae458db3fe664ddd6738b770a26289c8 in nifi's branch
refs/heads/main from p-kimberley
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=3ebad40fae ]
NIFI-12594: ListS3 - observe min/max object age when entity state tracking is
used
This closes #8231.
Signed-off-by: Peter Turcsanyi <turcsa...@apache.org>
> 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, 2.0.0
> Environment: Docker, on-prem S3
> Reporter: Peter Kimberley
> Priority: Major
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> 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 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
