When you use DataWorks to run SQL statements in Data Development and synchronization tasks in Data Integration, you may come up with these questions: What are the differences between running on pages and test run? Why does the system prompt me to enter temporary values for system variables, instead of auto parsing the system parameters I have configured during the running in codes?
Now, let’s see the major differences between running on pages and test run.
In this mode, the tasks are directly distributed to the underlying layer instead of being submitted to the scheduling system. For this reason, you must specify the value for the parsing of scheduling parameters when using these parameters. Also, the running triggered on pages does not generate any instance, so the server for the task running cannot be specified. Therefore, the tasks can only be distributed to the default resource group of DataWorks for running.
In Data Development, a custom parameter is used in SQL statements when a SQL node task is created. In this case, a prompt box is displayed when you click Run on the page. In this prompt box, you must enter a specific value but not a variable like $[yyyymmdd], which cannot be recognized in codes.
In Data Integration, a custom parameter is used in the script when a task is created in script mode. After saving the task and clicking Run on the page, a prompt box is displayed prompting you to assign a value for the custom parameter.
The specified value is not parsed, because system parameters and custom system parameters are the scheduling system parameters, which can be parsed only in the scheduling system. However, the task running on the page is not distributed to the scheduling system. Therefore, you must enter a specific value for the custom parameter, so that it can be replaced during the task execution.
Given that tasks in the test run are distributed to the scheduling system to generate instances, scheduling parameters can be auto parsed during the run, and you can specify the resource group for running these instances.