Merge branch 'apache:master' into master

Author: KassieZ

blog/arrow-flight-sql-in-apache-doris-for-10x-faster-data-transfer.md

@@ -99,6 +99,10 @@ Configure parameters for Doris frontend (FE) and backend (BE):
 
 - In `be/conf/be.conf`, set `arrow_flight_sql_port ` to an available port, such as 9091.
 
+`Note: The arrow_flight_sql_port port number configured in fe.conf and be.conf is different`
+
+After modifying the configuration and restarting the cluster, searching for `Arrow Flight SQL service is started` in the fe/log/fe.log file indicates that the Arrow Flight Server of FE has been successfully started; searching for `Arrow Flight Service bind to host` in the be/log/be.INFO file indicates that the Arrow Flight Server of BE has been successfully started.
+
 Suppose that the Arrow Flight SQL services for the Doris instance will run on ports 9090 and 9091 for FE and BE respectively, and the Doris username/password is "user" and "pass", the connection process would be:
 
 ```C++

docs/admin-manual/auth/authorization/data.md

@@ -37,8 +37,8 @@ Equivalent to automatically adding the predicate set in the Row Policy for users
 Row Policy cannot be set for default users root and admin.
 
 ### Related Commands
-- View Row Permission Policies [SHOW ROW POLICY](../../../sql-manual/sql-statements/Show-Statements/SHOW-POLICY.md)
-- Create Row Permission Policy [CREATE ROW POLICY](../../../sql-manual/sql-statements/Data-Definition-Statements/Create/CREATE-POLICY.md)
+- View Row Permission Policies [SHOW ROW POLICY](../../../sql-manual/sql-statements/data-governance/SHOW-ROW-POLICY)
+- Create Row Permission Policy [CREATE ROW POLICY](../../../sql-manual/sql-statements/data-governance/CREATE-ROW-POLICY)
 
 ### Row Permission Example
 1. Restrict the test user to only query data in table1 where c1='a'

docs/admin-manual/auth/user-privilege.md

@@ -96,8 +96,8 @@ The default role cannot be deleted or assigned to others. When a user is deleted
 1. Create users: [CREATE USER](../../sql-manual/sql-statements/account-management/CREATE-USER)
 2. Alter users: [ALTER USER](../../sql-manual/sql-statements/account-management/ALTER-USER)
 3. Delete users: [DROP USER](../../sql-manual/sql-statements/account-management/DROP-USER)
-4. Authorization/Assign roles: [GRANT](../../sql-manual/sql-reference/Account-Management-Statements/GRANT.md)
-5. Withdrawal/REVOKE roles: [REVOKE](../../sql-manual/sql-reference/Account-Management-Statements/REVOKE.md)
+4. Authorization/Assign roles: [GRANT](../../sql-manual/sql-statements/account-management/GRANT-TO)
+5. Withdrawal/REVOKE roles: [REVOKE](../../sql-manual/sql-statements/account-management/REVOKE-FROM)
 6. Create role: [CREATE ROLE](../../sql-manual/sql-statements/account-management/CREATE-ROLE)
 7. Delete roles: [DROP ROLE](../../sql-manual/sql-statements/account-management/DROP-ROLE)
 8. View current user privileges: [SHOW GRANTS](../../sql-manual/sql-statements/account-management/SHOW-GRANTS)
@@ -293,4 +293,4 @@ Here are some usage scenarios of Doris privilege system.
 
 ## More help
 
-For more detailed syntax and best practices for permission management use, please refer to the [GRANTS](../../sql-manual/sql-reference/Account-Management-Statements/GRANT.md) command manual. Enter `HELP GRANTS` at the command line of the MySql client for more help information.
+For more detailed syntax and best practices for permission management use, please refer to the [GRANTS](../../sql-manual/sql-statements/account-management/GRANT-TO) command manual. Enter `HELP GRANTS` at the command line of the MySql client for more help information.

docs/admin-manual/config/fe-config-template.md

@@ -48,7 +48,7 @@ There are two ways to view the configuration items of FE:
 
 2. View by command
 
-    After the FE is started, you can view the configuration items of the FE in the MySQL client with the following command,Concrete language law reference [ADMIN-SHOW-CONFIG](../../sql-manual/sql-reference/Database-Administration-Statements/ADMIN-SHOW-CONFIG.md):
+    After the FE is started, you can view the configuration items of the FE in the MySQL client with the following command,Concrete language law reference [ADMIN-SHOW-CONFIG](../../sql-manual/sql-statements/cluster-management/instance-management/SHOW-FRONTEND-CONFIG):
 
     `ADMIN SHOW FRONTEND CONFIG;`
 
@@ -1519,7 +1519,7 @@ For some high-frequency load work, such as: INSERT, STREAMING LOAD, ROUTINE_LOAD
 
 #### `label_clean_interval_second`
 
-Default：1 * 3600  (1 hour)
+Default: 1 * 3600  (1 hour)
 
 Load label cleaner will run every *label_clean_interval_second* to clean the outdated jobs.
 

docs/admin-manual/workload-management/compute-group.md

@@ -62,8 +62,8 @@ SHOW COMPUTE GROUPS;
 
 ## Adding Compute Groups
 
-Managing compute groups requires `OPERATOR` privilege, which controls node management permissions. For more details, please refer to [Privilege Management](../sql-manual/sql-statements/Account-Management-Statements/GRANT.md). By default, only the root account has the `OPERATOR` privilege, but it can be granted to other accounts using the `GRANT` command.
-To add a BE and assign it to a compute group, use the [Add BE](../sql-manual/sql-statements/Cluster-Management-Statements/ALTER-SYSTEM-ADD-BACKEND.md) command. For example:
+Managing compute groups requires `OPERATOR` privilege, which controls node management permissions. For more details, please refer to [Privilege Management](../../sql-manual/sql-statements/account-management/GRANT-TO). By default, only the root account has the `OPERATOR` privilege, but it can be granted to other accounts using the `GRANT` command.
+To add a BE and assign it to a compute group, use the [Add BE](../../sql-manual/sql-statements/cluster-management/instance-management/ADD-BACKEND) command. For example:
 
 ```sql
 ALTER SYSTEM ADD BACKEND 'host:9050' PROPERTIES ("tag.compute_group_name" = "new_group");

