[
https://issues.apache.org/jira/browse/HADOOP-16903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17051056#comment-17051056
]
Steve Loughran commented on HADOOP-16903:
-----------------------------------------
FWIW we've been looking at whether we are getting the s3a US right and if we
should change it to embed information more in accordance with what's in the
HTTP spec.
*we can't change the current layout as existing applications which parse logs
will break*
That holds for abfs as well as s3a. All we can do is add the ability to add
extra information through more opts
> fs.azure.user.agent.prefix adds customisation as suffix.
> --------------------------------------------------------
>
> Key: HADOOP-16903
> URL: https://issues.apache.org/jira/browse/HADOOP-16903
> Project: Hadoop Common
> Issue Type: Improvement
> Components: fs/azure
> Affects Versions: 3.2.0
> Reporter: Arun Ravi M V
> Priority: Minor
>
> Setting fs.azure.user.agent.prefix adds customization as suffix
> eg: when I set `fs.azure.user.agent.prefix` to my email the user agent value
> is
> Azure Blob FS/1.0 (DBFS) (JavaJRE 1.8.0_232; Linux 4.15.0-1050-azure;
> SunJSSE-1.8) [email protected]
> I believe this is inconsistent with the similar setting in AWS S3
> fs.s3a.user.agent.prefix where the customization is added as a prefix. I
> believe that it would be great if we make this consistent with configuration
> name.
>
> The proposed change is to fix the AbfsClient.initializeUserAgent.
>
> We use a user agent information available in cloud service logs for extended
> tracking.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
