You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@devlake.apache.org by zk...@apache.org on 2022/07/04 16:29:33 UTC
[incubator-devlake-website] branch main updated: fix: update table issue_changelogs
This is an automated email from the ASF dual-hosted git repository.
zky pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/incubator-devlake-website.git
The following commit(s) were added to refs/heads/main by this push:
new 1bb03df fix: update table issue_changelogs
1bb03df is described below
commit 1bb03df1f3d286c199b55682521e0cffb6d19b28
Author: Startrekzky <ka...@merico.dev>
AuthorDate: Tue Jul 5 00:23:37 2022 +0800
fix: update table issue_changelogs
---
docs/DataModels/01-DevLakeDomainLayerSchema.md | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/docs/DataModels/01-DevLakeDomainLayerSchema.md b/docs/DataModels/01-DevLakeDomainLayerSchema.md
index 3402e4b..80bd41b 100644
--- a/docs/DataModels/01-DevLakeDomainLayerSchema.md
+++ b/docs/DataModels/01-DevLakeDomainLayerSchema.md
@@ -17,9 +17,9 @@ Data in the domain layer is transformed from the data in the tool layer. The too
Domain layer schema itself includes 2 logical layers: a `DWD` layer and a `DWM` layer. The DWD layer stores the detailed data points, while the DWM is the slight aggregation and operation of DWD to store more organized details or middle-level metrics.
-## Use Case Scenario
+## Use Cases
1. Users can make customized Grafana dashboards based on the domain layer schema.
-2. Contributors can understand more about DevLake's data model.
+2. Contributors can complete the ETL logic when adding new data source plugins refering to this data model.
## Data Model
@@ -117,7 +117,6 @@ This table shows the changelogs of issues. Issues with multiple changelogs are s
| `issue_id` | varchar | 255 | Issue ID | FK_issues.id |
| `actor_id` | varchar | 255 | The id of the user who made the change | FK_users.id |
| `field` | varchar | 255 | The id of changed field | |
-| `action` | varchar | 255 | The operation. For instance, an action may be 'create', 'update', etc.| |
| `from` | varchar | 255 | The original value of the changed field | |
| `to` | varchar | 255 | The new value of the changed field | |
| `created_date` | datetime | 3 | The creation date of the changelog | |