docs/data-operate/import/file-format/csv.md

@@ -34,8 +34,8 @@ Doris supports the following methods to load CSV format data:
 - [Broker Load](../import-way/broker-load-manual)
 - [Routine Load](../import-way/routine-load-manual)
 - [MySQL Load](../import-way/mysql-load-manual)
-- [INSERT INTO FROM S3 TVF](../../sql-manual/sql-functions/table-valued-functions/s3)
-- [INSERT INTO FROM HDFS TVF](../../sql-manual/sql-functions/table-valued-functions/hdfs)
+- [INSERT INTO FROM S3 TVF](../../../sql-manual/sql-functions/table-valued-functions/s3)
+- [INSERT INTO FROM HDFS TVF](../../../sql-manual/sql-functions/table-valued-functions/hdfs)
 
 ## Parameter Configuration
 

docs/data-operate/import/file-format/json.md

@@ -33,8 +33,8 @@ The following loading methods support JSON format data:
 - [Stream Load](../import-way/stream-load-manual.md)
 - [Broker Load](../import-way/broker-load-manual.md)
 - [Routine Load](../import-way/routine-load-manual.md)
-- [INSERT INTO FROM S3 TVF](../../sql-manual/sql-functions/table-valued-functions/s3)
-- [INSERT INTO FROM HDFS TVF](../../sql-manual/sql-functions/table-valued-functions/hdfs)
+- [INSERT INTO FROM S3 TVF](../../../sql-manual/sql-functions/table-valued-functions/s3)
+- [INSERT INTO FROM HDFS TVF](../../../sql-manual/sql-functions/table-valued-functions/hdfs)
 
 ## Supported JSON Formats
 

docs/data-operate/import/import-way/insert-into-manual.md

