[GitHub] [shardingsphere-elasticjob] terrymanu commented on a change in pull request #1154: Translate user manual, table-structure for event-trace.

[GitBox <gi...@apache.org>]

terrymanu commented on a change in pull request #1154:
URL: https://github.com/apache/shardingsphere-elasticjob/pull/1154#discussion_r456852651



##########
File path: docs/content/user-manual/elasticjob-lite/usage/event-trace/table-structure.cn.md
##########
@@ -26,7 +26,7 @@ JOB_EXECUTION_LOG 记录每次作业的执行历史。
 分为两个步骤：
 
 1. 作业开始执行时向数据库插入数据，除 failure_cause 和 complete_time 外的其他字段均不为空。
-1. 作业完成执行时向数据库更新数据，更新 is_success, complete_time 和 failure_cause(如果作业执行失败)。
+2. 作业完成执行时向数据库更新数据，更新 is_success, complete_time 和 failure_cause(如果作业执行失败)。

Review comment:
       Please do not modify here, it is the correct md syntax.
   The number will auto increment

##########
File path: docs/content/user-manual/elasticjob-lite/usage/event-trace/table-structure.en.md
##########
@@ -4,4 +4,45 @@ weight = 4
 chapter = true
 +++
 
-TODO
+The database which is the value of the event tracing property `event_trace_rdb_url` will automatically creates two tables `JOB_EXECUTION_LOG` and `JOB_STATUS_TRACE_LOG` and several indexes.
+
+## JOB_EXECUTION_LOG columns
+
+| Column name      | Column type   | Required  | Describe                                                   |
+| ---------------- |:------------- |:--------- |:----------------------------------------------------- |
+| id               | VARCHAR(40)   | Yes       | Primary key                                                   |
+| job_name         | VARCHAR(100)  | Yes       | Job name                                               |
+| task_id          | VARCHAR(1000) | Yes       | Task name, create new tasks every time the job runs.    |
+| hostname         | VARCHAR(255)  | Yes       | Hostname                                               |
+| ip               | VARCHAR(50)   | Yes       | IP                                                |
+| sharding_item    | INT           | Yes       | Sharding item                                                |
+| execution_source | VARCHAR(20)   | Yes       | Source of job execution. The value options are `NORMAL_TRIGGER`, `MISFIRE`, `FAILOVER`. |
+| failure_cause    | VARCHAR(2000) | No        | The reason for execution failure                                           |
+| is_success       | BIT           | Yes       | Execute successfully or not                                           |
+| start_time       | TIMESTAMP     | Yes       | Job start time                                        |
+| complete_time    | TIMESTAMP     | No        | Job end time                                        |
+
+`JOB_EXECUTION_LOG` records the execution history of each job.
+There are two steps:
+
+1. When the job is executed, program will create one record in the `JOB_EXECUTION_LOG`, and all fields except `failure_cause` and `complete_time` are not empty.
+2. When the job completes execution, program will update the record, update the columns of `is_success`, `complete_time` and `failure_cause`(if the job execution fails).

Review comment:
       Please leave here as `1.`




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

For queries about this service, please contact Infrastructure at:
users@infra.apache.org