lenboo commented on a change in pull request #6485:
URL: https://github.com/apache/dolphinscheduler/pull/6485#discussion_r725811690



##########
File path: sql/dolphinscheduler_mysql.sql
##########
@@ -317,22 +317,24 @@ CREATE TABLE `t_ds_alertgroup`(
 -- ----------------------------
 DROP TABLE IF EXISTS `t_ds_command`;
 CREATE TABLE `t_ds_command` (
-  `id` int(11) NOT NULL AUTO_INCREMENT COMMENT 'key',
-  `command_type` tinyint(4) DEFAULT NULL COMMENT 'Command type: 0 start 
workflow, 1 start execution from current node, 2 resume fault-tolerant 
workflow, 3 resume pause process, 4 start execution from failed node, 5 
complement, 6 schedule, 7 rerun, 8 pause, 9 stop, 10 resume waiting thread',
-  `process_definition_code` bigint(20) DEFAULT NULL COMMENT 'process 
definition code',
-  `command_param` text COMMENT 'json command parameters',
-  `task_depend_type` tinyint(4) DEFAULT NULL COMMENT 'Node dependency type: 0 
current node, 1 forward, 2 backward',
-  `failure_strategy` tinyint(4) DEFAULT '0' COMMENT 'Failed policy: 0 end, 1 
continue',
-  `warning_type` tinyint(4) DEFAULT '0' COMMENT 'Alarm type: 0 is not sent, 1 
process is sent successfully, 2 process is sent failed, 3 process is sent 
successfully and all failures are sent',
-  `warning_group_id` int(11) DEFAULT NULL COMMENT 'warning group',
-  `schedule_time` datetime DEFAULT NULL COMMENT 'schedule time',
-  `start_time` datetime DEFAULT NULL COMMENT 'start time',
-  `executor_id` int(11) DEFAULT NULL COMMENT 'executor id',
-  `update_time` datetime DEFAULT NULL COMMENT 'update time',
+  `id`                        int(11)    NOT NULL AUTO_INCREMENT COMMENT 'key',

Review comment:
       yes, i add two fields in the end
   and find the sql format is invalid, so i change the format at the same.




-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to