-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: Paginator For OpenSearch Client #3245
Comments
With this change, we can use paginator for the OpenSearch APIs with Max Results limit, instead of looping with NextToken manually. fixes: boto#3245
With this change, we can use paginator for the OpenSearch APIs with Max Results limit, instead of looping with NextToken manually. fixes: boto#3245
With this change, we can use paginator for the OpenSearch APIs with Max Results limit, instead of looping with NextToken manually. fixes: boto#3245
Thanks for the feature request and for creating that PR. Paginator models are owned and maintained upstream by service teams, because they are used across AWS SDKs. Therefore the OpenSearch team would need to release these paginator models directly in order for SDKs like Boto3 to use them. I have created an internal feature request for that service team to add the paginator models from your PR. I'm going to close this since the feature request won't be tracked here, but please refer to the CHANGELOG for future updates. |
This issue is now closed. Comments on closed issues are hard for our team to see. |
Describe the feature
Add paginator support for OpenSearch Client.
Use Case
With this feature, we can use
paginator
for the OpenSearch APIs with Max Results limit, instead of looping withNextToken
manually. Something likeProposed Solution
Update
paginators-1.json
of opensearchOther Information
No response
Acknowledgements
SDK version used
Python SDK Botocore 1.x
Environment details (OS name and version, etc.)
macos
The text was updated successfully, but these errors were encountered: