Work for this feature is now being planned. Will update when work on this feature starts and when it becomes generally available.
The ability to rename databases and collections is not currently something that is in our road map.
Currently the way to accomplish this task in Cosmos DB is to create a new collection with the changed name then use bulk exec or change feed to populate it.
Thanks for your request and input on this. We may consider this for a future planning cycle.
Thank you for your suggestion.
We will add this to our backlog for our upcoming dev cycle.
I would also suggest you add this to our Issues list for .NET SDK v3. https://github.com/azure/azure-cosmos-dotnet-v3/issues. This may get additional visibility and attention for this feature.
Either way this suggestion will be reviewed by us.
Update on this item.
Bytecode implementation is now targeting the first half of 2020 to provide stability and performance improvements in the platform.
Apologies for the delay. We are continuing to work on this. Will announce here when this becomes available.
Sorry for the lack of constructive content but I just couldn't resist.
Can't wait for christmas this year! :-)
For applications that require cross document join, please consider the Gremlin API: https://docs.microsoft.com/en-us/azure/cosmos-db/create-graph-dotnet, which has primitives for joins, traversals, and other graph operations.
We are evaluating expanding the SQL grammar to support graph functionality, which will provide the ability to perform cross-document JOINs. Please upvote this item to help us prioritize this work.
This is an interesting idea, but not in our current scope. What is your use case? As you mention, queues may fulfil this use case quite well currently.
One case is to use event grid as a timer. We do workflows using Azure servicebus and our timeouts and even some retries go via BrokeredMessage.ScheduledEnqueueTimeUtc.
We have reviewed this and have elected to not include this on our road map for the time being. We may revisit this in the future so will leave as unplanned rather than declined or closed.
Thanks for your suggestion and comments.
Work on this feature has started. Will update here when this becomes generally available.
Thank you for your suggestion and votes.
So, any chance of getting back to us?
What is the status?
Thank you for your feedback. We are currently in public preview of static website hosting for Azure Storage to enable this scenario. Check out the blog post here for more details: https://azure.microsoft.com/en-us/blog/azure-storage-static-web-hosting-public-preview. The feature set includes support for default documents and custom error documents for HTTP status code 404.
For any further questions, or to discuss your specific scenario, send us an email at email@example.com.
Reopening this user voice item as our support for Skip/Take (Offset/Limit) was only limited to single partition queries.
The newly released .NET SDK v3 now includes support for x-partition queries using Offset/Limit. You can learn more about v3 SDK and try it and provide feedback on our github repo here.
We will also be back-porting this functionality to our .NET v2 SDK. This work will begin shortly and we anticipate it to be released in September.
Once that is released we will mark this feature as complete.
Thank you for your patience and votes.
So, how far is this?
The link by Henrik Ebbeskog shows how to iterate, but not how to page. (Paging is when the user can go to the previous or next page in a view.)
Furthermore, for a collection to use min/max requires some unique sortable property, which many collections don't have.
(Many have either unique or sortable, but not both.)
893 votesunplanned · AdminSQL Database feature voting forum admins (Product Owner, Microsoft Azure) responded
This is not currently planned at this time. Will keep this item open for voting and comments.
Put my vote on the list for that too.
In Azure, filestream doesn't make sense, but a BLOB data type using BLOB storage would be great.