Welcome to the Jazz Community Forum
Paged OSLC query result limited to 100 ?
In our implementation the XML Data source is retrieved from an OSLC query to the JTS Server.
By setting XML Data source to the value :
https://<server-name>:<port>/ccm/oslc/contexts/<id of project AREA/workitems?oslc_cm.query=dc:type=%22component%22&oslc_cm.pageSize=100&oslc_cm.properties=dc:title
Im a able to retreive and process 100 WI, but if there are more than 100 I receive an exception. This is because the query is paginated and the maximum page size is of 100.
Is there any way to increase the page size to more than 100 ?
Can we reset the pagination before running the query ?
We checked that in the server (ccm) there is a property called 'Maximum Query Result Set Size' set to 1000
and another property (jts) called 'Max Number of Entries Returned from User Search' set to 100.
We don't know what they are exactly for – can it help us increasing the limit to be more than 100 in our case ?
Please advise, this limitation could have a severe impact our implementation.
Accepted answer
you could handle the resource paging feature as described in the Pagination section of this article:
https://jazz.net/library/article/1001#advanced_concepts
Regards,
Stéphane
Comments
Hi Stephane,
Thanks for pointing out to this article.
There is indeed a nice section about Pagination that explains how can we handle it, but in our implementation what we need is to increase the maximum page size to handle more than 100 WIs.
If we try to set oslc_cm.pageSize to a value superior to 100 for example, the page size is automatically set back to default value (50).
We can handle that with a script following the recomendation of the article but we would prefer increase the maximum page size or disable pagination in the same query.
It seems to be working as designed for that OSLC services.
I will open an RFE.
Thanks again for your help.
Regards,
Armand
Hi Armand,
seems like what you depict was experienced before:
https://jazz.net/forum/questions/73265/max-100-results/
https://jazz.net/forum/questions/68752/cm-rest-api-simpe-query-results-limitted-to-50/
FYI, a previous answer in
https://jazz.net/forum/questions/85641/rtc-returns-only-50-work-items-when-it-is-accessed-though-oslc-query points to an already existing RFE (will save you time maybe):
https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=228310/
My guess is that we don't want the CLM server to be overloaded with possibly very large OSLC requests. But again, just a guess. You should get more details along with this RFE tracking/analysis.
Regards,
Stéphane
Thanks again stephane for your help.
The RFE link was very useful.
Regards.
Armand.
2 other answers
Max Feed Entries/Page , in the advanced properties?
Comments
Hi Srikanth,
Thanks for your reply !
Unfortunately, changing this value does not have any effect on the result of the ccm oslc query.
Regards,
Armand.
Currently, the number of WIs is limited to 100. I have implemented paging like:
- Get the first page, it contains totalCount.
- Get oslc:totalCount, then determine the number of pages divided by 100.
-
Get next page by adding &_startIndex='<next page>' to query syntax.
3 loops until page is last page. The key is to specify "_startindex".
Hope this helps
Thanks Takehiko !
This will help if we decide to implement the paging.
However, we prefer to push for the existing RFE for have raised to raise the existing limit.
Regards.
Armand.
The simple way to do it is to :
- Do the initial query
- get datas
- Get the oslc_cm:next attribute in oslc_cm:Collection
- if oslc_cm:next is set, go to 1 with the oslc_cm:next as the resource url and loop