[Bug-12954] [Schedule] Fix that workflow-level configuration information does not take effect when timing triggers execution (#12955)

This commit is contained in:
Kerwin 2022-11-22 15:35:29 +08:00 committed by GitHub
parent 3747029cc0
commit 2f8f0952fb
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 1 deletions

View File

@ -19,7 +19,7 @@ Sqoop task type for executing Sqoop application. The workers run `sqoop` to exec
| **Parameter** | **Description** |
|-------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Job Name | map-reduce job name |
| Direct | (1) import:Imports an individual table from an RDBMS to HDFS or Hive. (2) export:Exports a set of files from HDFS or Hive back to an RDBMS. |
| Direct | (1) import:Imports an individual table from an RDBMS to HDFS or Hive. (2) export:Exports a set of files from HDFS or Hive back to an RDBMS. |
| Hadoop Params | Hadoop custom param for sqoop job. |
| Sqoop Advanced Parameters | Sqoop advanced param for sqoop job. |
| Data Source - Type | Select the corresponding data source type. |

View File

@ -100,6 +100,7 @@ public class ProcessScheduleTask extends QuartzJobBean {
String workerGroup = StringUtils.isEmpty(schedule.getWorkerGroup()) ? Constants.DEFAULT_WORKER_GROUP
: schedule.getWorkerGroup();
command.setWorkerGroup(workerGroup);
command.setEnvironmentCode(schedule.getEnvironmentCode());
command.setWarningType(schedule.getWarningType());
command.setProcessInstancePriority(schedule.getProcessInstancePriority());
command.setProcessDefinitionVersion(processDefinition.getVersion());