[
https://issues.apache.org/jira/browse/HADOOP-13122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15281506#comment-15281506
]
Hudson commented on HADOOP-13122:
---------------------------------
FAILURE: Integrated in Hadoop-trunk-Commit #9751 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/9751/])
HADOOP-13122 Customize User-Agent header sent in HTTP requests by S3A. (stevel:
rev def2a6d3856452d5c804f04e5bf485541a3bc53a)
*
hadoop-tools/hadoop-aws/src/test/java/org/apache/hadoop/fs/s3a/TestS3AConfiguration.java
*
hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/S3AFileSystem.java
* hadoop-common-project/hadoop-common/src/main/resources/core-default.xml
* hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/index.md
* hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/Constants.java
> Customize User-Agent header sent in HTTP requests by S3A.
> ---------------------------------------------------------
>
> Key: HADOOP-13122
> URL: https://issues.apache.org/jira/browse/HADOOP-13122
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Fix For: 2.8.0
>
> Attachments: HADOOP-13122.001.patch
>
>
> S3A passes a User-Agent header to the S3 back-end. Right now, it uses the
> default value set by the AWS SDK, so Hadoop HTTP traffic doesn't appear any
> different from general AWS SDK traffic. If we customize the User-Agent
> header, then it will enable better troubleshooting and analysis by AWS or
> alternative providers of S3-like services.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
