Dolphinscheduler: [Bug][DAG Editor] the dag node data loss by switch browser tab

Created on 23 Dec 2020  路  5Comments  路  Source: apache/dolphinscheduler

#4162
this pr make a new problem, when you are editing dag:
eg:

  1. update a sql node and click ok(not save the dag)
  2. switch tab to copy something;
  3. switch to ds dag edit tab;
  4. open the node param ,found that the sql change is lost!

that means,i have to save the dag with any small change! that will make the dag version boom...

bug discussion

All 5 comments

@geosmart @break60
This is a problem caused by state synchronization in new tab. For state synchronization, we will refresh page in new opened page.
If we don't do this, the issue the task of a certain tab is changed, and the task of another tab will not be updated synchronously referenced by @break60 will occur.

This is the trade-off

the designing dag data will loss when:

  1. switch browser to another app
  2. switch browser tab

this means:
you must design a complex dag without refer anything, that's impossibe!
or you have to save the uncomplete dag version(it's a garbage dag version, not real working when scheduled)

Maybe I filter some scenarios to resolve this issue, so I will fix it.

visibility change is a good feature, if you add some filter may be better :

  1. some scenario no need to refresh: create,update
  2. some scenario need to refresh: detail,list
Was this page helpful?
0 / 5 - 0 ratings