apache / apache/dolphinscheduler
[Improvement][Dao] Further encapsulation of BaseDao avoids writing many conditional queries
- Dominant language
- Java
- Stars
- 14.5k
- Forks
- 5.1k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 29
Description
### Search before asking
- [x] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
Avoid provide many query method in dao/mapper e.g. `queryByName`, `queryByNameAndStatus`
### Are you willing to submit a PR?
- [x] Yes I am willing to submit a PR!
### Code of Conduct
- [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
Contributor guide
Research direction
Start by reading BaseDao and the existing dao/mapper query methods, especially patterns such as queryByName and queryByNameAndStatus. Compare how these methods are used across the project and identify the intended common abstraction. Done should mean the repeated conditional query methods are consistently encapsulated without changing their behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, database
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100