-
Notifications
You must be signed in to change notification settings - Fork 21
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
Collection name cannot be specified? #25
Comments
I see that another attribute can easily be added to CosmoStore.CosmosDb.Configuration, and used in CosmoStore.CosmosDb.EventStore. But I see in the js sproc hardcoded Events, any idea how that can be changed? |
Hi @deyanp, you are right, currently it cannot be changed, but I got an idea how to put more separate collections into one database. I'll keep it open until solved. |
Fixed in v2.1.0 |
Thanks a lot, @Dzoukr!!! |
Hi,
I am looking into creating a Cosmos DB database with shared throughput across all collections/containers. It seems the database name can be specified when setting up the configuration, but the collection/container name not? Asking because I wanted to create several XxxEvents collections, and have different Cosmos Db Triggers assigned to each one ..
The text was updated successfully, but these errors were encountered: