Imre Pühvel

My feedback

  1. 15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Azure Cosmos DB » SQL API  ·  Flag idea as inappropriate…  ·  Admin →
    Imre Pühvel shared this idea  · 
  2. 72 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Azure Migrate  ·  Flag idea as inappropriate…  ·  Admin →
  3. 135 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    9 comments  ·  Azure Migrate  ·  Flag idea as inappropriate…  ·  Admin →
    Imre Pühvel supported this idea  · 
  4. 23 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  (General Feedback) » azure.microsoft.com  ·  Flag idea as inappropriate…  ·  Admin →
    Imre Pühvel commented  · 

    This is a common scenario. Recreating the lock from scratch is cumbersome + there's chance it is forgotten. Disabled locks would raise questions. Missing locks are harder to spot.

    Imre Pühvel supported this idea  · 
  5. 15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Azure Cosmos DB » Portal  ·  Flag idea as inappropriate…  ·  Admin →
    Imre Pühvel commented  · 

    Partition key and unique constraints can be added only during collection creation. For existing collections it is cumbersome to view/verify how a collection has been set up regarding keys.

    It would make sense if these read-only properties would be made available via Azure portal, for example in collection "scale and settings" view. The information is already present in JSON loaded to browser, so it is just the matter of GUI/UX.

    Imre Pühvel supported this idea  · 
  6. 396 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Azure Cosmos DB » Management  ·  Flag idea as inappropriate…  ·  Admin →
    Imre Pühvel supported this idea  · 
  7. 12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Storage » Blobs  ·  Flag idea as inappropriate…  ·  Admin →
    Imre Pühvel supported this idea  · 
  8. 237 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  Storage » General  ·  Flag idea as inappropriate…  ·  Admin →
    Imre Pühvel supported this idea  · 
  9. 1,070 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    26 comments  ·  Storage » General  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for your feedback. We view this ask as a set of related features.

    Soft delete for blobs enables you to save and recover your data where blobs or blob snapshots are deleted. It does not protect against container or account deletion. This feature is currently generally available. You can see the announcement here: https://azure.microsoft.com/en-us/blog/soft-delete-for-azure-storage-blobs-ga/ and the full documentation here: https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blob-soft-delete

    Object versioning will also offer object-level protection, and will offer a few incremental improvements to soft delete. Specifically, it will make recovery of deleted data easier. This feature is planned for the coming year.

    Container soft delete will protect against container-level deletion and modification. This feature is planned for the coming year as well.

    Native support for blob backup will protect against account-level deletion and modification, and is currently on our backlog.

    We will provide updates when they become available. For any further questions, or to discuss your…

    Imre Pühvel supported this idea  · 
  10. 4,613 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    142 comments  ·  Storage » Blobs  ·  Flag idea as inappropriate…  ·  Admin →

    You can now use the Azure CDN to access blobs with custom domains over HTTPS. See the following article for instructions on how to do so: https://docs.microsoft.com/en-us/azure/storage/storage-https-custom-domain-cdn. Having talked to a number of customers, we concluded that this solution addresses many scenarios where the need for HTTPS access to blobs with custom domains exists.

    Native Azure Storage support for using SSL to access blobs at custom domains is still on our backlog. We would love to hear about your scenarios where using the Azure CDN is not an acceptable solution, either by posting on this thread or sending us an email at azurestoragefeedback@microsoft.com.

    Imre Pühvel supported this idea  · 
  11. 3,840 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    80 comments  ·  Azure Cosmos DB » SQL API  ·  Flag idea as inappropriate…  ·  Admin →
    Imre Pühvel commented  · 

    This would be useful **as long as it does NOT hurt where cosmosDB shines - scaling** and working on documents level. CosmosDB is not supposed to be notepad nor SQL and it can never be optimal for all scenarios. CosmosDB team, I trust you here to not encourage people to skip data design step too much ;)

    Still, it would be useful as a bandwidth saving calling code simplification feature, I imagine it would be relatively simple to implement API which internally would use existing model (SP or other serverside logic block could read document, modify by adding provided part, save with etag check).

  12. 2,728 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    74 comments  ·  Azure Cosmos DB » SQL API  ·  Flag idea as inappropriate…  ·  Admin →
    Imre Pühvel supported this idea  · 
  13. 392 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Azure Cosmos DB » Management  ·  Flag idea as inappropriate…  ·  Admin →

    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.

    thanks.

    Imre Pühvel supported this idea  · 

Feedback and Knowledge Base