This is Planned but low priority at this time.
Thank you for your suggestion.
Seems like there's some internal limit being hit at around 42 characters long - I can't seems to create unique indices with combines path ('field1_field2_...') larger than that.
The thing is - this fails even if I provide a valid custom name via the name mongo option.
Is there any ETA on fixing this ?
Azure Cosmos DB is a multi-model database service, and therefore supports accessing the same underlying data using any/all APIs. We are however implementing some platform-level changes to make data access from different APIs seamless like supporting conversions between disparate type systems, and capabilities.
Hm - this doesn't seem to work anymore since the new mongo 3.6 wire protocol; I'm now getting 'Sql api is not supported for this database account', and have no ability to turn it on via az cli / powershell.
Is there any workaround ?
Just a quick update. Work on this feature continues but is taking longer than expected.
We have recently published guidance how how users who can run Windows in a VM whether on Parallels or Virtual Box with a Mac or Linux host can use the Cosmos emulator. Please feel free to use this as a workaround.
When this feature is complete we will update here.
+1 on this - is this on the road map for 2020 by any chance ?
307 votesstarted · 36 comments · Azure Key Vault » Managing application secrets · Flag idea as inappropriate… · Admin →
+1 - This must to be introduced
We’ve started the Auto-Purge work, with this current design: https://github.com/AzureCR/specs/tree/master/auto-purge
Please provide feedback here: https://github.com/AzureCR/specs/issues/1