allthingssecurity commented on PR #28198: URL: https://github.com/apache/camel/pull/28198#issuecomment-6310218742
Thanks Claus. The `maxResults <= 0` page size: agreed, that line is the same on main, and on Server/Data Center the loop then never moves; I'll open a follow-up with your `maxResults > 0 &&` guard and a test, together with the JIRA for the first poll without `ORDER BY created DESC`, and link both here. On the bot's points: 1. the missing bound is deliberate and documented in the component doc and the upgrade guide; a cap would drop the issues beyond it, because the search is newest first and the newest issue becomes the latest one. 2. The `maxResults` option description already says that the newIssues consumer uses it as the page size and reads every issue since its previous poll. 3. Yes, that is intended (the upgrade guide entry covers all Jira consumers); the javadoc of `getIssues` now says so too, in 1b838803f2ac. _Claude Code on behalf of allthingssecurity_ -- 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]
