[
https://issues.apache.org/jira/browse/HADOOP-14518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16061064#comment-16061064
]
Steve Loughran commented on HADOOP-14518:
-----------------------------------------
Looking at s3a, the property for setting the prefix is
"fs.s3a.user.agent.prefix". Could you do something similar with
{{fs.azure.user.agent.prefix}}. It's good not just for users to have consistent
attribute names, but for anyone fielding support calls trying to work out why
the setting isn't being picked up. Now is the time to get it right.
> Customize User-Agent header sent in HTTP/HTTPS requests by WASB.
> ----------------------------------------------------------------
>
> Key: HADOOP-14518
> URL: https://issues.apache.org/jira/browse/HADOOP-14518
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/azure
> Affects Versions: 3.0.0-alpha3
> Reporter: Georgi Chalakov
> Assignee: Georgi Chalakov
> Priority: Minor
> Attachments: HADOOP-14518-01.patch, HADOOP-14518-01-test.txt,
> HADOOP-14518-02.patch, HADOOP-14518-03.patch, HADOOP-14518-04.patch
>
>
> WASB passes a User-Agent header to the Azure back-end. Right now, it uses the
> default value set by the Azure Client SDK, so Hadoop traffic doesn't appear
> any different from general Blob traffic. If we customize the User-Agent
> header, then it will enable better troubleshooting and analysis by Azure
> service.
> The following configuration
> <property>
> <name>fs.azure.user.agent.id</name>
> <value>MSFT</value>
> </property>
> set the user agent to
> User-Agent: WASB/3.0.0-alpha4-SNAPSHOT (MSFT) Azure-Storage/4.2.0
> (JavaJRE 1.8.0_131; WindowsServer2012R2 6.3)
> Test Results :
> Tests run: 703, Failures: 0, Errors: 0, Skipped: 119
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
