[jira] [Commented] (NIFI-12936) ListGCSBucket should reset its tracking state after configuration change
[ https://issues.apache.org/jira/browse/NIFI-12936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17830650#comment-17830650 ] ASF subversion and git services commented on NIFI-12936: Commit e97431f0604fccad84c79048758eed567db117e1 in nifi's branch refs/heads/support/nifi-1.x from Peter Turcsanyi [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=e97431f060 ] NIFI-12936 ListGCSBucket resets its tracking state after configuration change Signed-off-by: Pierre Villard This closes #8563. > ListGCSBucket should reset its tracking state after configuration change > > > Key: NIFI-12936 > URL: https://issues.apache.org/jira/browse/NIFI-12936 > Project: Apache NiFi > Issue Type: Bug >Reporter: Peter Turcsanyi >Assignee: Peter Turcsanyi >Priority: Major > Fix For: 2.0.0-M3 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Same as NIFI-12732 but for ListGCSBucket. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12936) ListGCSBucket should reset its tracking state after configuration change
[ https://issues.apache.org/jira/browse/NIFI-12936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17830541#comment-17830541 ] ASF subversion and git services commented on NIFI-12936: Commit a9e246956cee822e407b20e45930e05c3fd72de6 in nifi's branch refs/heads/main from Peter Turcsanyi [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=a9e246956c ] NIFI-12936 ListGCSBucket resets its tracking state after configuration change Signed-off-by: Pierre Villard This closes #8550. > ListGCSBucket should reset its tracking state after configuration change > > > Key: NIFI-12936 > URL: https://issues.apache.org/jira/browse/NIFI-12936 > Project: Apache NiFi > Issue Type: Bug >Reporter: Peter Turcsanyi >Assignee: Peter Turcsanyi >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Same as NIFI-12732 but for ListGCSBucket. -- This message was sent by Atlassian Jira (v8.20.10#820010)