[GitHub] [incubator-dolphinscheduler] wangsvip opened a new issue #1339: DS功能建议/DS Feature Suggestions

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

wangsvip opened a new issue #1339: DS功能建议/DS Feature Suggestions
URL: https://github.com/apache/incubator-dolphinscheduler/issues/1339
 
 
   目前遇到的最大的问题，是跨项目依赖，据说1.2.0会支持这个功能；
   还有很多地方最好能微调下，我有很多使用过程中的建议，如果能采纳，那这将会是一个了不起的项目；
   例如：
   1.分页查看，每页固定10条，我觉得很不合理，至少要留给用户一个可选的条数。
   2.批量上线下线的问题
   3.用户创建shell任务的界面，右边弹出的框太小了，我的shell经常会写的很长，要拖到最下面才有进度条来查看后面的内容。你至少要留给我很大空间能够让我看到我的命令，或者就放弃这种右边弹框的方式，直接正中央弹出，并且这个弹框是可以随意移动，可以伸缩大小的，这样就不要纠结shell长度的问题。
   4.创建shell任务界面的时候，所有东西都填好了，不小心在左边空白处，点了下鼠标，弹框就缩回去了，然后我填的很多东西都没有了，我很气知道么，好多次就是这样，我填了一大堆，然后就没了，我觉得应该给用户一个关闭当前弹框的按钮，而不是不小心点击了空白界面就什么都没有了。
   5.还是shell创建页面，如果我填了很多东西，突然我想放弃这次任务，我点击了chrome左上角的后退按钮，返回到了“工作流定义”界面，这个时候弹框还会存在，我觉得这是个界面BUG。
   6.设置定时任务点击“执行时间”按钮，会导致API使用内存不释放，导致闪退，只能重启服务，这个问题可能会修复。
   7.建立Dependent任务时，我的任务名字会很长，回显shell名称那里，太长的任务名字显示不了，找不到哪个是我想要的，只能输入名字精确搜索，这里应该要优化一下，至少让用户能完整的看到任务名称，或者把鼠标移上去，能显示完整的名称。
   8.我觉得建立子任务名称，不应该叫节点名称，让人很容易想成是物理机节点名称，一个Job下由多个Task组成工作流,而那里应该改为TaskName(任务名称),而不是NodeName(节点名称)。
   9.应该让管理员控制每个账户有哪些可选的work工作组，我们之前发生了一件事，就是本来在大数据平台的建表任务，阴差阳错跑到TiDB上建表了，首先能确定你是在什么平台跑数据的，然后只授权一个默认的work工作组，，如果需要连接多个地方，在授权这个账户多个work工作组。
   10.将任务下线调整任务后，每次上线都要重新选择work工作组，用户体验度不是很好；如果我上次选择过在哪个work工作组下执行任务，那这些也将会跑在上次work环境中，只有明确要更换work工作组，用户才需要重新选择，而不是每一次都要选择work工作组；至少要记住我上次的选择。
   
   ================================================================
   
   The biggest problem is cross-project dependencies, which are said to be supported in 1.2.0.
   There are a lot of things that you might want to fine-tune. I have a lot of Suggestions for how to use it.
   Such as:
   1. Pagination, fixed 10 pages per page, I think it is unreasonable, at least leave the user an optional number of pages.
   2. Batch online and offline problems
   3. When the user creates the interface of shell task, the pop-up box on the right is too small. My shell often writes very long, so I have to drag it to the bottom to have a progress bar to check the following content.You have to at least give me a lot of room to see my commands, or you have to give up the right popover and pop it right in the middle, and the popover can be moved around and scaled up, so you don't have to worry about shell length.
   Task 4. Create a shell interface, everything is filled out, accidentally in the left-hand margin, point under the mouse, bounced back, then I fill a lot of things all have no, I know, angrily this is many times, I filled out a lot of, and then you didn't, I think I should give the user a close the current play button box, rather than accidentally click on a blank screen is nothing.
   5. Shell created the page. If I filled in a lot of things and suddenly I wanted to give up the task, I clicked the back button in the top left corner of chrome and went back to the "workflow definition" interface.
   6. Set timing task click the "execution time" button, which will result in API usage memory not released, resulting in flash back, only restart the service, this problem may be fixed.
   7. Establish Dependent tasks, task name I will be very long, echo the shell name there, is too long task name display, which is what I want, can't find can only enter the name search precision, here should be optimized, at least let users can see the task name, complete or move the mouse, can display the complete name.
   8. I think creating a subtask name, instead of calling it a NodeName, is easy to think of it as a physical machine NodeName, a workflow consisting of multiple tasks under a Job, where it should be TaskName instead of NodeName.
   9. Should let the administrator control each account what are the optional work group, something happened between us is in big data platform table task of building, ran to the table is built on the TiDB mistake, first of all to determine what you are running data of the platform, only then a default authorization work group, and if you need to connect to multiple places, authorized the account in multiple group work.
   10. After taking the task offline and adjusting the task, we have to choose the work group again every time we go online. The user experience is not very good.If I chose which work group to work under last time, these will also be in the last work environment. Only when the work group is explicitly changed, users need to choose again, instead of choosing the work group every time.At least remember my last choice.

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services