[
https://issues.apache.org/jira/browse/HADOOP-17511?focusedWorklogId=601253&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-601253
]
ASF GitHub Bot logged work on HADOOP-17511:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 24/May/21 16:03
Start Date: 24/May/21 16:03
Worklog Time Spent: 10m
Work Description: steveloughran commented on pull request #2807:
URL: https://github.com/apache/hadoop/pull/2807#issuecomment-847148990
Somehow the header test had failed on the principal. Changes
* how the principal is added has changed
* fixed up the referrer entry which adding a hadoop/1 prefix change of
friday was no longer a valid URI.
This wasn't just a yetus failure; I replicated it locally. How did my tests
pass? They didn't, but I hadn't noticed because the failsafe test run was
happening anyway...and the failure of the unit tests was happening in a
scrolled of test run I wasn't looking at.
That's not good: I've always expected maven to fail as soon as unit tests
do. Will investigate separately
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 601253)
Time Spent: 21h (was: 20h 50m)
> Add an Audit plugin point for S3A auditing/context
> --------------------------------------------------
>
> Key: HADOOP-17511
> URL: https://issues.apache.org/jira/browse/HADOOP-17511
> Project: Hadoop Common
> Issue Type: Sub-task
> Affects Versions: 3.3.1
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Major
> Labels: pull-request-available
> Time Spent: 21h
> Remaining Estimate: 0h
>
> Add a way for auditing tools to correlate S3 object calls with Hadoop FS API
> calls.
> Initially just to log/forward to an auditing service.
> Later: let us attach them as parameters in S3 requests, such as opentrace
> headeers or (my initial idea: http referrer header -where it will get into
> the log)
> Challenges
> * ensuring the audit span is created for every public entry point. That will
> have to include those used in s3guard tools, some defacto public APIs
> * and not re-entered for active spans. s3A code must not call back into the
> FS API points
> * Propagation across worker threads
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
