You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by GitBox <gi...@apache.org> on 2022/03/30 13:50:13 UTC
[GitHub] [dolphinscheduler] huagetai opened a new issue #9292: [Improvement][service] move remote clients to dolphinscheduler-remote module
huagetai opened a new issue #9292:
URL: https://github.com/apache/dolphinscheduler/issues/9292
### 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
The remote clients AlertClientService, LogClientService, RegistryClient should be moved from the dolphinscheduler-service module to the dolphinscheduler-remote module.
They mainly depend on the remote module instead of the service model.
The package name after moving to dolphinscheduler-remote：
```java
org.apache.dolphinscheduler.remote.client.alert.AlertClientService
org.apache.dolphinscheduler.remote.client.log.RegistryClient
org.apache.dolphinscheduler.remote.client.registry.RegistryClient
```
This will involve refactoring the api、service、master、worker and etc. modules
We can copy the remote clients to the remote first, migrate gradually, and finally delete the remote clients in the service.
The purpose is to remove the worker server's dependency on the service module (that is, the database)
### Use case
- more reasonable dependencies
- prepare to remove the worker server's dependency on the service module
### Related issues
#9283
### 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)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [dolphinscheduler] github-actions[bot] commented on issue #9292: [Improvement][service] move remote clients to dolphinscheduler-remote module
Posted by GitBox <gi...@apache.org>.
github-actions[bot] commented on issue #9292:
URL: https://github.com/apache/dolphinscheduler/issues/9292#issuecomment-1083166554
Hi:
* Thank you for your feedback, we have received your issue, Please wait patiently for a reply.
* In order for us to understand your request as soon as possible, please provide detailed information、version or pictures.
* If you haven't received a reply for a long time, you can subscribe to the developer's email，Mail subscription steps reference https://dolphinscheduler.apache.org/en-us/community/development/subscribe.html ,Then write the issue URL in the email content and send question to dev@dolphinscheduler.apache.org.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [dolphinscheduler] huagetai commented on issue #9292: [Improvement][service] move remote clients to dolphinscheduler-remote module
Posted by GitBox <gi...@apache.org>.
huagetai commented on issue #9292:
URL: https://github.com/apache/dolphinscheduler/issues/9292#issuecomment-1083417402
I tried it.it is too difficult, too many dependencies are nested.
The better way is to move to dolphinscheduler-server, keep the package structure the same so that the impact is minimal.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org