[
https://issues.apache.org/jira/browse/NIFI-4533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16302656#comment-16302656
]
Milan Das commented on NIFI-4533:
---------------------------------
I think the fix will very similar to NIFI-4715. maxTimestamp should be
instantiated with lastModified
https://issues.apache.org/jira/browse/NIFI-4715
{code}
long maxTimestamp = 0L; \\is a bug should be long maxTimestamp=lastModified
{code}
> ListGCSBucket Returns Duplicate FlowFiles
> -----------------------------------------
>
> Key: NIFI-4533
> URL: https://issues.apache.org/jira/browse/NIFI-4533
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.3.0, 1.4.0
> Reporter: James Wing
> Priority: Minor
>
> The ListGCSBucket processor returns duplicate flowfiles under some unknown
> circumstances. Dan Young reported the issue to the dev list (see
> [ListGCSBucket and
> duplicates|http://apache-nifi.1125220.n5.nabble.com/ListGCSBucket-and-duplicates-td19633.html]).
> I was able to reproduce this issue by writing a constant stream of objects to
> a GCS bucket, while running ListGCBucket on a 30-second schedule reading the
> bucket and DetectDuplicate with a Cache Entry Identifier of $\{gcs.key}.
> Using a DetectDuplicate processor immediately following ListGCSBucket is also
> an effective workaround.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
