fix set configuration: add quote mark

Author: leto-b

src/UserGuide/Master/Tree/Reference/Modify-Config-Manual.md

@@ -37,21 +37,21 @@ load configuration
 ```
 # SetConfiguration statement
 ```
-set configuration key1 = 'value1' key2 = 'value2'... (on nodeId)
+set configuration 'key1' = 'value1' 'key2' = 'value2'... (on nodeId)
 ```
 ### Example 1
 ```
-set configuration enable_cross_space_compaction='false'
+set configuration 'enable_cross_space_compaction'='false'
 ```
 To take effect permanently on all nodes in the cluster, set enable_cross_space_compaction to false and write it to iotdb-system.properties.
 ### Example 2
 ```
-set configuration enable_cross_space_compaction='false' enable_seq_space_compaction='false' on 1
+set configuration 'enable_cross_space_compaction'='false' 'enable_seq_space_compaction'='false' on 1
 ```
 To take effect permanently on the node with nodeId 1, set enable_cross_space_compaction to false, set enable_seq_space_compaction to false, and write it to iotdb-system.properties.
 ### Example 3
 ```
-set configuration enable_cross_space_compaction='false' timestamp_precision='ns'
+set configuration 'enable_cross_space_compaction'='false' 'timestamp_precision'='ns'
 ```
 To take effect permanently on all nodes in the cluster, set enable_cross_space_compaction to false, timestamp_precision to ns, and write it to iotdb-system.properties. However, timestamp_precision is a configuration item that cannot be modified after the first startup, so the update of this configuration item will be ignored and the return is as follows.
 ```
@@ -63,7 +63,7 @@ Configuration items that support hot reloading and take effect immediately are m
 Example
 ```
 # Used for indicate cluster name and distinguish different cluster.
-# If you need to modify the cluster name, it's recommended to use [set configuration cluster_name='xxx'] sql.
+# If you need to modify the cluster name, it's recommended to use [set configuration 'cluster_name'='xxx'] sql.
 # Manually modifying configuration file is not recommended, which may cause node restart fail.
 # effectiveMode: hot_reload
 # Datatype: string

src/UserGuide/Master/Tree/User-Manual/Maintenance-commands.md

@@ -280,7 +280,7 @@ propertyValue
 **Example**:
 
 ```SQL
-IoTDB> SET CONFIGURATION a='1',b='1' ON 1;
+IoTDB> SET CONFIGURATION 'a'='1','b'='1' ON 1;
 ```
 
 ### 2.3 Loading Manually Modified Configuration Files

src/UserGuide/V1.3.x/Reference/Modify-Config-Manual.md

@@ -37,21 +37,21 @@ load configuration
 ```
 # SetConfiguration statement
 ```
-set configuration key1 = 'value1' key2 = 'value2'... (on nodeId)
+set configuration 'key1' = 'value1' 'key2' = 'value2'... (on nodeId)
 ```
 ### Example 1
 ```
-set configuration enable_cross_space_compaction='false'
+set configuration 'enable_cross_space_compaction'='false'
 ```
 To take effect permanently on all nodes in the cluster, set enable_cross_space_compaction to false and write it to iotdb-system.properties.
 ### Example 2
 ```
-set configuration enable_cross_space_compaction='false' enable_seq_space_compaction='false' on 1
+set configuration 'enable_cross_space_compaction'='false' 'enable_seq_space_compaction'='false' on 1
 ```
 To take effect permanently on the node with nodeId 1, set enable_cross_space_compaction to false, set enable_seq_space_compaction to false, and write it to iotdb-system.properties.
 ### Example 3
 ```
-set configuration enable_cross_space_compaction='false' timestamp_precision='ns'
+set configuration 'enable_cross_space_compaction'='false' 'timestamp_precision'='ns'
 ```
 To take effect permanently on all nodes in the cluster, set enable_cross_space_compaction to false, timestamp_precision to ns, and write it to iotdb-system.properties. However, timestamp_precision is a configuration item that cannot be modified after the first startup, so the update of this configuration item will be ignored and the return is as follows.
 ```
@@ -63,7 +63,7 @@ Configuration items that support hot reloading and take effect immediately are m
 Example
 ```
 # Used for indicate cluster name and distinguish different cluster.
