[Improvement] Make all uniifle class under org.apache.uniffle package to avoid conflict
- Dominant language
- Java
- Stars
- 454
- Forks
- 172
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 5
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-uniffle/issues?q=is%3Aissue) and found no similar issues.
### What would you like to be improved?
Make all uniifle class under org.apache.uniffle package to avoid conflict.
Something like spark mr tez client sdk.
### How should we improve?
Make all uniifle class under org.apache.uniffle package to avoid conflict.
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
Contributor guide
Research direction
No files, tests, or entry points are named. Start by inventorying Java classes and package declarations across the repository, then clarify whether the Spark, MapReduce, Tez, and client SDK areas are in scope. Done means the agreed Uniffle classes use the org.apache.uniffle package without conflicts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, distributed-systems
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100