[ https://issues.apache.org/jira/browse/NIFI-12732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17814844#comment-17814844 ]
ASF subversion and git services commented on NIFI-12732: -------------------------------------------------------- Commit 47c41ba8d72d3f3494d42f6d4c32da53fc009a7b in nifi's branch refs/heads/support/nifi-1.x from Peter Turcsanyi [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=47c41ba8d7 ] NIFI-12732 ListS3 resets its tracking state after configuration change This closes #8360. Signed-off-by: Tamas Palfy <tpa...@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: 1h 10m > 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)