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
Get the change feed for all partitions of a collection #265
Comments
Today, with the Node.js SDK, you can't monitor all partitions at once, but it is a feature we plan on adding soon. It is possible to do this via REST API but quite complex because you have to handle the shifting layout of Cosmos DB (increasing number of partitions, partition keys being shifted around, etc.). Would not recommend this approach. Today, easiest option is to use the Cosmos DB trigger in Azure Functions which does this for Node.js/Java/Python/etc. |
@christopheranderson Thanks for your answer! I'll be looking forward to this. I guess the issue can be closed in favour of #268? |
Hi, so you cant get change feed across partitions? How reliable / what grantee is there that the Cosmos DB trigger will never fail? Cosmos DB seems to really come up short when working with many partitions. |
@christopheranderson when do you expect to have this feature available? |
Probably before end of June. Currently, we point folks to try using Azure Functions if you need change feed processor functionality with JavaScript. |
Covered by Azure/azure-sdk-for-js#4808 |
@christopheranderson please could you provide a link to the documentation for this? |
In order to get the change feed for a partioned collection with
readChangeFeed
you have to specify apartionKey
.However, if the partition path is the
ID
of the document, you can only get the change feed of one document.Is there a way to get the change feed for all partitions of a collection, either with this package or with the REST API?
The text was updated successfully, but these errors were encountered: