[SQSERVICES-1773] Allow pagination for team search endpoints - has_more

[battermann]

This is an extension of #2895 and adds the has_more field to the search result.

https://wearezeta.atlassian.net/browse/SQSERVICES-1773

Checklist

• No new changelog entry needed as this already exists in the base PR
• Read and follow the PR guidelines

[mdimjasevic]

Please add a changelog. You can extend the one from the previous PR by listing both PR numbers, which should look nice in the release notes.

The part I didn't get is +1; a comment is inlined.

Furthermore, is there a way for the API user to iterate over result pages?

[mdimjasevic]

Why is it + 1?

[battermann]

Please add a changelog. You can extend the one from the previous PR by listing both PR numbers, which should look nice in the release notes.

The part I didn't get is +1; a comment is inlined.

Good points, I'll add a comment about the +1 and update the changelog.

Furthermore, is there a way for the API user to iterate over result pages?

Not sure what you mean exactly. This PR adds the has_more field. If it is true, it means that there is a next page. They can use the paging_state and include it in a request, and this will give them the next page.

[mdimjasevic]

Furthermore, is there a way for the API user to iterate over result pages?

Not sure what you mean exactly. This PR adds the has_more field. If it is true, it means that there is a next page. They can use the paging_state and include it in a request, and this will give them the next page.

Ok, that's what I was asking about. Thanks for clarifying.

Given the experience with the Cassandra paging endpoints, I expect client devs to be asking how to use this Es paging system. Perhaps it'd be good to include a thorough description in Swagger analogous to the way the Cassandra paging endpoints have it, by extending the endpoint description.

[battermann]

Given the experience with the Cassandra paging endpoints, I expect client devs to be asking how to use this Es paging system. Perhaps it'd be good to include a thorough description in Swagger analogous to the way the Cassandra paging endpoints have it, by extending the endpoint description.

I updated the docs, and tried to be more clear. From the client perspective, ES's and C*'s paging mechanisms works exactly the same. In other words, the API is the same (only the implementation differs). So I assume they are already fairly familiar with it. However, it can't hurt to be more clear.