[HADOOP-18691] Add a CallerContext getter on the Schedulable interface

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.4.0, 3.3.6
• Fix Version/s: 3.4.0, 3.3.6
• Component/s: common
• Labels: pull-request-available
• Target Version/s: 3.4.0, 3.3.6
• Hadoop Flags: Reviewed
• Assignee: Christos Bisias
• Reporter: Christos Bisias
• Created: 06/Apr/23 17:41
• Updated: 27/Jan/24 08:26
• Resolved: 20/Apr/23 17:12

Description

We would like to add a default CallerContext getter on the Schedulable interface

default public CallerContext getCallerContext() {
  return null;  
} 

and then override it on the ipc/Server.Call class

@Override
public CallerContext getCallerContext() {  
  return this.callerContext;
} 

to expose the already existing callerContext field.

 

This change will help us access the CallerContext on an Apache Ozone IdentityProvider implementation.

On Ozone side the FairCallQueue doesn't work with the Ozone S3G, because all users are masked under a special S3G user and there is no impersonation. Therefore, the FCQ reads only 1 user and becomes ineffective. We can use the CallerContext field to store the current user and access it on the Ozone IdentityProvider.

 

This is a presentation with the proposed approach.

https://docs.google.com/presentation/d/1iChpCz_qf-LXiPyvotpOGiZ31yEUyxAdU4RhWMKo0c0/edit#slide=id.p

Issue Links

• blocks: HDDS-7319 To support s3g usernames with Fair Call Queue from hadoop-commons
• links to: GitHub Pull Request #5540