Re: [I] [Improvement][API] The EnvironmentWorkerGroupRelation cannot use when workergroup name change [dolphinscheduler]

["ruanwenjun (via GitHub)" <gi...@apache.org>]

ruanwenjun commented on issue #17890:
URL: https://github.com/apache/dolphinscheduler/issues/17890#issuecomment-3830349680

   In DolphinScheduler, there are two types of worker groups: one defined through the UI, and the other defined in worker configurations and registered dynamically at runtime.
   
   The current issue is that worker groups registered dynamically by workers do not have an ID and lack associated metadata. As a result, we can only rely on the worker group name for identification and association.
   
   For scenarios that require dynamic worker registration, we can still require worker groups to be created in advance through the UI. When a worker starts, it will then automatically register itself to the specified worker group. This approach ensures that all worker groups have consistent metadata while still supporting dynamic worker registration.


-- 
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