mrtisttt commented on PR #5653:
URL: https://github.com/apache/kyuubi/pull/5653#issuecomment-1805031973

   > @mrtisttt thanks for making this PR, for consistent perspective, I think 
we should name it with `kyuubi.session.proxy.user`
   > 
   > currently, Kyuubi uses
   > 
   >     * `kyuubi.session.real.user` to represent the user who provides the 
credential for authentication
   > 
   >     * `hive.server2.proxy.user` to represent who the real user wants to 
impersonate
   > 
   >     * `kyuubi.session.user` to represent the final user for authorization
   > 
   > 
   > For the API side, I think we should shorten the name to `proxyUser`, but 
allow using `kyuubi.session.proxy.user` in `conf: Map<String, String>`
   > 
   > Just something like `spark-submit`
   > 
   > ```
   > spark-submit --driver-memory=2g
   > spark-submit --conf spark.driver.memory=2g
   > ```
   
   @pan3793 Thank you so much Pan, I get it. In this PR, I just completed:
   
   - **1.Use `kyuubi.proxy.user` to be compatible with the behavior of 
`hive.server2.proxy.user` in RESTful API;**
   
   - **2.Added `kyuubi.proxy.user` entry in beeline, although it has not been 
implemented yet;**
   
   Wait a minute, I will submit a new commit in this PR to change 
`kyuubi.proxy.user` to `kyuubi.session.proxy.user`, and also modify some 
descriptions of the document.
   
   As a subtask that fully implements the functionality of 
`kyuubi.session.proxy.user`, then I plan to complete the functions you 
mentioned in subsequent PRs, including but not limited to:
   
   - **1.Completely implement the functionality of `kyuubi.session.proxy.user` 
in beeline;**
   
   - **2.Allow using `kyuubi.session.proxy.user` to submit tasks in 
spark-submit;**
   
   According to my current understanding, in order to perfectly support 
`kyuubi.session.proxy.user` in Kyuubi, there will be more work to be completed 
in the future, and I will continue to improve this function.
   Hi, Pan, do you think this plan is okay?


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


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

Reply via email to