[Improvement] Move jdbc engine common interface to individual module
- 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/incubator-kyuubi/issues?q=is%3Aissue) and found no similar issues.
### What would you like to be improved?
There are a few interface that need extended by engine, if they located in jdbc engine module. User need modify kyuubi code, if there is a common module, a new engine can be supported freely because the implement is loaded by SPI.
### How should we improve?
_No response_
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
Contributor guide
Research direction
Start by inspecting the JDBC engine module and the interfaces that engines currently extend, then trace how implementations are loaded through SPI. Clarify which interfaces belong in a common module and verify that a new engine can implement them without modifying Kyuubi; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- backend, databases
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100