Thanks, This is a common ask from our customers and something we are seriously thinking about. In the meantime you can use Azure Data Factory to “delete” the cluster and you can use persistent metastore using Azure SQL and persistent store like Azure Data Lake Store or Azure Blob which will make it seem like it is “shut down”. Thanks for your feedback. Rashim Gupta (HDInsight Engineering team)
359 votesunder review · 15 comments · API Management » Developer portal · Flag idea as inappropriate… · Admin →
Thanks for the feedback!
There are multiple responses to this suggestion.
Support for SQL-like syntax for UPDATE, DELETE and INSERT INTO are not on our road map at this time.
However, the underlying functionality for an UPDATE, SET is essentially a PATCH. This functionality we are actively working on. See this User Voice item here to track for future updates. https://feedback.azure.com/forums/263030-azure-cosmos-db/suggestions/6693091-be-able-to-do-partial-updates-on-document
Thank you for your suggestion.WDixon commented
This becomes even more important under GA, where, I'm informed that
a) every collection will be billed a minimum of one hour
b) a maximum of 5 collections can be created per minute.
In the acceptance testing phase of our CI/CD process we delete and recreate a collection to ensure it's empty. This is much easier (and faster) than listing and iteratively deleting each type (document, udf, s-proc, trigger). This will soon cost us an hour for each invocation. Having the ability to Set, or better, wildcard delete will be critical.
Thanks for the feedback, keep votes coming!