This is an automated email from the ASF dual-hosted git repository.
zhonghongsheng pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/shardingsphere.git
The following commit(s) were added to refs/heads/master by this push:
new b59b1196be0 Update
2023_02_09_Leverage_Terraform_to_Create_an_Apache_ShardingSphere_Proxy_High_Availability_Cluster_on_AWS.en.md
(#24573)
b59b1196be0 is described below
commit b59b1196be01df516dc31350953d25eae088e109
Author: FPokerFace <[email protected]>
AuthorDate: Mon Mar 13 13:43:45 2023 +0800
Update
2023_02_09_Leverage_Terraform_to_Create_an_Apache_ShardingSphere_Proxy_High_Availability_Cluster_on_AWS.en.md
(#24573)
* Upload 2 Blogs to Shardingsphere
* Update
2023_01_04_Refactoring_the_DistSQL_Syntax__ShardingSphere_5.3.0_Deep_Dive.en.md
* Update
2023_01_04_Refactoring_the_DistSQL_Syntax__ShardingSphere_5.3.0_Deep_Dive.en.md
* Update
2023_02_09_Leverage_Terraform_to_Create_an_Apache_ShardingSphere_Proxy_High_Availability_Cluster_on_AWS.en.md
* Fix the recent blogs
* Fix the recent blogs
---
...QL_Syntax__ShardingSphere_5.3.0_Deep_Dive.en.md | 78 +++++++++++-----------
...re_Proxy_High_Availability_Cluster_on_AWS.en.md | 8 +--
2 files changed, 43 insertions(+), 43 deletions(-)
diff --git
a/docs/blog/content/material/2023_01_04_Refactoring_the_DistSQL_Syntax__ShardingSphere_5.3.0_Deep_Dive.en.md
b/docs/blog/content/material/2023_01_04_Refactoring_the_DistSQL_Syntax__ShardingSphere_5.3.0_Deep_Dive.en.md
index fcc92d2dda6..20e5c79d87b 100644
---
a/docs/blog/content/material/2023_01_04_Refactoring_the_DistSQL_Syntax__ShardingSphere_5.3.0_Deep_Dive.en.md
+++
b/docs/blog/content/material/2023_01_04_Refactoring_the_DistSQL_Syntax__ShardingSphere_5.3.0_Deep_Dive.en.md
@@ -92,17 +92,17 @@ The new release 5.3.0 has upgraded DistSQL. We have
completely sorted out and re
-> Description: keyword `INSTANCE` is updated to `COMPUTE NODE`.
+*Description: keyword* `INSTANCE` *is updated to* `COMPUTE NODE`*.*
**Storage Node**
-> Description:
->
-> Keyword `RESOURCE` is updated to `STORAGE NODE / STORAGE UNIT`, which
corresponds to instance-level storage and database-level storage respectively.
->
-> The `STORAGE NODE` is reserved and is not used currently.
+*Description:*
+
+*Keyword* `RESOURCE` *is updated to* `STORAGE NODE / STORAGE UNIT`*, which
corresponds to instance-level storage and database-level storage respectively.*
+
+*The* `STORAGE NODE` *is reserved and is not used currently.*
## Instance Object
@@ -114,29 +114,29 @@ Global rule syntax is not adjusted this time.
-> Description: DIST is added before VARIABLE to represent a distributed
variable.
+*Description:* `DIST` *is added before* `VARIABLE` *to represent a distributed
variable.*
**MIGRATION Job**
-> Description:
->
-> `PROCESS CONFIGURATION` keyword is changed to `RULE`.
->
-> Remove `CREATE` and `DROP` operations because `MIGRATION RULE` has default
values.
->
-> Other syntax is not adjusted.
+*Description:*
+
+`PROCESS CONFIGURATION` *keyword is changed to* `RULE`*.*
+
+*Remove* `CREATE` *and* `DROP` *operations because* `MIGRATION RULE` *has
default values.*
+
+*Other syntax is not adjusted.*
## Database Object
-> Description:
->
-> `CONFIG` is changed to `CONFIGURATION`, which is more accurate.
->
-> The `REFRESH DATABASE METADATA `statement is added to pull the configuration
from the governance center to forcibly refresh the local metadata.
+*Description:*
+
+`CONFIG` *is changed to* `CONFIGURATION`*, which is more accurate.*
+
+*The* `REFRESH DATABASE METADATA` *statement is added to pull the
configuration from the governance center to forcibly refresh the local
metadata.*
## Table Object
@@ -144,7 +144,7 @@ Global rule syntax is not adjusted this time.
-> Description: `SHARDING` keyword is removed from the broadcast table.
+*Description:* `SHARDING` *keyword is removed from the broadcast table.*
**Data Encryption**
@@ -154,17 +154,17 @@ The syntax related to data encryption is not adjusted
this time. Please refer to
-> Description:
->
-> Remove the syntax for independently creating sharding algorithms and
distributed ID generators and integrate them into the rule definition of
`CREATE SHARDING TABLE RULE.`
->
-> Other syntax is not adjusted.
+*Description:*
+
+*Remove the syntax for independently creating sharding algorithms and
distributed ID generators and integrate them into the rule definition of*
`CREATE SHARDING TABLE RULE`*.*
+
+*Other syntax is not adjusted.*
**Single Table**
-> Description: by default, only one single-table router can be created. And
`CREATE` is updated to `SET`.
+*Description: by default, only one single-table router can be created. And*
`CREATE` *is updated to* `SET`*.*
## **Relation Object**
@@ -172,23 +172,23 @@ The syntax related to data encryption is not adjusted
this time. Please refer to
-> Description:
->
-> Remove the syntax for creating a `DB_DISCOVERY TYPE` and `HEARTBEAT`
independently and integrate them into the rule definition of the `CREATE
DB_DISCOVERY RULE`.
->
-> Other syntax is not adjusted.
+*Description:*
+
+*Remove the syntax for creating a* `DB_DISCOVERY TYPE` *and* `HEARTBEAT`
*independently and integrate them into the rule definition of the* `CREATE
DB_DISCOVERY RULE`*.*
+
+*Other syntax is not adjusted.*
**Binding Table**
-> Description: adjust the keyword and add `ruleName` for easier management.
+*Description: adjust the keyword and add* `ruleName` *for easier management.*
# Traffic Object
**Read/write Splitting**
-Description: there is no major change to read/write splitting syntax. Only
`RESOURCE` is replaced with `STORAGE_UNIT` based on the keyword change of the
storage node. For example:
+*Description: there is no major change to read/write splitting syntax. Only*
`RESOURCE` *is replaced with* `STORAGE_UNIT` *based on the keyword change of
the storage node. For example:*
```sql
CREATE READWRITE_SPLITTING RULE ms_group_0 (
@@ -202,11 +202,11 @@ TYPE(NAME="random")
-> Description:
->
-> Remove syntax for creating shadow algorithms independently and integrate it
into the rule definition of `CREATE SHADOW RULE`.
->
-> Add statements to `ALTER` and `SHOW` default shadow algorithm, corresponding
to `CREATE DEFAULT SHADOW ALGORITHM`.
+*Description:*
+
+*Remove syntax for creating shadow algorithms independently and integrate it
into the rule definition of* `CREATE SHADOW RULE`*.*
+
+*Add statements to* `ALTER` *and* `SHOW` *default shadow algorithm,
corresponding to* `CREATE DEFAULT SHADOW ALGORITHM`*.*
# Property Specification Optimization
@@ -231,7 +231,7 @@ After this optimization, you can omit quotes when
referencing a built-in algorit
Therefore, the following is also rightful and equivalent:
```sql
-TYPE(NAME="MOD",PROPERTIES("sharding-count"="4"))
+TYPE(NAME="MOD",PROPERTIES("sharding-count"=4))
```
# Demo
diff --git
a/docs/blog/content/material/2023_02_09_Leverage_Terraform_to_Create_an_Apache_ShardingSphere_Proxy_High_Availability_Cluster_on_AWS.en.md
b/docs/blog/content/material/2023_02_09_Leverage_Terraform_to_Create_an_Apache_ShardingSphere_Proxy_High_Availability_Cluster_on_AWS.en.md
index 0eb96babde2..1561ce0d7d1 100644
---
a/docs/blog/content/material/2023_02_09_Leverage_Terraform_to_Create_an_Apache_ShardingSphere_Proxy_High_Availability_Cluster_on_AWS.en.md
+++
b/docs/blog/content/material/2023_02_09_Leverage_Terraform_to_Create_an_Apache_ShardingSphere_Proxy_High_Availability_Cluster_on_AWS.en.md
@@ -1,5 +1,5 @@
+++
-title = "Leverage Terraform to Create an [Apache
ShardingSphere](https://medium.com/u/b9760a2e8a07?source=post_page-----45d27a114904--------------------------------)
Proxy High Availability Cluster on AWS"
+title = "Leverage Terraform to Create an Apache ShardingSphere Proxy High
Availability Cluster on AWS"
weight = 86
chapter = true
+++
@@ -18,15 +18,15 @@ It’s supported by public cloud vendors such as AWS, GCP,
AZURE and a variety o
**Terraform has the following advantages:**
-> Support for multi-cloud deployments
+*Support for multi-cloud deployments*
Terraform is suitable for multi-cloud scenarios, deploying similar
infrastructures such as Alibaba Cloud, or other cloud providers and local data
centres. Developers can use the same tools and similar profiles to manage
resources from different cloud providers simultaneously.
-> Automated management infrastructure
+*Automated management infrastructure*
Terraform’s ability to create reusable modules reduces human-induced
deployment and management errors.
-> Infrastructure as code
+*Infrastructure as code*
Resources can be managed and maintained in code, allowing infrastructure state
to be saved. This enables users to track changes made to different components
of the system (infrastructure as code) and share these configurations with
others.
