pan3793 opened a new issue, #5378:
URL: https://github.com/apache/kyuubi/issues/5378

   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   
   
   ### Search before creating
   
   - [X] I have searched in the [task 
list](https://github.com/orgs/apache/projects/296) and found no similar tasks.
   
   
   ### Mentor
   
   - [X] I have sufficient knowledge and experience of this task, and I 
volunteer to be the mentor of this task to guide contributors to complete the 
task.
   
   
   ### Skill requirements
   
   - Basic knowledge on Scala Programing Language
   - High Level knowledge of Kyuubi architecture
   - Familiar with Kyuubi and each engine's configuration
   
   
   ### Background and Goals
   
   Kyuubi is mainly composed of two components: Server and Engine. Some 
configurations take effect on both Server and Engine, but some only take effect 
on Server or specific Engine.
   
   The Server picks up configurations from `kyuubi-defaults.conf` and passes 
them to the command line during the launching engine process, including some 
sensitive data. To overcome it, we introduce a `serverOnly` flag on each 
configuration's definition.
   
   
   ### Implementation steps
   
   Replace the `serverOnly` flag with `requiredByEngines(...)` and 
`requiredByAllEngines`, so that we can only pass the required configurations to 
each engine.
   
   Note: we should always bypass the unknown properties to the engine in case 
some user custom properties do not take effect.
   
   ### Additional context
   
   _No response_


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