-# If you need to modify the cluster name, it's recommended to use [set configuration cluster_name='xxx'] sql.
+# If you need to modify the cluster name, it's recommended to use [set configuration 'cluster_name'='xxx'] sql.
 # Manually modifying configuration file is not recommended, which may cause node restart fail.
 # effectiveMode: hot_reload
 # Datatype: string

src/UserGuide/V1.3.x/User-Manual/Maintenance-commands.md

@@ -225,7 +225,7 @@ propertyValue
 **Example**:
 
 ```SQL
-IoTDB> SET CONFIGURATION a='1',b='1' ON 1;
+IoTDB> SET CONFIGURATION 'a'='1','b'='1' ON 1;
 ```
 
 ### 2.2 Loading Manually Modified Configuration Files

src/UserGuide/dev-1.3/Reference/Modify-Config-Manual.md

@@ -37,21 +37,21 @@ load configuration
 ```
 # SetConfiguration statement
 ```
-set configuration key1 = 'value1' key2 = 'value2'... (on nodeId)
+set configuration 'key1' = 'value1' 'key2' = 'value2'... (on nodeId)
 ```
 ### Example 1
 ```
-set configuration enable_cross_space_compaction='false'
+set configuration 'enable_cross_space_compaction'='false'
 ```
 To take effect permanently on all nodes in the cluster, set enable_cross_space_compaction to false and write it to iotdb-system.properties.
 ### Example 2
 ```
-set configuration enable_cross_space_compaction='false' enable_seq_space_compaction='false' on 1
+set configuration 'enable_cross_space_compaction'='false' 'enable_seq_space_compaction'='false' on 1
 ```
 To take effect permanently on the node with nodeId 1, set enable_cross_space_compaction to false, set enable_seq_space_compaction to false, and write it to iotdb-system.properties.
 ### Example 3
 ```
-set configuration enable_cross_space_compaction='false' timestamp_precision='ns'
+set configuration 'enable_cross_space_compaction'='false' 'timestamp_precision'='ns'
 ```
 To take effect permanently on all nodes in the cluster, set enable_cross_space_compaction to false, timestamp_precision to ns, and write it to iotdb-system.properties. However, timestamp_precision is a configuration item that cannot be modified after the first startup, so the update of this configuration item will be ignored and the return is as follows.
 ```
@@ -63,7 +63,7 @@ Configuration items that support hot reloading and take effect immediately are m
 Example
 ```
 # Used for indicate cluster name and distinguish different cluster.
-# If you need to modify the cluster name, it's recommended to use [set configuration cluster_name='xxx'] sql.
+# If you need to modify the cluster name, it's recommended to use [set configuration 'cluster_name'='xxx'] sql.
 # Manually modifying configuration file is not recommended, which may cause node restart fail.
 # effectiveMode: hot_reload
 # Datatype: string

src/UserGuide/dev-1.3/User-Manual/Maintenance-commands.md

@@ -225,7 +225,7 @@ propertyValue
 **Example**:
 
 ```SQL
-IoTDB> SET CONFIGURATION a='1',b='1' ON 1;
+IoTDB> SET CONFIGURATION 'a'='1','b'='1' ON 1;
 ```
 
 ### 2.2 Loading Manually Modified Configuration Files

src/UserGuide/latest/Reference/Modify-Config-Manual.md

@@ -37,21 +37,21 @@ load configuration
 ```
 # SetConfiguration statement
 ```
-set configuration key1 = 'value1' key2 = 'value2'... (on nodeId)
+set configuration 'key1' = 'value1' 'key2' = 'value2'... (on nodeId)
 ```
 ### Example 1
 ```
-set configuration enable_cross_space_compaction='false'
+set configuration 'enable_cross_space_compaction'='false'
 ```
 To take effect permanently on all nodes in the cluster, set enable_cross_space_compaction to false and write it to iotdb-system.properties.
 ### Example 2
 ```
-set configuration enable_cross_space_compaction='false' enable_seq_space_compaction='false' on 1
+set configuration 'enable_cross_space_compaction'='false' 'enable_seq_space_compaction'='false' on 1
 ```
 To take effect permanently on the node with nodeId 1, set enable_cross_space_compaction to false, set enable_seq_space_compaction to false, and write it to iotdb-system.properties.
 ### Example 3
 ```
-set configuration enable_cross_space_compaction='false' timestamp_precision='ns'
+set configuration 'enable_cross_space_compaction'='false' 'timestamp_precision'='ns'
 ```
 To take effect permanently on all nodes in the cluster, set enable_cross_space_compaction to false, timestamp_precision to ns, and write it to iotdb-system.properties. However, timestamp_precision is a configuration item that cannot be modified after the first startup, so the update of this configuration item will be ignored and the return is as follows.
 ```
@@ -63,7 +63,7 @@ Configuration items that support hot reloading and take effect immediately are m
 Example
 ```
 # Used for indicate cluster name and distinguish different cluster.
