You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is port the ReadMany API implemented by Java SDK. This API allows users to efficiently read many items from the container. This can be done via query and/or batch currently but makes the process complex and is not user friendly.
Suggested APIs
1. Single page response
Pros: It's easier to use. No complex pulling model. No users forgetting to do the HasMoreResult loop.
Cons: Stream response would need a way to join streams from multiple responses.
Pros: Follows the same model as query and other multiple page responses
Cons: Requires users to combine the results from multiple pages and know to do the HasMoreResult to fully drain the results
As per latest discussion, we have decided to go ahead with the first option (Single Page response) as we think it will be easier for our customers to use. We need to optimize on joining multiple stream responses.
This is port the ReadMany API implemented by Java SDK. This API allows users to efficiently read many items from the container. This can be done via query and/or batch currently but makes the process complex and is not user friendly.
Suggested APIs
1. Single page response
Pros: It's easier to use. No complex pulling model. No users forgetting to do the HasMoreResult loop.
Cons: Stream response would need a way to join streams from multiple responses.
2. Multiple page responses
Pros: Follows the same model as query and other multiple page responses
Cons: Requires users to combine the results from multiple pages and know to do the HasMoreResult to fully drain the results
Java PR: Azure/azure-sdk-for-java#8123
Implementation it will use Query under the covers to provide the functionality. This follows the current Java implementation.
The text was updated successfully, but these errors were encountered: