You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Andrea Cosentino (Jira)" <ji...@apache.org> on 2021/10/18 12:01:00 UTC

[jira] [Commented] (CAMEL-17100) Minio Consumer doesn't take into account the maxMessagesPerPoll configuration

    [ https://issues.apache.org/jira/browse/CAMEL-17100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17429974#comment-17429974 ] 

Andrea Cosentino commented on CAMEL-17100:
------------------------------------------

The behavior seems to be correct, but the initial listing is really slow.

> Minio Consumer doesn't take into account the maxMessagesPerPoll configuration
> -----------------------------------------------------------------------------
>
>                 Key: CAMEL-17100
>                 URL: https://issues.apache.org/jira/browse/CAMEL-17100
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-minio
>    Affects Versions: 3.11.3, 3.12.0
>            Reporter: Andrea Cosentino
>            Assignee: Andrea Cosentino
>            Priority: Major
>             Fix For: 3.13.0, 3.11.4
>
>
> Instead it is taking into account the value from the ScheduledBatchPollingConsumer, which is not defined. If you have a bucket with a lot of files, the result is a long waiting time, for listing the object in the bucket and the consumer will start really later.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)