You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the server share level, If I don't use the Ranger AuthZ Plugin, multiple users use the system user's credential, who submits the spark job, to access HDFS, rather than their owner credential. So on the HDFS side, all actions are executed as the system user, so the HDFS Ranger Plugin loses control.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello guys
At the server share level, If I don't use the Ranger AuthZ Plugin, multiple users use the system user's credential, who submits the spark job, to access HDFS, rather than their owner credential. So on the HDFS side, all actions are executed as the system user, so the HDFS Ranger Plugin loses control.
I read Kyuubi's code And found the function setting appropriate configs for each session user. 👇
https://github.com/apache/kyuubi/blob/master/externals/kyuubi-spark-sql-engine/src/main/scala/org/apache/kyuubi/engine/spark/operation/SparkOperation.scala#L130
So why Kyuubi doesn't use [session user] as [proxy user] to execute statements at the server share level like this: 👇
Are there some lurking issues or concerns at the system level?
Looking forward to your opinions very much!
Beta Was this translation helpful? Give feedback.
All reactions