apache/amoro

[Improvement]: Optimize the project's module structure

Closed this issue · 0 comments

zhoujinsong commented

Search before asking

  • I have searched in the issues and found no similar issues.

What would you like to be improved?

The current module structure of the project does not effectively reflect the hierarchical relationship between modules, often leading to incorrect guidance for developers who are new to the code.

We need to optimize the existing module structure to make it more logical and assist developers in understanding the roles of different modules correctly.

How should we improve?

The module adjustment this time does not involve introducing new modules or moving classes to other modules. It will only involve reorganizing the existing modules to truly reflect their hierarchical structure.

The new module structure will be:

- core
- ams
  - api
  - server
  - dashboard
  - optimizer
    - common
    - flink-optimizer
    - standalone-optimizer
  - dist 
- mixed
  - flink
    - flink-common
    - flink-common-format
    - flink-common-iceberg-bridge
    - v1.15/flink
    - v1.15/flink-runtime
    - v1.16/flink
    - v1.16/flink-runtime
    - v1.17/flink
    - v1.17/flink-runtime
  - spark
    - common
    - v3.1/spark
    - v3.1/spark-runtime
    - v3.2/spark
    - v3.2/spark-runtime
    - v3.3/spark
    - v3.3/spark-runtime
  - hive
  - trino

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Subtasks

No response

Code of Conduct