-
Suggestion
-
Resolution: Unresolved
-
None
Since the change regarding the start parameter for the Confluence search api, we adapted our app to load data using the cursor API. We need to load all data before rendering the view to the user. As there is a limitation of 200 records per call for the search confluence api, we used to use parallel requests using the start parameter. Now, with the cursor parameter, we need to do the same work sequentially, unfortunately that increases the load time significantly.
Our customers are reporting important lag time, unfortunately we cannot do much about…
Is it possible to increase the current limitation of 200 records per page to a higher value (ideally 1000), that will decrease significantly the number of calls and thus reduces the load time?
- from a Confluence app developer
[AI-678] Increase the search API limitation of 200 records per search results page
Component/s | Original: Search - Core [ 46383 ] | |
Component/s | Original: Ecosystem - API Framework [ 46317 ] | |
Component/s | New: Search - Core [ 75296 ] | |
Component/s | New: Admin Experience [ 74216 ] | |
Key | Original: CONFCLOUD-70643 | New: AI-678 |
QA Demo Status | Original: Not Done [ 14330 ] | |
QA Kickoff Status | Original: Not Done [ 14234 ] | |
Project | Original: Confluence Cloud [ 18513 ] | New: Atlassian Intelligence [ 23110 ] |
Component/s | Original: Search - Scaling [ 61411 ] |
Component/s | New: Search - Core [ 46383 ] |
Comment | [ A comment with security level 'atlassian-staff' was removed. ] |
Status | Original: Gathering Interest [ 11772 ] | New: Gathering Interest [ 11772 ] |
Component/s | New: Core - APIs [ 46317 ] |
Hi David/Team,
Can you please share an update regarding this request?
Thank you !