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

Utilize lease containers when consuming the change feed in CosmosDB #24249

Closed
JarroVGIT opened this issue Apr 29, 2022 · 5 comments
Closed

Utilize lease containers when consuming the change feed in CosmosDB #24249

JarroVGIT opened this issue Apr 29, 2022 · 5 comments
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. Cosmos 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. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@JarroVGIT
Copy link

Is your feature request related to a problem? Please describe.
When creating a consumer that listens to the change feed of CosmosDB, the python sdk doesn’t offer any way to use lease containers to store state of the consumer(s). This prevents using this feature in python, as there is no resilience or scalability.

Describe the solution you'd like
A similar implementation as found in the .NET sdk, where the name of the lease container is an parameter in the method returning the iterator with changes.

Describe alternatives you've considered
The alternative is to custom build this functionality every time I am writing a consumer.

Additional context
N/A

@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 Apr 29, 2022
@azure-sdk azure-sdk added Client This issue points to a problem in the data-plane of the library. Cosmos needs-team-triage Workflow: This issue needs the team to triage. labels Apr 29, 2022
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Apr 29, 2022
@tjprescott tjprescott added CXP Attention and removed needs-team-triage Workflow: This issue needs the team to triage. labels Apr 29, 2022
@tjprescott
Copy link
Member

Thanks for the question @JarroVGIT. @simorenoh can you comment on this?

@SatishBoddu-MSFT SatishBoddu-MSFT added Service Attention Workflow: This issue is responsible by Azure service team. and removed CXP Attention labels May 2, 2022
@ghost
Copy link

ghost commented May 2, 2022

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @simorenoh, @gahl-levy.

Issue Details

Is your feature request related to a problem? Please describe.
When creating a consumer that listens to the change feed of CosmosDB, the python sdk doesn’t offer any way to use lease containers to store state of the consumer(s). This prevents using this feature in python, as there is no resilience or scalability.

Describe the solution you'd like
A similar implementation as found in the .NET sdk, where the name of the lease container is an parameter in the method returning the iterator with changes.

Describe alternatives you've considered
The alternative is to custom build this functionality every time I am writing a consumer.

Additional context
N/A

Author: JarroVGIT
Assignees: simorenoh
Labels:

question, Cosmos, Service Attention, Client, customer-reported

Milestone: -

@ghost ghost added the needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team label May 2, 2022
@simorenoh simorenoh added needs-author-feedback Workflow: More information is needed from author to address the issue. and removed needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team labels May 3, 2022
@simorenoh
Copy link
Member

@JarroVGIT Thank you for using our SDK and for opening this issue. This feature you mentioned is part of a larger feature outlined in the limitations that are present in the repo's README.md file, under the Change Feed Processor bullet points. As of today, only the .NET and Java SDKs have these capabilities.

We also do not have a timeline for when this work will happen for this SDK unfortunately. Do let me know if this answers your question.

@ghost ghost added the no-recent-activity There has been no recent activity on this issue. label May 11, 2022
@ghost
Copy link

ghost commented May 11, 2022

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!

@JarroVGIT
Copy link
Author

@simorenoh Thanks for your reply and sorry to hear this feature will be exclusive to the .NET and Java SDK's for the time being. I will close this feature request :) Keep up the great work!

@ghost ghost removed the no-recent-activity There has been no recent activity on this issue. label May 11, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Apr 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Client This issue points to a problem in the data-plane of the library. Cosmos 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. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

5 participants