Skip to content

ChangeFeedProcessor support request #176

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

Open
david-cag opened this issue Feb 27, 2025 · 4 comments
Open

ChangeFeedProcessor support request #176

david-cag opened this issue Feb 27, 2025 · 4 comments

Comments

@david-cag
Copy link

david-cag commented Feb 27, 2025

Is your feature request related to a problem? Please describe.
We currently uses change feed features in CosmosDB cloud service and we wanted to validate our tests againts a local cosmosdb instance but @TheovanKraay answered us in this ticket that is not currently supported:
Azure/azure-sdk-for-java#44393 (comment)

Describe the solution you'd like
Same behaviour as Azure CosmosDB cloud instance. Transparent management of continuationTokens.

Describe alternatives you've considered
We have holded docker instance usage for testing pourposes due this feature block us our business flow scenarios but with the proper guidance we are open to look for a way to mitigate continuation token errors (although change events will continue to be ignored).

Setup (please complete the following information):

  • OS: Windows 11
  • IDE: IntelliJ
  • Library/Libraries: [ com.azure:azure-spring-data-cosmos:5.20.0
  • Java version: [21.0.4]
  • Frameworks: [SpringBoot 3.3.9]
  • Image: CosmosDB Emulator (vnext-preview)
@UKR555
Copy link

UKR555 commented Feb 27, 2025

Currently, the Cosmos DB Emulator does not support the change feed feature, as confirmed in
Azure/azure-sdk-for-java#44393.

To resolve this, the recommended approach is to use an Azure Cosmos DB instance in a test environment, as it fully supports the change feed functionality, including continuation tokens.

If using the cloud instance is not feasible, an alternative is to manually handle continuation tokens and implement a polling mechanism for detecting changes. However, this may not fully replicate the behavior of the change feed in the cloud.

Would appreciate any updates on future support for this in the emulator.

@MattHartz
Copy link

@UKR555 The point of this post is to request support. I think @david-cag is well aware it's not supported. Is there any roadmap to add this support?

@trulsmp
Copy link

trulsmp commented Apr 4, 2025

@MattHartz @david-cag There is a separate issue #152 on change feed support, is that the same request as this?
There are details on timeline in that issue. Will be interesting to see if covers all consumption types of the change feed or only specific use cases.

@david-cag
Copy link
Author

Hi!
It's close related to that ticket. We both require ChangeFeedSupport but as I described in the alternatives we could mitigate our problems (discarding change feed functionality) if we find a way to mitigate continuation token errors (although change events will continue to be ignored).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants