-1
I am using ambari integration to manage dolphin.
The removal of each function should take into account its existing group
interests.
Once removed, it means that those of us who are using the function cannot enjoy
the benefits of the new version and need to spend a lot of effort to migrate
some components.
Plugins can not be maintained, and the use risk prompt of related old plug-ins
can be added in the new version, but components cannot be removed blindly.
--
At 2021-11-19 14:44:57, "Jiajie Zhong" <[email protected]> wrote:
>Hey guys,
>
>I am here to proposal we DolphinScheduler remove Apache Ambari plugin in
>our main repo.
>
>I think we should keep our main repo as pure as possible, and Ambari plugin
>is not our major features.
>
>For now Ambari plugin in our main repo, we have to verify the availability
>when we create a new release.
>And some users would create an issue about the plugin. All this things I
>think is not the responsibilities of
>DolphinScheduler, it more looks like the responsibilities of
>DolphinScheduler, and should not blame
>DolphinScheduler core itself.
>
>Maybe it is time to make it clear whose responsibility it is.
>
>If this proposal passes, we should:
>1. Create an issue and PR to remove code in `ambari_plugin` and other
>related in main repo
>2. Remove related document in dev and 2.0
>
>Best Wish
>— Jiajie
