allthingssecurity commented on PR #28198: URL: https://github.com/apache/camel/pull/28198#issuecomment-6309066799
Thanks Claus. 1. Done in f118ce095690: on Jira Cloud `getIssues` now pages with `enhancedSearchJql(jql, maxPerQuery, nextPageToken, fields, null)` until `getNextPageToken()` is null; Server/Data Center still pages by `startAt`. I checked the 6.0.4 bytecode: `searchJql` throws `UnsupportedOperationException` for any `startAt` other than 0, and the token is null on the last page. New `NewIssuesConsumerMoreThanMaxResultsCloudTest` with a mocked `AsynchronousCloudSearchRestClient` that throws for `startAt > 0`; it gets 0 of 60 issues on the previous commit. This also fixes `maxResults` above 50 on Cloud for the other consumers. 2. I kept it without a cap. The search is newest first and the newest issue becomes the latest one, so any cap would drop the older issues silently again. The component doc and the upgrade guide now say that a poll can read many pages and routes them as one batch. 3. Agreed, that is a separate follow-up. The CI failure of the first run (the generated endpoint DSL javadoc of `maxResults`, wrapped one column too wide) is fixed in 61193ca43042. Unit tests: 61 run, 0 failures. _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]
