Parameters can be set in environment variables, job parameters, and script parameters, but their application scopes are different. If there is a conflict when parameters in environment variables, job parameters, and script parameters of the same name, the calling priority is: job parameters > environment variables > script parameters.
Introduction and usage of environment variables, job parameters, and script parameters are as follows:
- Variables and constants can be defined in environment variables. Environment variables take effect in current workspace.
- The value of a variable (such as workspace name) varies depending on the workspace. When exporting a variable from a workspace and import it to another workspace, you must reconfigure its value.
- The value of a constant in different workspaces is the same. When importing a constant to another workspace, you do not need to reconfigure its value.
Figure 1 Environment variable
- Parameters and constants can be defined in job parameters. Job parameters take effect in current job.
- The value of a parameter varies depending on jobs. When exporting a parameter from a workspace and import it to another workspace, you must reconfigure its value.
- The value of a constant in different jobs is the same. When importing a constant to another job, you do not need to reconfigure its value.
Figure 2 Job parameter.
- Script parameters take effect in current script and it can be used in the following ways.
- Enter SQL script parameters in the script editor (Flink SQL is not supported). If the script is executed independently, you can configure the parameters in the lower part of the editor, as shown in Figure 3. If the script is executed by job scheduling, you can assign values to the parameters based on node attributes, as shown in Figure 4.
- For Shell scripts, you can enter a parameter and an interactive parameter in the upper part of the editor to transfer the parameters.
- Python scripts do not support parameter transfer.
