[
https://issues.apache.org/jira/browse/NIFI-6636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16925943#comment-16925943
]
ASF subversion and git services commented on NIFI-6636:
-------------------------------------------------------
Commit 21a27c8bb00c3f41836c938c3bb59ff428a27ca4 in nifi's branch
refs/heads/master from Peter Turcsanyi
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=21a27c8 ]
NIFI-6636: Fixed ListGCSBucket file duplication error
ListGCSBucket duplicated files if they arrived not in alphabetical order.
The set storing the name of the latest blob (which was loaded with the highest
timestamp during the previous run of the processor) was cleared too early.
Also changed the state persisting logic: it is now saved only once at the end
of onTrigger() (similar to ListS3). Some inconsistent state (only blob names
without the timestamp) was also saved earlier.
This closes #3702.
Signed-off-by: Mark Payne <[email protected]>
> ListGCSBucket duplicates files if they arrive not in alphabetical order
> -----------------------------------------------------------------------
>
> Key: NIFI-6636
> URL: https://issues.apache.org/jira/browse/NIFI-6636
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.9.2
> Reporter: Peter Turcsanyi
> Assignee: Peter Turcsanyi
> Priority: Major
> Time Spent: 1h
> Remaining Estimate: 0h
>
> If the files are being uploaded to the bucket NOT in alphabetical order, then
> the last loaded file will be reloaded again at the next run of the processor.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