@@ -314,7 +314,7 @@ PROPERTIES (
 );
 ```
 
-2. For detailed instructions on creating Doris tables, please refer to [CREATE TABLE](../../../sql-manual/sql-statements/Data-Definition-Statements/Create/CREATE-TABLE/).
+2. For detailed instructions on creating Doris tables, please refer to [CREATE TABLE](../../../sql-manual/sql-statements/table-and-view/table/CREATE-TABLE).
 
 3. Importing data (from the `hive.db1.source_tbl` table into the `target_tbl` table).
 

docs/db-connect/arrow-flight-sql-connect.md

@@ -68,7 +68,9 @@ Modify the configuration parameters of Doris FE and BE:
 - Modify arrow_flight_sql_port in fe/conf/fe.conf to an available port, such as 9090.
 - Modify arrow_flight_sql_port in be/conf/be.conf to an available port, such as 9091.
 
-`Note: arrow_flight_sql_port configured in fe.conf and be.conf are different`
+`Note: The arrow_flight_sql_port port number configured in fe.conf and be.conf is different`
+
+After modifying the configuration and restarting the cluster, searching for `Arrow Flight SQL service is started` in the fe/log/fe.log file indicates that the Arrow Flight Server of FE has been successfully started; searching for `Arrow Flight Service bind to host` in the be/log/be.INFO file indicates that the Arrow Flight Server of BE has been successfully started.
 
 Assuming that the Arrow Flight SQL services of FE and BE in the Doris instance will run on ports 9090 and 9091 respectively, and the Doris username/password is "user"/"pass", the connection process is as follows:
 
@@ -281,7 +283,7 @@ The open source JDBC driver of Arrow Flight SQL protocol is compatible with the
 POM dependency:
 ```Java
 <properties>
-    <arrow.version>15.0.1</arrow.version>
+    <arrow.version>17.0.0</arrow.version>
 </properties>
 <dependencies>
     <dependency>

docs/ecosystem/hive-bitmap-udf.md

