gitPratikSingh opened a new pull request, #29656: URL: https://github.com/apache/camel/pull/29656
In camel-minio, `maxMessagesPerPoll` only set the S3 listing page size, so a single poll kept paging through the bucket and routed every object in it. This change caps the listing at `maxMessagesPerPoll`, so one poll processes at most that many objects (one page per poll, mirroring the AWS2 S3 consumer), with the continuation token derived from what the poll actually listed. Changes: - `MinioConsumer`: listing is capped per poll; the continuation token is taken from the objects the poll listed (cleared when the listing is exhausted, unchanged when a listing request fails). - New regression test `MinioConsumerMaxMessagesPerPollTest`: 30 objects with a limit of 10 asserts polls of 10/10/10 in listing order and that no poll exceeds the limit. - 4.24 upgrade guide entry noting the behavior change. JIRA: https://issues.apache.org/jira/browse/CAMEL-26653 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
