[jira] [Commented] (NIFI-12732) ListS3 should reset its tracking state after configuration change

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-12732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17814831#comment-17814831 ] 

ASF subversion and git services commented on NIFI-12732:
--------------------------------------------------------

Commit 8f63e928a9d1ed5c3bf90ebf9766b5fcf4655e46 in nifi's branch refs/heads/main from Peter Turcsanyi
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=8f63e928a9 ]

NIFI-12732 ListS3 resets its tracking state after configuration change

This closes #8348.

Signed-off-by: Tamas Palfy <tp...@apache.org>


> ListS3 should reset its tracking state after configuration change
> -----------------------------------------------------------------
>
>                 Key: NIFI-12732
>                 URL: https://issues.apache.org/jira/browse/NIFI-12732
>             Project: Apache NiFi
>          Issue Type: Bug
>            Reporter: Peter Turcsanyi
>            Assignee: Peter Turcsanyi
>            Priority: Major
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> {{List}} processors can reset their listing tracking state (stored in the component state or in a distributed cache depending on the {{{}Listing Strategy{}}}) when a relevant property has been modified (e.g. the directory to list). The functionality was implemented in {{{}AbstractListProcessor{}}}, the child processors only need to provide the property list when the reset should occur.
> {{ListS3}} is not a child of {{AbstractListProcessor}} and the listing logic was implemented separately. The reset function is missing in the processor.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)