@@ -125,7 +125,7 @@ CREATE TABLE IF NOT EXISTS `test`.`hive_bitmap_table`(
 ) stored as textfile 
 ```
 
-2. [Creating a Catalog in Doris](../lakehouse/datalake-analytics/hive.md)
+2. [Creating a Catalog in Doris](../lakehouse/catalogs/hive-catalog)
 
 ```sql
 CREATE CATALOG hive PROPERTIES (

docs/ecosystem/hive-hll-udf.md

@@ -181,7 +181,7 @@ CREATE TABLE IF NOT EXISTS `hive_hll_table`(
 -- then reuse the previous steps to insert data from a normal table into it using the to_hll function
 ```
 
-2. [Create a Doris catalog](../lakehouse/datalake-analytics/hive.md)
+2. [Create a Doris catalog](../lakehouse/catalogs/hive-catalog)
 
 ```sql
 CREATE CATALOG hive PROPERTIES (

docs/install/deploy-on-kubernetes/integrated-storage-compute/install-config-cluster.md

@@ -725,3 +725,29 @@ For more details on creating users, setting passwords, and granting permissions,
 :::tip Tip  
 After setting the root password and configuring the new username and password for managing nodes after deployment, the existing services will be restarted once in a rolling manner.  
 :::
+
+## Automatic Service Restart on Configuration Changes
+Doris specifies startup parameters through configuration files. While most parameters can be modified through web interfaces and take effect immediately, certain parameters requiring service restart can now be automatically handled through Doris Operator's restart capability introduced in version 25.1.0.    
+To enable this functionality in a `DorisCluster` resource, configure:
+```yaml
+spec:
+  enableRestartWhenConfigChange: true
+```
+When this configuration is present, Doris Operator will:
+1. Monitor changes to cluster startup configurations (mounted via ConfigMap, see [Customizing Startup Configurations](#custom-startup-configuration)).
+2. Automatically restart affected services when configurations change.
+
+### Example Usage
+Support configmap monitoring and restart for FE and BE, Use FE usage as example.
+1. Sample DorisCluster deployment specification:
+    ```yaml
+    spec:
+      enableRestartWhenConfigChange: true
+      feSpec:
+        image: apache/doris:fe-2.1.8
+        replicas: 1
+        configMapInfo:
+        configMapName: fe-configmap
+    ```
+2. Update FE service configurations.  
+   When modifying values under the `fe.conf` key in the fe-configmap ConfigMap (containing FE service configurations), Doris Operator will automatically perform a rolling restart of FE services to apply changes.

docs/query-acceleration/materialized-view/async-materialized-view/faq.md

@@ -88,7 +88,7 @@ Unable to find a suitable base table for partitioning
 
 This error typically indicates that the SQL definition of the materialized view and the choice of partitioning fields do not allow incremental partition updates, resulting in an error during the creation of the partitioned materialized view.
 
-- For incremental partition updates, the materialized view's SQL definition and partitioning field selection must meet specific requirements. See [Materialized View Refresh Modes](../../../sql-manual/sql-statements/Data-Definition-Statements/Create/CREATE-ASYNC-MATERIALIZED-VIEW#refreshmethod) for details.
+- For incremental partition updates, the materialized view's SQL definition and partitioning field selection must meet specific requirements. See [Materialized View Refresh Modes](../../../sql-manual/sql-statements/table-and-view/async-materialized-view/CREATE-ASYNC-MATERIALIZED-VIEW#optional-parameters) for details.
 
 - The latest code can indicate the reason for partition build failure, with error summaries and descriptions provided in Appendix 2.
 

docs/query-acceleration/materialized-view/async-materialized-view/use-guide.md

@@ -52,7 +52,7 @@ When the following conditions are met, it is recommended to create partitioned m
 
 - The tables used by the materialized view, except for the partitioned table, do not change frequently.
 
-- The definition SQL of the materialized view and the partition field meet the requirements of partition derivation, that is, meet the requirements of partition incremental update. Detailed requirements can be found in [CREATE-ASYNC-MATERIALIZED-VIEW](../../../sql-manual/sql-statements/Data-Definition-Statements/Create/CREATE-ASYNC-MATERIALIZED-VIEW/#refreshmethod)
+- The definition SQL of the materialized view and the partition field meet the requirements of partition derivation, that is, meet the requirements of partition incremental update. Detailed requirements can be found in [CREATE-ASYNC-MATERIALIZED-VIEW](../../../sql-manual/sql-statements/table-and-view/async-materialized-view/CREATE-ASYNC-MATERIALIZED-VIEW#optional-parameters)
 
 - The number of partitions in the materialized view is not large, as too many partitions will lead to excessively long partition materialized view construction time.
 
@@ -62,7 +62,7 @@ If partitioned materialized views cannot be constructed, you can consider choosi
 
 ## Common Usage of Partitioned Materialized Views
 
-When the materialized view's base table data volume is large and the base table is a partitioned table, if the materialized view's definition SQL and partition fields meet the requirements of partition derivation, this scenario is suitable for building partitioned materialized views. For detailed requirements of partition derivation, refer to [CREATE-ASYNC-MATERIALIZED-VIEW](../../../sql-manual/sql-statements/Data-Definition-Statements/Create/CREATE-ASYNC-MATERIALIZED-VIEW/#refreshmethod) and [Async Materialized View FAQ Building Question 12](../../../query-acceleration/materialized-view/async-materialized-view/faq#q12-error-when-building-partitioned-materialized-view).
+When the materialized view's base table data volume is large and the base table is a partitioned table, if the materialized view's definition SQL and partition fields meet the requirements of partition derivation, this scenario is suitable for building partitioned materialized views. For detailed requirements of partition derivation, refer to [CREATE-ASYNC-MATERIALIZED-VIEW](../../../sql-manual/sql-statements/table-and-view/async-materialized-view/CREATE-ASYNC-MATERIALIZED-VIEW#optional-parameters) and [Async Materialized View FAQ Building Question 12](../../../query-acceleration/materialized-view/async-materialized-view/faq#q12-error-when-building-partitioned-materialized-view).
 
 The materialized view's partitions are created following the base table's partition mapping, generally having a 1:1 or 1:n relationship with the base table's partitions.
 

docs/query-data/udf/java-user-defined-function.md

@@ -377,7 +377,7 @@ UDTF is supported starting from Doris version 3.0.
     }
     ```
 
-2. Register and create the Java-UDTF function in Doris. Two UDTF functions will be registered. Table functions in Doris may exhibit different behaviors due to the `_outer` suffix. For more details, refer to [OUTER combinator](../../sql-manual/sql-functions/table-functions/explode-numbers-outer.md).
+2. Register and create the Java-UDTF function in Doris. Two UDTF functions will be registered. Table functions in Doris may exhibit different behaviors due to the `_outer` suffix. For more details, refer to [OUTER combinator](../../sql-manual/sql-functions/table-functions/explode-numbers).
 For more syntax details, please refer to [CREATE FUNCTION](../../sql-manual/sql-statements/function/CREATE-FUNCTION).
 
     ```sql