-# If you need to modify the cluster name, it's recommended to use [set configuration cluster_name='xxx'] sql.
+# If you need to modify the cluster name, it's recommended to use [set configuration 'cluster_name'='xxx'] sql.
 # Manually modifying configuration file is not recommended, which may cause node restart fail.
 # effectiveMode: hot_reload
 # Datatype: string

src/UserGuide/latest/User-Manual/Maintenance-commands.md

@@ -280,7 +280,7 @@ propertyValue
 **Example**:
 
 ```SQL
-IoTDB> SET CONFIGURATION a='1',b='1' ON 1;
+IoTDB> SET CONFIGURATION 'a'='1','b'='1' ON 1;
 ```
 
 ### 2.3 Loading Manually Modified Configuration Files

src/zh/UserGuide/Master/Tree/Reference/Modify-Config-Manual.md

@@ -38,21 +38,21 @@ load configuration
 # 配置项操作语句
 设置配置项
 ```
-set configuration key1 = 'value1' key2 = 'value2'... (on nodeId)
+set configuration 'key1' = 'value1' 'key2' = 'value2'... (on nodeId)
 ```
 ### 示例1
 ```
-set configuration enable_cross_space_compaction = 'false'
+set configuration 'enable_cross_space_compaction' = 'false'
 ```
 对集群所有节点永久生效，设置 enable_cross_space_compaction 为 false，并写入到 iotdb-system.properties 中。
 ### 示例2
 ```
-set configuration enable_cross_space_compaction ='false' enable_seq_space_compaction = 'false' on 1
+set configuration 'enable_cross_space_compaction' ='false' 'enable_seq_space_compaction' = 'false' on 1
 ```
 对 nodeId 为 1 的节点永久生效，设置 enable_cross_space_compaction 为 false，设置 enable_seq_space_compaction 为 false，并写入到 iotdb-system.properties 中。
 ### 示例3
 ```
-set configuration  enable_cross_space_compaction = 'false'  timestamp_precision = 'ns'
+set configuration  'enable_cross_space_compaction' = 'false'  'timestamp_precision' = 'ns'
 ```
 对集群所有节点永久生效，设置 enable_cross_space_compaction 为 false，timestamp_precision 为 ns，并写入到 iotdb-system.properties 中。但是，timestamp_precision 是第一次启动后就无法修改的配置项，因此会忽略这个配置项的更新，返回如下。
 ```
@@ -63,7 +63,7 @@ Msg: org.apache.iotdb.jdbc.IoTDBSQLException: 301: ignored config items: [timest
 示例
 ```
 # Used for indicate cluster name and distinguish different cluster.
-# If you need to modify the cluster name, it's recommended to use [set configuration cluster_name='xxx'] sql.
+# If you need to modify the cluster name, it's recommended to use [set configuration 'cluster_name'='xxx'] sql.
 # Manually modifying configuration file is not recommended, which may cause node restart fail.
 # effectiveMode: hot_reload
 # Datatype: string

src/zh/UserGuide/Master/Tree/User-Manual/Maintenance-statement.md

@@ -281,7 +281,7 @@ propertyValue
 #### 示例：
 
 ```SQL
-IoTDB> SET CONFIGURATION a='1',b='1' ON 1;
+IoTDB> SET CONFIGURATION 'a'='1','b'='1' ON 1;
 ```
 
 ### 2.3 读取手动修改的配置文件