Skip to content

Commit b17f949

Browse files
committed
fixup! [AMORO-3404] Correct the description about MySQL usage
1 parent a053083 commit b17f949

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

amoro-docs/content/admin-guides/deployment-on-kubernetes.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -156,8 +156,8 @@ ingress:
156156
157157
### Configure the database.
158158
159-
AMS default is to use Derby database for storage. When the pod is destroyed, the data will also disappear.
160-
In production environments, we recommend using a RDBMS as the storage for system data, you can ref to [Database Configuration](/deployment/#configure-system-database) for more detail.
159+
AMS uses embedded [Apache Derby](https://db.apache.org/derby/) as its backend storage by default.
160+
In production environments, we recommend using a RDBMS(Relational Database Management System) with higher availability guarantees as the storage for system data, you can ref to [Database Configuration](/deployment/#configure-system-database) for more detail.
161161
162162
```yaml
163163
amoroConf:

amoro-docs/content/admin-guides/deployment.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -98,7 +98,7 @@ Make sure the port is not used before configuring it.
9898
9999
### Configure system database
100100
101-
Amoro used `Derby` as the backend storage default, so you can use `Derby` directly without any additional configuration.
101+
AMS uses embedded [Apache Derby](https://db.apache.org/derby/) as the backend storage by default, so you can use `Derby` directly without any additional configuration.
102102

103103
You can also configure a relational backend storage as you needed.
104104

0 commit comments

Comments
 (0)