[ 
https://issues.apache.org/jira/browse/HADOOP-19365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17905453#comment-17905453
 ] 

Ahmar Suhail commented on HADOOP-19365:
---------------------------------------

Current flow of how this works (I think) is 

 

when creating the RequestFactory in S3AFileSystem, we do 
 
RequestFactoryImpl.builder().withRequestPreparer(getAuditManager()::requestCreated),
 
then when requests are created, we do prepareRequest(builder), see 
RequestFactoryImpl.newGetObjectRequestBuilder(). This attaches the span to a 
request. 
 
And then executionInterceptors before submitting the request, will extract the 
referrer, using 
[https://sdk.amazonaws.com/java/api/latest/software/amazon/awssdk/core/interceptor/ExecutionInterceptor.html#modifyHttpRequest(software.amazon.awssdk.core.interceptor.Context.ModifyHttpRequest,software.amazon.awssdk.core.interceptor.ExecutionAttributes)]

> Add audit header support 
> -------------------------
>
>                 Key: HADOOP-19365
>                 URL: https://issues.apache.org/jira/browse/HADOOP-19365
>             Project: Hadoop Common
>          Issue Type: Sub-task
>            Reporter: Ahmar Suhail
>            Priority: Major
>
> S3A adds audit information as referrer headers, see 
> [https://github.com/apache/hadoop/blob/trunk/hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/auditing.md]
>  for documentation on this. 
> These are attached using execution interceptors, see ActiveAuditManagerS3A.
> createExecutionInterceptors(). 
>  
> analyitcs-accelerator-s3 makes the GET requests now but does not update the 
> referrer with GETs. 
>  
> See LoggingAuditor.attachRangeFromRequest() for how this is done. 
>  
> When using analytics-accelerator-s3, audit headers from S3A should be sent 
> through. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to