Support attaching to a read-only storage account
It is common to attach two storage accounts to an HDInsight cluster. The secondary storage account is the source and is intended to be read-only. We create an external table on top of the source files and then insert to tables living in the default storage account which is read-write.
Please add support for HDInsight to attach to a storage account as read-only so we can 100% ensure we don't write to the source account?
I don't know if this would require blob storage adding a read-only storage account key or if this would be a flag in HDInsight or if this would be HDInsight enabling support for SAS tokens to enable read-only access (as described here http://feedback.azure.com/forums/217298-storage/suggestions/2222335-read-only-storage-keys).
HDInsight supports creating read-only clusters using SAS tokens. We are currently updating our documentation to provide sample and more details. I’ll update this thread with a link to the sample and documentation by the end of this week.
-Adnan | PM | HDInsight
As a follow up to Adnan’s comment we do have a blog post below which shows how to do this:
The config to use as provided in the link is fs.azure.sas…blob.core.windows.net in core-site.xml
Is there any progress on adding additional secondary storages to HDInsight hadoop clusters?