-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Search: ListIndexes operation should return a pageable collection #11053
Comments
Currently, the model returns themselves aren't pageable, but if they ever became pageable we'd be ready without a breaking change. That said, I imagine that all of these in the |
@brjohnstmsft might some of these methods ever become pageable, such that we should make the return types pageable now so these aren't breaking changes later (well, we wouldn't break the API, but would have to add overloads which isn't ideal). |
@brjohnstmsft Index and Indexer limits for S3 were pretty high. If there's any chance the service would return a nextLink or something in the future, we should make it pageable now. /cc @pakrym |
@heaths The max indexer count is 200; that's not high. Indexes can get up to 3000 in case of S3HD. So far that hasn't been enough to motivate us to introduce paging. We're looking at allowing more fields per index, which would increase the response size for this API, so maybe we can consider nextLink in the future. If you want to be maximally defensive against breaking changes, maybe make listing indexes pageable. For the other resources, I would say whether you make it pageable or not should depend on how much that degrades the developer experience, because the chances of us making those APIs return nextLink is very low. |
No, 200 isn't that high but if properties increase that still gets pretty big. Key Vault, in comparison, has pretty small pages. Making only GetIndexes pageable carries the concern about inconsistency, since enumerating a pageable method uses different code. |
Should we make all these
Get*s
Pageable<T>
? We can discuss it after this Preview with Bruce to get an idea of how these features might grow over time.Originally posted by @tg-msft in #11049
The text was updated successfully, but these errors were encountered: