[DSIP-][SDK] Java SDK

[Dyqer]

Search before asking

• [X] I had searched in the DSIP and found no similar DSIP.

Motivation

I think we need to create a new module, perhaps called dolphinscheduler-spec, and move all the POJO objects from the task-api, registry-api, datasource-api, and dolphinscheduler-api modules into this new module. This way, we can easily create a Java SDK for external use.

Design Detail

dolphinsheduler-spec +- dolphinsheduler-task-api +- dolphinsheduler-registry-api +- dolphinsheduler-datasource-api +- dolphinsheduler-scheduler-api

Compatibility, Deprecation, and Migration Plan

No response

Test Plan

No response

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[SbloodyS]

I think we need to create a new module, perhaps called dolphinscheduler-spec, and move all the POJO objects from the task-api, registry-api, datasource-api, and dolphinscheduler-api modules into this new module. This way, we can easily create a Java SDK for external use.

dolphinsheduler-spec +- dolphinsheduler-task-api +- dolphinsheduler-registry-api +- dolphinsheduler-datasource-api +- dolphinsheduler-scheduler-api

I don't see how this is related to JAVA SDK. Please describe clearly what you want firstly. Then the design scheme.

[davidzollo]

I also can't find out the relationship between jdk and pojo

[Dyqer]

@SbloodyS Sb @davidzollo da For the SDK, we need to share base classes with SDK users, such as ProcessDefinition, DEPENDENT task, K8s task, and Schedule. If we can move these classes to a common API module, this module can then be reused by both the SDK module and the Master/Worker modules.

Of course, we can create some DTO classes, but we also need to plan for creating DTOs for future classes.

[liunaijie]

I think what you want to say is: move project's POJO class to a splited module, then the system out of DS can import this module and use those POJO, am I right? Maybe you can update the title then we can understand more easily.