[FEATURE] Set different shares for different engines
- Dominant language
- Scala
- Stars
- 2.4k
- Forks
- 1k
- PR merge metrics
- No merged PRs in 30d
Description
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
### Search before asking
- [X] I have searched in the [issues](https://github.com/apache/kyuubi/issues?q=is%3Aissue) and found no similar issues.
### Describe the feature
We hope that spark can be shared at the use level, and trino can be shared at the pool level, but kyuubi has not yet provided the setting for configuring the sharing level according to the engine type
**"kyuubi.engine.share.level"** is globally effective, and session conf is only for sessions alone. It is hoped to add different sharing levels according to engine settings. For example: **"kyuubi.engine.{spark|trino|flink}.share.level"**
The priority is : session conf > kyuubi.engine.{spark|trino|flink}.share.level > kyuubi.engine.share.level
### Motivation
_No response_
### Describe the solution
_No response_
### Additional context
_No response_
### Are you willing to submit PR?
- [x] Yes. I would be willing to submit a PR with guidance from the Kyuubi community to improve.
- [ ] No. I cannot submit a PR at this time.
Contributor guide
Research direction
Start by tracing how kyuubi.engine.share.level and session configuration are read for Spark, Trino, and Flink engines. Verify how an engine-specific setting should interact with the global setting and confirm the stated precedence: session configuration, then engine-specific configuration, then the global default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala, spark
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100