[
https://issues.apache.org/jira/browse/HDFS-16901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17685427#comment-17685427
]
ASF GitHub Bot commented on HDFS-16901:
---------------------------------------
omalley commented on code in PR #5346:
URL: https://github.com/apache/hadoop/pull/5346#discussion_r1099074190
##########
hadoop-hdfs-project/hadoop-hdfs-rbf/src/main/java/org/apache/hadoop/hdfs/server/federation/router/RouterRpcClient.java:
##########
@@ -492,6 +492,7 @@ public Object invokeMethod(
}
addClientInfoToCallerContext();
+ addRealUserToCallerContext(ugi);
Review Comment:
Let's add the user information in addClientInfoToCallerContext so that we
only have to rebuild the caller context once.
> RBF: Routers should propagate the real user in the UGI via the caller context
> -----------------------------------------------------------------------------
>
> Key: HDFS-16901
> URL: https://issues.apache.org/jira/browse/HDFS-16901
> Project: Hadoop HDFS
> Issue Type: Task
> Reporter: Simbarashe Dzinamarira
> Assignee: Simbarashe Dzinamarira
> Priority: Major
> Labels: pull-request-available
>
> If the router receives an operation from a proxyUser, it drops the realUser
> in the UGI and makes the routerUser the realUser for the operation that goes
> to the namenode.
> In the namenode UGI logs, we'd like the ability to know the original realUser.
> The router should propagate the realUser from the client call as part of the
> callerContext.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
