davsclaus commented on PR #30481:
URL: https://github.com/apache/camel/pull/30481#issuecomment-7036815029

   Thanks @ramu11. Let's keep this PR as it is: preparing the batch up front 
keeps the batch properties exact, and with `maxMessagesPerPoll` set it is 
bounded. Once CI is green it can go in, and it unblocks the Kamelet option for 
4.24.0.
   
   Just-in-time gets are now 
[CAMEL-27295](https://issues.apache.org/jira/browse/CAMEL-27295), as a 
follow-up. Keep `maxMessagesPerPoll` counting got blobs, not listed ones. Fetch 
one blob ahead, so that `CamelBatchIndex` and `CamelBatchComplete` stay exact 
and only `CamelBatchSize` is no longer exact (as with S3, see CAMEL-26662). 
Document that `completionFromBatchConsumer` on the aggregator does not fit this 
consumer, and add an upgrade-guide entry, since blobs are then read at routing 
time.
   
   _Claude Code on behalf of davsclaus_


-- 
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]

Reply via email to