[GitHub] [dolphinscheduler] github-actions[bot] commented on issue #5790: [Improvement][UI experience] Some suggestions for UI experience

[GitBox <gi...@apache.org>]

github-actions[bot] commented on issue #5790:
URL: https://github.com/apache/dolphinscheduler/issues/5790#issuecomment-877588894


   **Describe the question**
   A clear and concise description of what the improvement is.
   
   **What are the current deficiencies and the benefits of improvement**
   -[Current Node Settings] field "Run ID" is changed to "Node Status", and the option value is changed to ["Enable", "Disable"], which is more intuitive.
   -[Current Node Settings] field "Failure Retry Times", "Failure Retry Interval", "Timeout Alarm", "Alarm Strategy", "Timeout Duration" and extract it to [Current Node Settings] to create a new TAB page to place, name Can be "execution strategy" (similar to the write and preview effects of filling in the issue). Taking timeout as an example, you can place a drop-down box on the execution strategy page, add a timeout strategy, and display the current related options as a GROUP. This can separate the node definition from the execution strategy and make it clearer. No policy is attached by default. At the same time, in addition to timeout, you can also define a notification strategy for execution success/failure (different notification methods can be defined in this strategy). In my actual use process, sometimes it is necessary to notify in real time when TASK fails or succeeds, instead of notifying until DAG level or overtime.
   -[System Variables] Add DAG-related system variables, such as dag name, currently executing task name, worker node IP, execution time, error message and other general ones. It can be very accurate when receiving system notifications for problem location.
   -[Resource Management] It is recommended to make the file management and UDF management pages into a tree structure, and the tree nodes can add/delete/move folders. Support batch upload of files. It's too painful to only upload a single file now.
   
   中文在这：
   - [当前节点设置] 字段“运行标识”改为“节点状态”，选项值变更为[“启用”，“禁用”]，更直观。
   - [当前节点设置] 字段“失败重试次数”，“失败重试间隔”，“超时告警”，“告警策略”，“超时时长”提取到[当前节点设置]新建一个TAB页去放置，名称可为“执行策略”（类似于填写issue的write与preview效果）。以超时举例，可在执行策略页面放置一个下拉框，添加超时策略，将当前相关选项做为一个GROUP进行展示。这样可以把节点定义与执行策略分离，更加清晰。默认情况下不附加任何策略。 同时除了超时，还可以定义执行成功/失败的通知策略（此策略中就可定义不同的通知方式）。我在实际使用过程中，有时候是需要在TASK失败或成功时实时通知，而不是到DAG级别或超时才通知。 
   - [系统变量] 增加DAG相关的系统变量，例如 dag名称,当前执行的task名称,worker节点IP，执行时间，出错信息  等这些通用的。在接收到系统通知进行问题定位时可以非常精准。
   - [资源管理] 建议将文件管理与UDF管理页面做成树状结构，树节点可增加/删除/移动 文件夹。 支持文件批量上传。 现在只能上传单个文件太痛苦了。
   
   
   **Which version of DolphinScheduler:**
    -[1.3.6-Realese]
   
   **Describe alternatives you've considered**
   A clear and concise description of any alternative improvement solutions you've considered.


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