Update udf and jdbc cluster description

src/UserGuide/Master/Table/API/Programming-JDBC_apache.md

@@ -71,6 +71,7 @@ Add the following dependency to your Maven `pom.xml` file:
 ```Java
 String url = "jdbc:iotdb://127.0.0.1:6667?sql_dialect=table";
 ```
+When connecting to a cluster via JDBC, configuring the URL with any one node in the cluster is sufficient.
 
 You can find the full example code at [GitHub Repository](https://github.com/apache/iotdb/blob/master/example/jdbc/src/main/java/org/apache/iotdb/TableModelJDBCExample.java).
 

src/UserGuide/Master/Table/API/Programming-JDBC_timecho.md

@@ -71,6 +71,7 @@ Add the following dependency to your Maven `pom.xml` file:
 ```Java
 String url = "jdbc:iotdb://127.0.0.1:6667?sql_dialect=table";
 ```
+When connecting to a cluster via JDBC, configuring the URL with any one node in the cluster is sufficient.
 
 You can find the full example code at [GitHub Repository](https://github.com/apache/iotdb/blob/master/example/jdbc/src/main/java/org/apache/iotdb/TableModelJDBCExample.java).
 

src/UserGuide/Master/Tree/API/Programming-JDBC.md

@@ -212,6 +212,8 @@ String url = "jdbc:iotdb://127.0.0.1:6667?version=V_1_0";
 The parameter `version` represents the SQL semantic version used by the client, which is used in order to be compatible with the SQL semantics of `0.12` when upgrading to `0.13`. 
 The possible values are: `V_0_12`, `V_0_13`, `V_1_0`.
 
+When connecting to a cluster via JDBC, configuring the URL with any one node in the cluster is sufficient.
+
 In addition, IoTDB provides additional interfaces in JDBC for users to read and write the database using different character sets (e.g., GB18030) in the connection.
 The default character set for IoTDB is UTF-8. When users want to use a character set other than UTF-8, they need to specify the charset property in the JDBC connection. For example:
 1. Create a connection using the GB18030 charset:

src/UserGuide/Master/Tree/User-Manual/User-defined-function_apache.md

@@ -97,7 +97,7 @@ CREATE FUNCTION <UDF-NAME> AS <UDF-CLASS-FULL-PATHNAME> (USING URI URI-STRING)
 ####  Method 1: Manually place the jar package
 
 Prepare:   
-When registering using this method, it is necessary to place the JAR package in advance in the `ext/udf` directory of all nodes in the cluster (which can be configured).
+When registering using this method, it is necessary to place the JAR package in advance in the `ext/udf` directory of **all nodes in the cluster** (which can be configured).
 
 Registration statement:
 

src/UserGuide/Master/Tree/User-Manual/User-defined-function_timecho.md

@@ -98,7 +98,7 @@ CREATE FUNCTION <UDF-NAME> AS <UDF-CLASS-FULL-PATHNAME> (USING URI URI-STRING)
 ####  Method 1: Manually place the jar package
 
 Prepare:   
-When registering using this method, it is necessary to place the JAR package in advance in the `ext/udf` directory of all nodes in the cluster (which can be configured).
+When registering using this method, it is necessary to place the JAR package in advance in the `ext/udf` directory of **all nodes in the cluster** (which can be configured).
 
 Registration statement:
 

src/UserGuide/V1.3.x/API/Programming-JDBC.md

@@ -207,6 +207,7 @@ The parameter `version` can be used in the url:
 ```java
 String url = "jdbc:iotdb://127.0.0.1:6667?version=V_1_0";
 ```
+When connecting to a cluster via JDBC, configuring the URL with any one node in the cluster is sufficient.
 
 The parameter `version` represents the SQL semantic version used by the client, which is used in order to be compatible with the SQL semantics of `0.12` when upgrading to `0.13`.
 The possible values are: `V_0_12`, `V_0_13`, `V_1_0`.

src/UserGuide/V1.3.x/User-Manual/User-defined-function_apache.md

@@ -98,7 +98,7 @@ CREATE FUNCTION <UDF-NAME> AS <UDF-CLASS-FULL-PATHNAME> (USING URI URI-STRING)
 ####  Method 1: Manually place the jar package
 
 Prepare:   
-When registering using this method, it is necessary to place the JAR package in advance in the `ext/udf` directory of all nodes in the cluster (which can be configured).
+When registering using this method, it is necessary to place the JAR package in advance in the `ext/udf` directory of **all nodes in the cluster** (which can be configured).
 
 Registration statement:
 

src/UserGuide/V1.3.x/User-Manual/User-defined-function_timecho.md

@@ -97,7 +97,7 @@ CREATE FUNCTION <UDF-NAME> AS <UDF-CLASS-FULL-PATHNAME> (USING URI URI-STRING)
 ####  Method 1: Manually place the jar package
 
 Prepare:   
-When registering using this method, it is necessary to place the JAR package in advance in the `ext/udf` directory of all nodes in the cluster (which can be configured).
+When registering using this method, it is necessary to place the JAR package in advance in the `ext/udf` directory of **all nodes in the cluster** (which can be configured).
 
 Registration statement:
 

src/UserGuide/dev-1.3/API/Programming-JDBC.md

@@ -212,6 +212,8 @@ String url = "jdbc:iotdb://127.0.0.1:6667?version=V_1_0";
 The parameter `version` represents the SQL semantic version used by the client, which is used in order to be compatible with the SQL semantics of `0.12` when upgrading to `0.13`.
 The possible values are: `V_0_12`, `V_0_13`, `V_1_0`.
 
+When connecting to a cluster via JDBC, configuring the URL with any one node in the cluster is sufficient.
+
 In addition, IoTDB provides additional interfaces in JDBC for users to read and write the database using different character sets (e.g., GB18030) in the connection.
 The default character set for IoTDB is UTF-8. When users want to use a character set other than UTF-8, they need to specify the charset property in the JDBC connection. For example:
 

src/UserGuide/dev-1.3/User-Manual/User-defined-function_apache.md

@@ -98,7 +98,7 @@ CREATE FUNCTION <UDF-NAME> AS <UDF-CLASS-FULL-PATHNAME> (USING URI URI-STRING)
 ####  Method 1: Manually place the jar package
 
 Prepare:   
-When registering using this method, it is necessary to place the JAR package in advance in the `ext/udf` directory of all nodes in the cluster (which can be configured).
+When registering using this method, it is necessary to place the JAR package in advance in the `ext/udf` directory of **all nodes in the cluster** (which can be configured).
 
 Registration statement:
 

src/UserGuide/dev-1.3/User-Manual/User-defined-function_timecho.md

@@ -97,7 +97,7 @@ CREATE FUNCTION <UDF-NAME> AS <UDF-CLASS-FULL-PATHNAME> (USING URI URI-STRING)
 ####  Method 1: Manually place the jar package
 
 Prepare:   
-When registering using this method, it is necessary to place the JAR package in advance in the `ext/udf` directory of all nodes in the cluster (which can be configured).
+When registering using this method, it is necessary to place the JAR package in advance in the `ext/udf` directory of **all nodes in the cluster** (which can be configured).
 
 Registration statement:
 

src/UserGuide/latest-Table/API/Programming-JDBC_apache.md

@@ -72,6 +72,8 @@ Add the following dependency to your Maven `pom.xml` file:
 String url = "jdbc:iotdb://127.0.0.1:6667?sql_dialect=table";
 ```
 
+When connecting to a cluster via JDBC, configuring the URL with any one node in the cluster is sufficient.
+
 You can find the full example code at [GitHub Repository](https://github.com/apache/iotdb/blob/rc/2.0.1/example/jdbc/src/main/java/org/apache/iotdb/TableModelJDBCExample.java).
 
 Here is an excerpt of the sample code:

src/UserGuide/latest-Table/API/Programming-JDBC_timecho.md

@@ -71,6 +71,7 @@ Add the following dependency to your Maven `pom.xml` file:
 ```Java
 String url = "jdbc:iotdb://127.0.0.1:6667?sql_dialect=table";
 ```
+When connecting to a cluster via JDBC, configuring the URL with any one node in the cluster is sufficient.
 
 You can find the full example code at [GitHub Repository](https://github.com/apache/iotdb/blob/rc/2.0.1/example/jdbc/src/main/java/org/apache/iotdb/TableModelJDBCExample.java).
 

src/UserGuide/latest/API/Programming-JDBC.md

@@ -211,6 +211,8 @@ String url = "jdbc:iotdb://127.0.0.1:6667?version=V_1_0";
 The parameter `version` represents the SQL semantic version used by the client, which is used in order to be compatible with the SQL semantics of `0.12` when upgrading to `0.13`. 
 The possible values are: `V_0_12`, `V_0_13`, `V_1_0`.
 
+When connecting to a cluster via JDBC, configuring the URL with any one node in the cluster is sufficient.
+
 In addition, IoTDB provides additional interfaces in JDBC for users to read and write the database using different character sets (e.g., GB18030) in the connection.
 The default character set for IoTDB is UTF-8. When users want to use a character set other than UTF-8, they need to specify the charset property in the JDBC connection. For example:
 1. Create a connection using the GB18030 charset:

src/UserGuide/latest/User-Manual/User-defined-function_apache.md

@@ -97,7 +97,7 @@ CREATE FUNCTION <UDF-NAME> AS <UDF-CLASS-FULL-PATHNAME> (USING URI URI-STRING)
 ####  Method 1: Manually place the jar package
 
 Prepare:   
-When registering using this method, it is necessary to place the JAR package in advance in the `ext/udf` directory of all nodes in the cluster (which can be configured).
+When registering using this method, it is necessary to place the JAR package in advance in the `ext/udf` directory of **all nodes in the cluster** (which can be configured).
 
 Registration statement:
 

src/UserGuide/latest/User-Manual/User-defined-function_timecho.md

@@ -98,7 +98,7 @@ CREATE FUNCTION <UDF-NAME> AS <UDF-CLASS-FULL-PATHNAME> (USING URI URI-STRING)
 ####  Method 1: Manually place the jar package
 
 Prepare:   
-When registering using this method, it is necessary to place the JAR package in advance in the `ext/udf` directory of all nodes in the cluster (which can be configured).
+When registering using this method, it is necessary to place the JAR package in advance in the `ext/udf` directory of **all nodes in the cluster** (which can be configured).
 
 Registration statement:
 

src/zh/UserGuide/Master/Table/API/Programming-JDBC_apache.md

@@ -75,6 +75,7 @@ IoTDB JDBC接口提供了一种标准的方式来与IoTDB数据库进行交互
 ```Java
 String url = "jdbc:iotdb://127.0.0.1:6667?sql_dialect=table";
 ```
+JDBC 连接集群时，url 配置集群中任意一个节点即可。
 
 JDBC接口示例代码:[src/main/java/org/apache/iotdb/TableModelJDBCExample.java](https://github.com/apache/iotdb/blob/master/example/jdbc/src/main/java/org/apache/iotdb/TableModelJDBCExample.java)
 

src/zh/UserGuide/Master/Table/API/Programming-JDBC_timecho.md

@@ -75,6 +75,7 @@ IoTDB JDBC接口提供了一种标准的方式来与IoTDB数据库进行交互
 ```Java
 String url = "jdbc:iotdb://127.0.0.1:6667?sql_dialect=table";
 ```
+JDBC 连接集群时，url 配置集群中任意一个节点即可。
 
 JDBC接口示例代码:[src/main/java/org/apache/iotdb/TableModelJDBCExample.java](https://github.com/apache/iotdb/blob/master/example/jdbc/src/main/java/org/apache/iotdb/TableModelJDBCExample.java)
 

src/zh/UserGuide/Master/Tree/API/Programming-JDBC.md

@@ -207,6 +207,8 @@ String url = "jdbc:iotdb://127.0.0.1:6667?version=V_1_0";
 ```
 version 表示客户端使用的 SQL 语义版本，用于升级 0.13 时兼容 0.12 的 SQL 语义，可能取值有：`V_0_12`、`V_0_13`、`V_1_0`。
 
+JDBC 连接集群时，url 配置集群中任意一个节点即可。
+
 此外，IoTDB 在 JDBC 中提供了额外的接口，供用户在连接中使用不同的字符集（例如 GB18030）读写数据库。
 IoTDB 默认的字符集为 UTF-8。当用户期望使用 UTF-8 外的字符集时，需要在 JDBC 的连接中，指定 charset 属性。例如：
 1. 使用 GB18030 的 charset 创建连接：

src/zh/UserGuide/Master/Tree/User-Manual/User-defined-function_apache.md

@@ -98,7 +98,7 @@ CREATE FUNCTION <UDF-NAME> AS <UDF-CLASS-FULL-PATHNAME> (USING URI URI-STRING)
 ####  方式一：手动放置jar包
 
 准备工作：  
-使用该种方式注册时，需要提前将 JAR 包放置到集群所有节点的 `ext/udf`目录下（该目录可配置）。
+使用该种方式注册时，需要提前将 JAR 包放置到**集群所有节点**的 `ext/udf`目录下（该目录可配置）。
 
 注册语句：
 

src/zh/UserGuide/Master/Tree/User-Manual/User-defined-function_timecho.md

@@ -99,7 +99,7 @@ CREATE FUNCTION <UDF-NAME> AS <UDF-CLASS-FULL-PATHNAME> (USING URI URI-STRING)
 ####  方式一：手动放置jar包
 
 准备工作：  
-使用该种方式注册时，需要提前将 JAR 包放置到集群所有节点的 `ext/udf`目录下（该目录可配置）。
+使用该种方式注册时，需要提前将 JAR 包放置到**集群所有节点**的 `ext/udf`目录下（该目录可配置）。
 
 注册语句：
 

src/zh/UserGuide/V1.3.x/API/Programming-JDBC.md

@@ -207,6 +207,8 @@ String url = "jdbc:iotdb://127.0.0.1:6667?version=V_1_0";
 ```
 version 表示客户端使用的 SQL 语义版本，用于升级 0.13 时兼容 0.12 的 SQL 语义，可能取值有：`V_0_12`、`V_0_13`、`V_1_0`。
 
+JDBC 连接集群时，url 配置集群中任意一个节点即可。
+
 此外，IoTDB 在 JDBC 中提供了额外的接口，供用户在连接中使用不同的字符集（例如 GB18030）读写数据库。
 IoTDB 默认的字符集为 UTF-8。当用户期望使用 UTF-8 外的字符集时，需要在 JDBC 的连接中，指定 charset 属性。例如：
 1. 使用 GB18030 的 charset 创建连接：

src/zh/UserGuide/V1.3.x/User-Manual/User-defined-function_apache.md

@@ -97,7 +97,7 @@ CREATE FUNCTION <UDF-NAME> AS <UDF-CLASS-FULL-PATHNAME> (USING URI URI-STRING)
 ####  方式一：手动放置jar包
 
 准备工作：  
-使用该种方式注册时，需要提前将 JAR 包放置到集群所有节点的 `ext/udf`目录下（该目录可配置）。
+使用该种方式注册时，需要提前将 JAR 包放置到**集群所有节点**的 `ext/udf`目录下（该目录可配置）。
 
 注册语句：
 

src/zh/UserGuide/V1.3.x/User-Manual/User-defined-function_timecho.md

@@ -98,7 +98,7 @@ CREATE FUNCTION <UDF-NAME> AS <UDF-CLASS-FULL-PATHNAME> (USING URI URI-STRING)
 ####  方式一：手动放置jar包
 
 准备工作：  
-使用该种方式注册时，需要提前将 JAR 包放置到集群所有节点的 `ext/udf`目录下（该目录可配置）。
+使用该种方式注册时，需要提前将 JAR 包放置到**集群所有节点**的 `ext/udf`目录下（该目录可配置）。
 
 注册语句：
 

src/zh/UserGuide/dev-1.3/API/Programming-JDBC.md

@@ -208,6 +208,8 @@ String url = "jdbc:iotdb://127.0.0.1:6667?version=V_1_0";
 ```
 version 表示客户端使用的 SQL 语义版本，用于升级 0.13 时兼容 0.12 的 SQL 语义，可能取值有：`V_0_12`、`V_0_13`、`V_1_0`。
 
+JDBC 连接集群时，url 配置集群中任意一个节点即可。
+
 此外，IoTDB 在 JDBC 中提供了额外的接口，供用户在连接中使用不同的字符集（例如 GB18030）读写数据库。
 IoTDB 默认的字符集为 UTF-8。当用户期望使用 UTF-8 外的字符集时，需要在 JDBC 的连接中，指定 charset 属性。例如：
 1. 使用 GB18030 的 charset 创建连接：

src/zh/UserGuide/dev-1.3/User-Manual/User-defined-function_apache.md

@@ -97,7 +97,7 @@ CREATE FUNCTION <UDF-NAME> AS <UDF-CLASS-FULL-PATHNAME> (USING URI URI-STRING)
 ####  方式一：手动放置jar包
 
 准备工作：  
-使用该种方式注册时，需要提前将 JAR 包放置到集群所有节点的 `ext/udf`目录下（该目录可配置）。
+使用该种方式注册时，需要提前将 JAR 包放置到**集群所有节点**的 `ext/udf`目录下（该目录可配置）。
 
 注册语句：
 

src/zh/UserGuide/dev-1.3/User-Manual/User-defined-function_timecho.md

@@ -98,7 +98,7 @@ CREATE FUNCTION <UDF-NAME> AS <UDF-CLASS-FULL-PATHNAME> (USING URI URI-STRING)
 ####  方式一：手动放置jar包
 
 准备工作：  
-使用该种方式注册时，需要提前将 JAR 包放置到集群所有节点的 `ext/udf`目录下（该目录可配置）。
+使用该种方式注册时，需要提前将 JAR 包放置到**集群所有节点**的 `ext/udf`目录下（该目录可配置）。
 
 注册语句：
 

src/zh/UserGuide/latest-Table/API/Programming-JDBC_apache.md

@@ -75,6 +75,7 @@ IoTDB JDBC接口提供了一种标准的方式来与IoTDB数据库进行交互
 ```Java
 String url = "jdbc:iotdb://127.0.0.1:6667?sql_dialect=table";
 ```
+JDBC 连接集群时，url 配置集群中任意一个节点即可。
 
 JDBC接口示例代码:[src/main/java/org/apache/iotdb/TableModelJDBCExample.java](https://github.com/apache/iotdb/blob/rc/2.0.1/example/jdbc/src/main/java/org/apache/iotdb/TableModelJDBCExample.java)
 

src/zh/UserGuide/latest-Table/API/Programming-JDBC_timecho.md

@@ -75,6 +75,7 @@ IoTDB JDBC接口提供了一种标准的方式来与IoTDB数据库进行交互
 ```Java
 String url = "jdbc:iotdb://127.0.0.1:6667?sql_dialect=table";
 ```
+JDBC 连接集群时，url 配置集群中任意一个节点即可。
 
 JDBC接口示例代码:[src/main/java/org/apache/iotdb/TableModelJDBCExample.java](https://github.com/apache/iotdb/blob/rc/2.0.1/example/jdbc/src/main/java/org/apache/iotdb/TableModelJDBCExample.java)
 

src/zh/UserGuide/latest/API/Programming-JDBC.md

@@ -208,6 +208,8 @@ String url = "jdbc:iotdb://127.0.0.1:6667?version=V_1_0";
 ```
 version 表示客户端使用的 SQL 语义版本，用于升级 0.13 时兼容 0.12 的 SQL 语义，可能取值有：`V_0_12`、`V_0_13`、`V_1_0`。
 
+JDBC 连接集群时，url 配置集群中任意一个节点即可。
+
 此外，IoTDB 在 JDBC 中提供了额外的接口，供用户在连接中使用不同的字符集（例如 GB18030）读写数据库。
 IoTDB 默认的字符集为 UTF-8。当用户期望使用 UTF-8 外的字符集时，需要在 JDBC 的连接中，指定 charset 属性。例如：
 1. 使用 GB18030 的 charset 创建连接：

src/zh/UserGuide/latest/User-Manual/User-defined-function_apache.md

@@ -98,7 +98,7 @@ CREATE FUNCTION <UDF-NAME> AS <UDF-CLASS-FULL-PATHNAME> (USING URI URI-STRING)
 ####  方式一：手动放置jar包
 
 准备工作：  
-使用该种方式注册时，需要提前将 JAR 包放置到集群所有节点的 `ext/udf`目录下（该目录可配置）。
+使用该种方式注册时，需要提前将 JAR 包放置到**集群所有节点**的 `ext/udf`目录下（该目录可配置）。
 
 注册语句：
 

src/zh/UserGuide/latest/User-Manual/User-defined-function_timecho.md

@@ -99,7 +99,7 @@ CREATE FUNCTION <UDF-NAME> AS <UDF-CLASS-FULL-PATHNAME> (USING URI URI-STRING)
 ####  方式一：手动放置jar包
 
 准备工作：  
-使用该种方式注册时，需要提前将 JAR 包放置到集群所有节点的 `ext/udf`目录下（该目录可配置）。
+使用该种方式注册时，需要提前将 JAR 包放置到**集群所有节点**的 `ext/udf`目录下（该目录可配置）。
 
 注册语句：