Over this weekend we released a new version of Cloud Portam. This blog post talks about the enhancements done in this release.
DocumentDB Latest SDK Support
Recently DocumentDB introduced support for “Order By” clause for your queries. In order to support this, there have been some major changes done at the service level mainly around how you define Indexing Policies. I’m pleased to announce that Cloud Portam now supports these changes.
Essentially the change is reflected in how you define the included paths for your indexing policies when creating a collection. Basically now for each indexed path, you can define both Hash and Range indexes. Previously they had to be in separate paths.
I would strongly recommend that you refer to Indexing Policies document: https://azure.microsoft.com/en-us/documentation/articles/documentdb-indexing-policies/ to learn more about it.
Apart from that, we included some business rules validations in the client side code itself so that your request doesn’t go to DocumentDB only to get failed. Some business rules we have incorporated are:
- If “Indexing Mode” is set as “None”, “Automatic Indexing” can’t be set to “Yes”.
- If “Indexing Mode” is set as “None”, application will not allow you to define included and excluded paths (basically the buttons will be disabled).
As you may already know that if you access Cloud Portam via Google Chrome or Opera browser, you can upload folders in your blob storage and Cloud Portam will preserve the folder hierarchy in your blob container by prefixing the blobs with proper folder path. This is working great however we discovered an issue when you try to upload folders in “$root” blob container. Cloud Portam was still trying to maintain the folder hierarchy however the blob upload would fail because “$root” container does not support the concept of blob prefixes.
In this release, we have fixed the code so that when you are uploading folders in “$root” blob container, folder hierarchy is not preserved and only files from all folders and sub-folders are uploaded to the container without any prefixes.
For example, consider is folder structure:
and these are the files in this folder:
and this is how the upload queue looks like in Cloud Portam:
However when they are uploaded, this is how they are saved in “$root” container:
However if the same set of files are uploaded in another blob container, this is how they are saved in that blob container:
Try It Out!
We humbly request you to try out these updates in Cloud Portam. This is available in both “Personal” and “Team” editions of Cloud Portam. Though extreme care has been taken regarding testing the current functionality, it is quite possible that we may have overlooked something. If you find something missing or implemented incorrectly, please feel free to reach out to us and tell us. We will fix the issues ASAP.
As you can see we’re constantly investing in making the product more and more useful. Do try out Cloud Portam and these features and let us know what you think. If you think, we can improve it in any way, please feel free to share your thoughts. The link to our website is http://www.cloudportam.com.