You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Luca Burgazzoli (JIRA)" <ji...@apache.org> on 2016/01/28 14:09:39 UTC
[jira] [Closed] (CAMEL-8539) S3 marker does not work
[ https://issues.apache.org/jira/browse/CAMEL-8539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Luca Burgazzoli closed CAMEL-8539.
----------------------------------
Resolution: Duplicate
> S3 marker does not work
> -----------------------
>
> Key: CAMEL-8539
> URL: https://issues.apache.org/jira/browse/CAMEL-8539
> Project: Camel
> Issue Type: Bug
> Components: camel-aws
> Affects Versions: 2.15.0
> Reporter: Alexey Hanin
> Attachments: 8539.patch
>
>
> S3Consumer doesn't set marker correctly, when {{deleteAfterRead}} is set to {{false}}. Therefore, on every subsequent poll, it starts from the beginning of the list.
> The reason for that is the following code in S3Consumer:
> {code:lang=java|title=S3Consumer.java}
> if (!getConfiguration().isDeleteAfterRead()) {
> // where marker is track
> marker = listObjects.getMarker();
> }
> {code}
> Accordingly to S3 client documentation, {{getMarker()}} return a marker previously set in request. Instead, {{getNextMarker()}} shall be used. Although, simply changing it to use {{getNextMarker()}} introduces an endless loop iterating over the same set of keys under the prefix, because when reached the end of the key set, {{getNextMarker()}} returns {{null}}, and on the next poll, the head of the list will be returned, and so on.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)