azure-docs
azure-docs copied to clipboard
Invalid capability EnableUniqueCompoundNestedDocs
This page has been recently updated adding this capability as available. However, following the provided steps I was unable to make work.
az cosmosdb update --resource-group test-mongo-database --name test-mongo-db0003 --capabilities @("EnableMongo", "EnableUniqueCompoundNestedDocs")
(BadRequest) Invalid capability EnableUniqueCompoundNestedDocs.
ActivityId: 87324f08-61de-11ed-83fe-f875a4ad18aa, Microsoft.Azure.Documents.Common/2.14.0
Code: BadRequest
Message: Invalid capability EnableUniqueCompoundNestedDocs.
ActivityId: 87324f08-61de-11ed-83fe-f875a4ad18aa, Microsoft.Azure.Documents.Common/2.14.0
I got similar output when a tried with create
instead of update
(az CLI version 2.42.0)
So, I don't know if there are missing steps/details to this specific capability, or if it is a bug in the product or is not yet available. In any case, this needs to be reviewed and addressed.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
- ID: 839bea7b-b0b0-792c-0e0c-d3ee260a9e31
- Version Independent ID: 44cfd449-186f-4759-4768-27a044a18f29
- Content: Configure your Azure Cosmos DB for MongoDB account capabilities
- Content Source: articles/cosmos-db/mongodb/how-to-configure-capabilities.md
- Service: cosmos-db
- Sub-service: mongodb
- GitHub Login: @seesharprun
- Microsoft Alias: sidandrews
@CorrenSoft Thank you for your feedback. We are reviewing this and will get shortly.
@CorrenSoft Are you trying to add this capability EnableUniqueCompoundNestedDocs? I am trying to test that from my end and will let you know.
@CorrenSoft, I am getting exacctly the same error message as you .
@gahl-levy any inputs on this. Is this a product bug.?
@CorrenSoft This is confirmed as a bug. The capability is available, but the ability to use it externally is blocked by a deployment, which is blocked by the holidays. Could you please file a support ticket to get this enabled for your account right away. The product group will revert the docs change until the capability is available. Apologies for this issue and thank you for bringing this into our attention.
Thanks for the update and the recommendation. I will skip that step thou because wasn't trying to implement this for myself but in Terraform's provider (https://github.com/hashicorp/terraform-provider-azurerm/issues/19192).
A notification when this is ready will be great :)
Thanks again.
Sure @CorrenSoft Our produc group will update the doc when this capability will be available.