[ https://issues.apache.org/jira/browse/HADOOP-14802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16141828#comment-16141828 ]
Steve Loughran commented on HADOOP-14802: ----------------------------------------- # add the property {{fs.azure.saskey.usecontainersaskeyforallaccess}} declaration to core-default.xml too, so that the autogenerated config docs list it there. # Is there any reason why you woudn't want to use the shared generator? As if it is faster and there are no reasons not to use it: why not make it the default always? That way: no config, no docs. If its not the case, and there are some reasons when you wouldn't, that should be listed in the index.md file # I've tried hard to see if I can think of a way to test that the shared instance is being used, but it's too deep inside the objects to get at. > Add support for using container saskeys for all accesses > -------------------------------------------------------- > > Key: HADOOP-14802 > URL: https://issues.apache.org/jira/browse/HADOOP-14802 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/azure > Reporter: Sivaguru Sankaridurg > Assignee: Sivaguru Sankaridurg > Labels: azure, fs, secure, wasb > Attachments: HADOOP-14802.001.patch, HADOOP-14802.002.patch > > > This JIRA tracks adding support for using container saskey for all storage > access. > Instead of using saskeys that are specific to each blob, it is possible to > re-use the container saskey for all blob accesses. > This provides a performance improvement over using blob-specific saskeys -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org