Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
3.0.0.RC3
-
None
-
Unknown
Description
When checking for the existence of the bucket the AWS S3 endpoint does not respect the values set with maxMessagesPerPoll [1]. Although it's not a severe problem, it may lead to a small degradation in the route startup when dealing with very larger buckets or simply an undesired behavior for users setting the maxMessagesPerPoll option.
I'll send a PR for this.
Attachments
Issue Links
- links to