Skip to content
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

[QUERY] CosmosQuery offset parameter #17920

Closed
siarheiburliayeu opened this issue Dec 2, 2020 · 4 comments
Closed

[QUERY] CosmosQuery offset parameter #17920

siarheiburliayeu opened this issue Dec 2, 2020 · 4 comments
Assignees
Labels
azure-spring-cosmos Spring cosmos related issues. Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-author-feedback Workflow: More information is needed from author to address the issue. no-recent-activity There has been no recent activity on this issue. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that

Comments

@siarheiburliayeu
Copy link

Question
Why doesn't com.azure.spring.data.cosmos.core.query.CosmosQuery provide offset parameter?

Setup

  • com.azure:azure-spring-data-cosmos:3.1.0
@ghost ghost added needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Dec 2, 2020
@ghost
Copy link

ghost commented Dec 2, 2020

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @kushagraThapar, @anfeldma-ms

@kushagraThapar
Copy link
Member

@mbhaskar - please take a look at this issue.

@kushagraThapar kushagraThapar added the azure-spring-cosmos Spring cosmos related issues. label Dec 2, 2020
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Dec 2, 2020
@jialindai jialindai added the Client This issue points to a problem in the data-plane of the library. label Feb 20, 2021
@mbhaskar
Copy link
Member

You can use annotated queries to specify offset/limit. Please find documentation here https://docs.microsoft.com/en-us/azure/developer/java/spring-framework/how-to-guides-spring-data-cosmosdb#custom-query-execution

@kushagraThapar kushagraThapar added the needs-author-feedback Workflow: More information is needed from author to address the issue. label Mar 9, 2021
@ghost ghost added the no-recent-activity There has been no recent activity on this issue. label Mar 17, 2021
@ghost
Copy link

ghost commented Mar 17, 2021

Hi, we're sending this friendly reminder because we haven't heard back from you in a while. We need more information about this issue to help address it. Please be sure to give us your input within the next 7 days. If we don't hear back from you within 14 days of this comment the issue will be automatically closed. Thank you!

@ghost ghost closed this as completed Mar 31, 2021
azure-sdk pushed a commit to azure-sdk/azure-sdk-for-java that referenced this issue Apr 22, 2022
Healthcareapis microsoft.healthcare apis 2022 01 31 preview (Azure#17920)

* Adds base for updating Microsoft.HealthcareApis from version preview/2021-06-01-preview to version 2021-11-01

* Updates readme

* Updates API version in new specs and examples

* Initial updates for 2021-11-01 version

* Fix prettier errors and resolve systemData error

* Add missing type definitions

* Remove pattern for validating Cors Origin.  Regex was found to have DDoS issues.  New correct pattern triggeres backwards breaking change alerts.  Removing patterns in latest iteration to avoid error.  Regexes are validated service side with updated logic already.

* Add missing endtime from OperationResult

* Revert CorsOriginEntry pattern removal to avoid false positive cross version breaking change

* Add definition for Properties property in operation definition that was missing.

* Test updating default verison per recommendation

* Update services and workspaces to use some provisioning state to remove .NET SDK error

* Resolve System.InvalidOperationException: Swagger document contains two or more x-ms-enum extensions with the same name 'ManagedServiceIdentityType' and different values: SystemAssigned,None vs. None,SystemAssigned,UserAssigned,SystemAssigned,UserAssigned

* Revert "Resolve System.InvalidOperationException: Swagger document contains two or more x-ms-enum extensions with the same name 'ManagedServiceIdentityType' and different values: SystemAssigned,None vs. None,SystemAssigned,UserAssigned,SystemAssigned,UserAssigned"

This reverts commit d44373c296808b50764b648279c60590a104a4b8.

* Resolve System.InvalidOperationException: Swagger document contains two or more x-ms-enum extensions with the same name 'ManagedServiceIdentityType' and different values: SystemAssigned,None vs. None,SystemAssigned,UserAssigned,SystemAssigned,UserAssigned"

* Change default back to 2021-01-11 version

* Change default version back in 2021-11-01 in anticipation of new release

* Revert changes that removed common-type references for local references

* Add async headers to patch examples

* Add managed identity settings to dicomservices

* Add resourceVersionPolicyCOnfiguration to workspaces/fhirservices

* Fix prettier errors

* Add missing description for resourceTypeOverrides

* Add missing  "x-ms-identifiers" property for arrays.

* add preview version 2021-11-01

* add api version 2022-01-31-preview

* fix path

* trigger GitHub actions

* fix path

Co-authored-by: Dustin Burson <47367432+dustinburson@users.noreply.github.com>
Co-authored-by: Dustin Burson <duburson@microsoft.com>
@github-actions github-actions bot locked and limited conversation to collaborators Apr 12, 2023
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
azure-spring-cosmos Spring cosmos related issues. Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-author-feedback Workflow: More information is needed from author to address the issue. no-recent-activity There has been no recent activity on this issue. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Projects
None yet
Development

No branches or pull requests

4 participants