This is an automated email from the ASF dual-hosted git repository.

luzhijing pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/doris-website.git


The following commit(s) were added to refs/heads/master by this push:
     new 54fdf6ea47 [docs](release) Add hyperlink of 2.1.3 release note (#676)
54fdf6ea47 is described below

commit 54fdf6ea4708040fd19fbe2236d456c701e4629b
Author: KassieZ <139741991+kass...@users.noreply.github.com>
AuthorDate: Thu May 23 13:12:09 2024 +0700

    [docs](release) Add hyperlink of 2.1.3 release note (#676)
---
 blog/release-note-2.1.3.md                         | 12 ++--
 docs/releasenotes/release-2.1.3.md                 | 74 +++++++++++-----------
 .../current/releasenotes/release-2.1.3.md          | 14 ++--
 .../version-2.1/releasenotes/release-2.1.3.md      | 12 ++--
 .../version-2.1/releasenotes/release-2.1.3.md      | 74 +++++++++++-----------
 5 files changed, 93 insertions(+), 93 deletions(-)

diff --git a/blog/release-note-2.1.3.md b/blog/release-note-2.1.3.md
index 21ecf91815..de8079b7ea 100644
--- a/blog/release-note-2.1.3.md
+++ b/blog/release-note-2.1.3.md
@@ -126,23 +126,23 @@ Supporting the decimal256 type in row-based storage 
extends the system's ability
 
 **1. Authorization**
 
-- **Grant_priv permission changes**: `Grant_priv` can no longer be arbitrarily 
granted. When performing a `GRANT` operation, the user not only needs to have 
`Grant_priv` but also the permissions to be granted. For example, to grant 
`SELECT` permission on `table1`, the user needs both `GRANT` permission and 
`SELECT` permission on `table1`, enhancing security and consistency in 
permission management. #32825
+- **Grant_priv permission changes**: `Grant_priv` can no longer be arbitrarily 
granted. When performing a `GRANT` operation, the user not only needs to have 
`Grant_priv` but also the permissions to be granted. For example, to grant 
`SELECT` permission on `table1`, the user needs both `GRANT` permission and 
`SELECT` permission on `table1`, enhancing security and consistency in 
permission management.
 
-- **Workload group and resource usage_priv**: `Usage_priv` for Workload Group 
and Resource is no longer global but limited to Resource and Workload Group, 
making permission granting and usage more specific. #32907
+- **Workload group and resource usage_priv**: `Usage_priv` for Workload Group 
and Resource is no longer global but limited to Resource and Workload Group, 
making permission granting and usage more specific.
 
-- **Authorization for operations**: Operations that were previously 
unauthorized now have corresponding authorizations for more detailed and 
comprehensive operational permission control. #33347
+- **Authorization for operations**: Operations that were previously 
unauthorized now have corresponding authorizations for more detailed and 
comprehensive operational permission control.
 
 **2. LOG directory configuration**
 
-The log directory configuration for FE and BE now uniformly uses the `LOG_DIR` 
environment variable. All other different types of logs will be stored with 
`LOG_DIR` as the root directory. To maintain compatibility between versions, 
the previous configuration item `sys_log_dir` can still be used. #32933
+The log directory configuration for FE and BE now uniformly uses the `LOG_DIR` 
environment variable. All other different types of logs will be stored with 
`LOG_DIR` as the root directory. To maintain compatibility between versions, 
the previous configuration item `sys_log_dir` can still be used.
 
 **3. S3 Table Function (TVF)**
 
-Due to issues with correctly recognizing or processing S3 URLs in certain 
cases, the parsing logic for object storage paths has been refactored. For file 
paths in S3 table functions, the `force_parsing_by_standard_uri` parameter 
needs to be passed to ensure correct parsing. #33858
+Due to issues with correctly recognizing or processing S3 URLs in certain 
cases, the parsing logic for object storage paths has been refactored. For file 
paths in S3 table functions, the `force_parsing_by_standard_uri` parameter 
needs to be passed to ensure correct parsing.
 
 ## Upgrade Issues
 
-Since many users use certain keywords as column names or attribute values, the 
following keywords have been set as non-reserved, allowing users to use them as 
identifiers. #34613
+Since many users use certain keywords as column names or attribute values, the 
following keywords have been set as non-reserved, allowing users to use them as 
identifiers.
 
 ## Bug Fixes
 
diff --git a/docs/releasenotes/release-2.1.3.md 
b/docs/releasenotes/release-2.1.3.md
index b53286746e..e88ec3e94f 100644
--- a/docs/releasenotes/release-2.1.3.md
+++ b/docs/releasenotes/release-2.1.3.md
@@ -42,103 +42,103 @@ Please refer: 
[https://doris.apache.org/docs/lakehouse/datalake-building/hive-bu
 
 **2. Support building new asynchronous materialized views on top of existing 
ones**
 
-Users can create new asynchronous materialized views on top of existing ones, 
directly reusing pre-computed intermediate results for data processing. This 
simplifies complex aggregation and computation operations, reducing resource 
consumption and maintenance costs while further accelerating query performance 
and improving data availability.
+Users can create new asynchronous materialized views on top of existing ones, 
directly reusing pre-computed intermediate results for data processing. This 
simplifies complex aggregation and computation operations, reducing resource 
consumption and maintenance costs while further accelerating query performance 
and improving data availability. 
[#32984](https://github.com/apache/doris/pull/32984)
 
 **3. Support rewriting through nested materialized views**
 
-Materialized View (MV) is a database object used to store query results. Now, 
Apache Doris supports rewriting through nested materialized views, which helps 
optimize query performance.
+Materialized View (MV) is a database object used to store query results. Now, 
Apache Doris supports rewriting through nested materialized views, which helps 
optimize query performance. [#33362](https://github.com/apache/doris/pull/33362)
 
 **4. New `SHOW VIEWS` statement**
 
-The `SHOW VIEWS` statement can be used to query views in the database, 
facilitating better management and understanding of view objects in the 
database.
+The `SHOW VIEWS` statement can be used to query views in the database, 
facilitating better management and understanding of view objects in the 
database. [#32358](https://github.com/apache/doris/pull/32358)
 
 **5. Workload Group supports binding to specific BE nodes**
 
-Workload Group can be bound to specific BE nodes, enabling more refined 
control over query execution to optimize resource usage and improve performance.
+Workload Group can be bound to specific BE nodes, enabling more refined 
control over query execution to optimize resource usage and improve 
performance. [#32874](https://github.com/apache/doris/pull/32874)
 
 **6. Broker Load supports compressed JSON format**
 
-Broker Load now supports importing compressed JSON format data, significantly 
reducing bandwidth requirements for data transmission and accelerating data 
import performance.
+Broker Load now supports importing compressed JSON format data, significantly 
reducing bandwidth requirements for data transmission and accelerating data 
import performance. [#30809](https://github.com/apache/doris/pull/30809)
 
 **7. TRUNCATE Function can use columns as scale parameters**
 
-The TRUNCATE function can now accept columns as scale parameters, providing 
more flexibility when processing numerical data.
+The TRUNCATE function can now accept columns as scale parameters, providing 
more flexibility when processing numerical data. 
[#32746](https://github.com/apache/doris/pull/32746)
 
 **8. Add new functions `uuid_to_int` and `int_to_uuid`**
 
-These two functions allow users to convert between UUID and integer, 
significantly helping in scenarios that require handling UUID data.
+These two functions allow users to convert between UUID and integer, 
significantly helping in scenarios that require handling UUID data. 
[#33005](https://github.com/apache/doris/pull/33005)
 
 **9. Add `bypass_workload_group` session variable to bypass query queue**
 
-The `bypass_workload_group` session variable allows certain queries to bypass 
the Workload Group queue and execute directly, which is useful for handling 
critical queries that require quick responses.
+The `bypass_workload_group` session variable allows certain queries to bypass 
the Workload Group queue and execute directly, which is useful for handling 
critical queries that require quick responses. 
[#33101](https://github.com/apache/doris/pull/33101)
 
 **10. Add strcmp function**
 
-The strcmp function compares two strings and returns their comparison result, 
simplifying text data processing.
+The strcmp function compares two strings and returns their comparison result, 
simplifying text data processing. 
[#33272](https://github.com/apache/doris/pull/33272)
 
 **11. Support HLL functions `hll_from_base64` and `hll_to_base64`**
 
-HyperLogLog (HLL) is an algorithm for cardinality estimation. These two 
functions allow users to decode HLL data from a Base64-encoded string or encode 
HLL data as a Base64 string, which is very useful for storing and transmitting 
HLL data.
+HyperLogLog (HLL) is an algorithm for cardinality estimation. These two 
functions allow users to decode HLL data from a Base64-encoded string or encode 
HLL data as a Base64 string, which is very useful for storing and transmitting 
HLL data. [#32089](https://github.com/apache/doris/pull/32089)
 
 ## Optimization and Improvements
 
 **1. Replace SipHash with XXHash to improve shuffle performance**
 
-Both SipHash and XXHash are hashing functions, but XXHash may provide faster 
hashing speeds and better performance in certain scenarios. This optimization 
aims to improve performance during data shuffling by adopting XXHash.
+Both SipHash and XXHash are hashing functions, but XXHash may provide faster 
hashing speeds and better performance in certain scenarios. This optimization 
aims to improve performance during data shuffling by adopting XXHash. 
[#32919](https://github.com/apache/doris/pull/32919)
 
 **2. Asynchronous materialized views support NULL partition columns in OLAP 
tables**
 
-This enhancement allows asynchronous materialized views to support NULL 
partition columns in OLAP tables, enhancing data processing flexibility.
+This enhancement allows asynchronous materialized views to support NULL 
partition columns in OLAP tables, enhancing data processing 
flexibility.[#32698](https://github.com/apache/doris/pull/32698)
 
 **3. Limit maximum string length to 1024 when collecting column statistics to 
control BE memory usage**
 
-Limiting the string length when collecting column statistics prevents 
excessive data from consuming too much BE memory, helping maintain system 
stability and performance.
+Limiting the string length when collecting column statistics prevents 
excessive data from consuming too much BE memory, helping maintain system 
stability and performance. [#32470](https://github.com/apache/doris/pull/32470)
 
 **4. Support dynamic deletion of Bitmap cache to improve performance**
 
-Dynamically deleting no longer needed Bitmap Cache can free up memory and 
improve system performance.
+Dynamically deleting no longer needed Bitmap Cache can free up memory and 
improve system performance. [#32991](https://github.com/apache/doris/pull/32991)
 
 **5. Reduce memory usage during ALTER operations**
 
-Reducing memory usage during ALTER operations improves the efficiency of 
system resource utilization.
+Reducing memory usage during ALTER operations improves the efficiency of 
system resource utilization. 
[#33474](https://github.com/apache/doris/pull/33474)
 
 **6. Support constant folding for complex types**
 
-Supports constant folding for Array/Map/Struct complex types.
+Supports constant folding for Array/Map/Struct complex 
types.[#32867](https://github.com/apache/doris/pull/32867)
 
 **7. Add support for Variant type in Aggregate Key Model**
 
-The Variant data type can store multiple data types. This optimization allows 
aggregation operations on Variant type data, enhancing the flexibility of 
semi-structured data analysis.
+The Variant data type can store multiple data types. This optimization allows 
aggregation operations on Variant type data, enhancing the flexibility of 
semi-structured data analysis. 
[#33493](https://github.com/apache/doris/pull/33493)
 
-**8. Support new inverted index format in CCR**
+**8. Support new inverted index format in CCR** 
[#33415](https://github.com/apache/doris/pull/33415)
 
-**9. Optimize rewriting performance for nested materialized views**
+**9. Optimize rewriting performance for nested materialized views** 
[#34127](https://github.com/apache/doris/pull/34127)
 
 **10. Support decimal256 type in row-based storage format**
 
-Supporting the decimal256 type in row-based storage extends the system's 
ability to handle high-precision numerical data.
+Supporting the decimal256 type in row-based storage extends the system's 
ability to handle high-precision numerical data. 
[#34887](https://github.com/apache/doris/pull/34887)
 
 ## Behavioral Changes
 
 **1. Authorization**
 
-- **Grant_priv permission changes**: `Grant_priv` can no longer be arbitrarily 
granted. When performing a `GRANT` operation, the user not only needs to have 
`Grant_priv` but also the permissions to be granted. For example, to grant 
`SELECT` permission on `table1`, the user needs both `GRANT` permission and 
`SELECT` permission on `table1`, enhancing security and consistency in 
permission management. #32825
+- **Grant_priv permission changes**: `Grant_priv` can no longer be arbitrarily 
granted. When performing a `GRANT` operation, the user not only needs to have 
`Grant_priv` but also the permissions to be granted. For example, to grant 
`SELECT` permission on `table1`, the user needs both `GRANT` permission and 
`SELECT` permission on `table1`, enhancing security and consistency in 
permission management. [#32825](https://github.com/apache/doris/pull/32825)
 
-- **Workload group and resource usage_priv**: `Usage_priv` for Workload Group 
and Resource is no longer global but limited to Resource and Workload Group, 
making permission granting and usage more specific. #32907
+- **Workload group and resource usage_priv**: `Usage_priv` for Workload Group 
and Resource is no longer global but limited to Resource and Workload Group, 
making permission granting and usage more specific. 
[#32907](https://github.com/apache/doris/pull/32907)
 
-- **Authorization for operations**: Operations that were previously 
unauthorized now have corresponding authorizations for more detailed and 
comprehensive operational permission control. #33347
+- **Authorization for operations**: Operations that were previously 
unauthorized now have corresponding authorizations for more detailed and 
comprehensive operational permission control. 
[#33347](https://github.com/apache/doris/pull/33347)
 
 **2. LOG directory configuration**
 
-The log directory configuration for FE and BE now uniformly uses the `LOG_DIR` 
environment variable. All other different types of logs will be stored with 
`LOG_DIR` as the root directory. To maintain compatibility between versions, 
the previous configuration item `sys_log_dir` can still be used. #32933
+The log directory configuration for FE and BE now uniformly uses the `LOG_DIR` 
environment variable. All other different types of logs will be stored with 
`LOG_DIR` as the root directory. To maintain compatibility between versions, 
the previous configuration item `sys_log_dir` can still be used. 
[#32933](https://github.com/apache/doris/pull/32933)
 
 **3. S3 Table Function (TVF)**
 
-Due to issues with correctly recognizing or processing S3 URLs in certain 
cases, the parsing logic for object storage paths has been refactored. For file 
paths in S3 table functions, the `force_parsing_by_standard_uri` parameter 
needs to be passed to ensure correct parsing. #33858
+Due to issues with correctly recognizing or processing S3 URLs in certain 
cases, the parsing logic for object storage paths has been refactored. For file 
paths in S3 table functions, the `force_parsing_by_standard_uri` parameter 
needs to be passed to ensure correct parsing. 
[#33858](https://github.com/apache/doris/pull/33858)
 
 ## Upgrade Issues
 
-Since many users use certain keywords as column names or attribute values, the 
following keywords have been set as non-reserved, allowing users to use them as 
identifiers. #34613
+Since many users use certain keywords as column names or attribute values, the 
following keywords have been set as non-reserved, allowing users to use them as 
identifiers. [#34613](https://github.com/apache/doris/pull/34613)
 
 ## Bug Fixes
 
@@ -148,44 +148,44 @@ Resolved the no data error that could occur when reading 
Hive tables on Tencent
 
 **2. Fix incorrect results returned by `milliseconds_diff` function**
 
-Fixed an issue where the `milliseconds_diff` function returned incorrect 
results in some cases, ensuring the accuracy of time difference calculations.
+Fixed an issue where the `milliseconds_diff` function returned incorrect 
results in some cases, ensuring the accuracy of time difference calculations. 
[#32897](https://github.com/apache/doris/pull/32897)
 
 **3. User-defined variables should be rorwarded to the Master node**
 
-Ensured that user-defined variables are correctly passed to the Master node 
for consistency and correct execution logic across the entire system.
+Ensured that user-defined variables are correctly passed to the Master node 
for consistency and correct execution logic across the entire system. 
[#33013]https://github.com/apache/doris/pull/33013
 
 **4. Fix Schema Change issues when adding complex type columns**
 
-Resolved Schema Change issues that could arise when adding complex type 
columns, ensuring the correctness of Schema Changes.
+Resolved Schema Change issues that could arise when adding complex type 
columns, ensuring the correctness of Schema Changes. 
[#31824](https://github.com/apache/doris/pull/31824)
 
 **5. Fix data loss issue in Routine Load when FE Master node changes**
 
-`Routine Load` is often used to subscribe to Kafka message queues. This fix 
addresses potential data loss issues that may occur during FE Master node 
changes.
+`Routine Load` is often used to subscribe to Kafka message queues. This fix 
addresses potential data loss issues that may occur during FE Master node 
changes. [#33678](https://github.com/apache/doris/pull/33678)
 
 **6. Fix Routine Load failure when Workload Group cannot be found**
 
-Resolved an issue where `Routine Load` would fail if the specified Workload 
Group could not be found.
+Resolved an issue where `Routine Load` would fail if the specified Workload 
Group could not be found. [#33596](https://github.com/apache/doris/pull/33596)
 
 **7. Support column string64 to avoid join failures when string size overflows 
unit32**
 
-In some cases, string sizes may exceed the unit32 limit. Supporting the 
`string64` type ensures correct execution of string JOIN operations.
+In some cases, string sizes may exceed the unit32 limit. Supporting the 
`string64` type ensures correct execution of string JOIN operations. 
[#33850](https://github.com/apache/doris/pull/33850)
 
 **8. Allow Hadoop users to create Paimon Catalog**
 
-Permitted authorized Hadoop users to create Paimon Catalogs.
+Permitted authorized Hadoop users to create Paimon 
Catalogs.[#33833](https://github.com/apache/doris/pull/33833)
 
 **9. Fix `function_ipxx_cidr` function issues with constant parameters**
 
-Resolved problems with the `function_ipxx_cidr` function when handling 
constant parameters, ensuring the correctness of function execution.
+Resolved problems with the `function_ipxx_cidr` function when handling 
constant parameters, ensuring the correctness of function 
execution.[#33968](https://github.com/apache/doris/pull/33968)
 
 **10. Fix file download errors when restoring using HDFS**
 
-Resolved "failed to download" errors encountered during data restoration using 
HDFS, ensuring the accuracy and reliability of data recovery.
+Resolved "failed to download" errors encountered during data restoration using 
HDFS, ensuring the accuracy and reliability of data recovery. 
[#33303](https://github.com/apache/doris/issues/33303)
 
 **11. Fix column permission issues related to hidden columns**
 
-In some cases, permission settings for hidden columns may be incorrect. This 
fix ensures the correctness and security of column permission settings.
+In some cases, permission settings for hidden columns may be incorrect. This 
fix ensures the correctness and security of column permission settings. 
[#34849](https://github.com/apache/doris/pull/34849)
 
 **12. Fix issue where Arrow Flight cannot obtain the correct IP in K8s 
deployments**
 
-This fix resolves an issue where Arrow Flight cannot correctly obtain the IP 
address in Kubernetes deployment environments.
\ No newline at end of file
+This fix resolves an issue where Arrow Flight cannot correctly obtain the IP 
address in Kubernetes deployment 
environments.[#34850](https://github.com/apache/doris/pull/34850)
\ No newline at end of file
diff --git 
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/releasenotes/release-2.1.3.md
 
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/releasenotes/release-2.1.3.md
index 9a3060d42b..dc33f0d601 100644
--- 
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/releasenotes/release-2.1.3.md
+++ 
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/releasenotes/release-2.1.3.md
@@ -24,7 +24,7 @@ specific language governing permissions and limitations
 under the License.
 -->
 
-**Apache Doris 2.1.3 版本已于 2024 年 5 月 21 日正式发布**。包括支持向 Hive 
回写数据、物化视图、新函数等功能,同时改善权限管理并修复若干问题,进一步提升了系统的性能及稳定性,欢迎大家下载体验。
+**Apache Doris 2.1.3 版本已于 2024 年 5 月 21 日正式发布**。该版本更新带来了若干改进项,包括支持向 Hive 
回写数据、物化视图、新函数等功能,同时改善权限管理并修复若干问题,进一步提升了系统的性能及稳定性,欢迎大家下载体验。
 
 **官网下载:** https://doris.apache.org/download/
 
@@ -124,23 +124,23 @@ Variant 数据类型能够存储多种数据类型,在此优化中允许对 Va
 
 **1. 授权(Authorization)**
 
-- **Grant_priv 权限更改**:`Grant_priv`不能再被任意授予。执行 `GRANT` 
操作时,用户不仅需要具有`Grant_priv`,还需要具有要授予的权限。例如,如果想要授予对`table1`的 `SELECT` 
权限,那么该用户不仅需要具有 `GRANT` 权限,还需要具有对`table1`的 `SELECT` 权限,这增加了权限管理的安全性和一致性。 #32825
+- **Grant_priv 权限更改**:`Grant_priv`不能再被任意授予。执行 `GRANT` 
操作时,用户不仅需要具有`Grant_priv`,还需要具有要授予的权限。例如,如果想要授予对`table1`的 `SELECT` 
权限,那么该用户不仅需要具有 `GRANT` 权限,还需要具有对`table1`的 `SELECT` 权限,这增加了权限管理的安全性和一致性。
 
-- **Workload Group 和 Resource 的 Usage_priv**:`Usage_priv` 对 Workload Group 和 
Resource 的权限不再是全局级别的,而是仅限于 Resource 和 Workload Group 内,权限的授予和使用将更加具体。#32907
+- **Workload Group 和 Resource 的 Usage_priv**:`Usage_priv` 对 Workload Group 和 
Resource 的权限不再是全局级别的,而是仅限于 Resource 和 Workload Group 内,权限的授予和使用将更加具体。
 
-- **操作的授权**:之前未被授权的操作现在都有了相应的授权,以实现更加细致和全面地操作权限控制。 #33347
+- **操作的授权**:之前未被授权的操作现在都有了相应的授权,以实现更加细致和全面地操作权限控制。
 
 **2. LOG 目录配置**
 
-FE 和 BE 
的日志目录配置现在统一使用`LOG_DIR`环境变量,所有其他不同类型的日志都将以`LOG_DIR`作为根目录进行存储。同时为了保持版本间的兼容性,以前的配置项`sys_log_dir`仍然可以使用。#32933
+FE 和 BE 
的日志目录配置现在统一使用`LOG_DIR`环境变量,所有其他不同类型的日志都将以`LOG_DIR`作为根目录进行存储。同时为了保持版本间的兼容性,以前的配置项`sys_log_dir`仍然可以使用。
 
 **3. S3 表函数(TVF)**
 
-由于之前的解析方式在某些情况下可能无法正确识别或处理 S3 的 URL,因此将对象存储路径的解析逻辑进行重构。对于 S3 
表函数中的文件路径,需要传递`force_parsing_by_standard_uri`参数来确保被正确解析。#33858
+由于之前的解析方式在某些情况下可能无法正确识别或处理 S3 的 URL,因此将对象存储路径的解析逻辑进行重构。对于 S3 
表函数中的文件路径,需要传递`force_parsing_by_standard_uri`参数来确保被正确解析。
 
 ## 升级问题
 
-由于许多用户将某些关键字用作列名或属性值,因此将如下关键字设置为非保留关键字,允许用户将其用作标识符使用。 #34613
+由于许多用户将某些关键字用作列名或属性值,因此将如下关键字设置为非保留关键字,允许用户将其用作标识符使用。 
 
 ## 问题修复
 
diff --git 
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/releasenotes/release-2.1.3.md
 
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/releasenotes/release-2.1.3.md
index 7d62ccb1d0..e674365044 100644
--- 
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/releasenotes/release-2.1.3.md
+++ 
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/releasenotes/release-2.1.3.md
@@ -125,23 +125,23 @@ Variant 数据类型能够存储多种数据类型,在此优化中允许对 Va
 
 **1. 授权(Authorization)**
 
-- **Grant_priv 权限更改**:`Grant_priv`不能再被任意授予。执行 `GRANT` 
操作时,用户不仅需要具有`Grant_priv`,还需要具有要授予的权限。例如,如果想要授予对`table1`的 `SELECT` 
权限,那么该用户不仅需要具有 `GRANT` 权限,还需要具有对`table1`的 `SELECT` 权限,这增加了权限管理的安全性和一致性。 #32825
+- **Grant_priv 权限更改**:`Grant_priv`不能再被任意授予。执行 `GRANT` 
操作时,用户不仅需要具有`Grant_priv`,还需要具有要授予的权限。例如,如果想要授予对`table1`的 `SELECT` 
权限,那么该用户不仅需要具有 `GRANT` 权限,还需要具有对`table1`的 `SELECT` 权限,这增加了权限管理的安全性和一致性。
 
-- **Workload Group 和 Resource 的 Usage_priv**:`Usage_priv` 对 Workload Group 和 
Resource 的权限不再是全局级别的,而是仅限于 Resource 和 Workload Group 内,权限的授予和使用将更加具体。#32907
+- **Workload Group 和 Resource 的 Usage_priv**:`Usage_priv` 对 Workload Group 和 
Resource 的权限不再是全局级别的,而是仅限于 Resource 和 Workload Group 内,权限的授予和使用将更加具体。
 
-- **操作的授权**:之前未被授权的操作现在都有了相应的授权,以实现更加细致和全面地操作权限控制。 #33347
+- **操作的授权**:之前未被授权的操作现在都有了相应的授权,以实现更加细致和全面地操作权限控制。
 
 **2. LOG 目录配置**
 
-FE 和 BE 
的日志目录配置现在统一使用`LOG_DIR`环境变量,所有其他不同类型的日志都将以`LOG_DIR`作为根目录进行存储。同时为了保持版本间的兼容性,以前的配置项`sys_log_dir`仍然可以使用。#32933
+FE 和 BE 
的日志目录配置现在统一使用`LOG_DIR`环境变量,所有其他不同类型的日志都将以`LOG_DIR`作为根目录进行存储。同时为了保持版本间的兼容性,以前的配置项`sys_log_dir`仍然可以使用。
 
 **3. S3 表函数(TVF)**
 
-由于之前的解析方式在某些情况下可能无法正确识别或处理 S3 的 URL,因此将对象存储路径的解析逻辑进行重构。对于 S3 
表函数中的文件路径,需要传递`force_parsing_by_standard_uri`参数来确保被正确解析。#33858
+由于之前的解析方式在某些情况下可能无法正确识别或处理 S3 的 URL,因此将对象存储路径的解析逻辑进行重构。对于 S3 
表函数中的文件路径,需要传递`force_parsing_by_standard_uri`参数来确保被正确解析。
 
 ## 升级问题
 
-由于许多用户将某些关键字用作列名或属性值,因此将如下关键字设置为非保留关键字,允许用户将其用作标识符使用。 #34613
+由于许多用户将某些关键字用作列名或属性值,因此将如下关键字设置为非保留关键字,允许用户将其用作标识符使用。 
 
 ## 问题修复
 
diff --git a/versioned_docs/version-2.1/releasenotes/release-2.1.3.md 
b/versioned_docs/version-2.1/releasenotes/release-2.1.3.md
index b53286746e..e88ec3e94f 100644
--- a/versioned_docs/version-2.1/releasenotes/release-2.1.3.md
+++ b/versioned_docs/version-2.1/releasenotes/release-2.1.3.md
@@ -42,103 +42,103 @@ Please refer: 
[https://doris.apache.org/docs/lakehouse/datalake-building/hive-bu
 
 **2. Support building new asynchronous materialized views on top of existing 
ones**
 
-Users can create new asynchronous materialized views on top of existing ones, 
directly reusing pre-computed intermediate results for data processing. This 
simplifies complex aggregation and computation operations, reducing resource 
consumption and maintenance costs while further accelerating query performance 
and improving data availability.
+Users can create new asynchronous materialized views on top of existing ones, 
directly reusing pre-computed intermediate results for data processing. This 
simplifies complex aggregation and computation operations, reducing resource 
consumption and maintenance costs while further accelerating query performance 
and improving data availability. 
[#32984](https://github.com/apache/doris/pull/32984)
 
 **3. Support rewriting through nested materialized views**
 
-Materialized View (MV) is a database object used to store query results. Now, 
Apache Doris supports rewriting through nested materialized views, which helps 
optimize query performance.
+Materialized View (MV) is a database object used to store query results. Now, 
Apache Doris supports rewriting through nested materialized views, which helps 
optimize query performance. [#33362](https://github.com/apache/doris/pull/33362)
 
 **4. New `SHOW VIEWS` statement**
 
-The `SHOW VIEWS` statement can be used to query views in the database, 
facilitating better management and understanding of view objects in the 
database.
+The `SHOW VIEWS` statement can be used to query views in the database, 
facilitating better management and understanding of view objects in the 
database. [#32358](https://github.com/apache/doris/pull/32358)
 
 **5. Workload Group supports binding to specific BE nodes**
 
-Workload Group can be bound to specific BE nodes, enabling more refined 
control over query execution to optimize resource usage and improve performance.
+Workload Group can be bound to specific BE nodes, enabling more refined 
control over query execution to optimize resource usage and improve 
performance. [#32874](https://github.com/apache/doris/pull/32874)
 
 **6. Broker Load supports compressed JSON format**
 
-Broker Load now supports importing compressed JSON format data, significantly 
reducing bandwidth requirements for data transmission and accelerating data 
import performance.
+Broker Load now supports importing compressed JSON format data, significantly 
reducing bandwidth requirements for data transmission and accelerating data 
import performance. [#30809](https://github.com/apache/doris/pull/30809)
 
 **7. TRUNCATE Function can use columns as scale parameters**
 
-The TRUNCATE function can now accept columns as scale parameters, providing 
more flexibility when processing numerical data.
+The TRUNCATE function can now accept columns as scale parameters, providing 
more flexibility when processing numerical data. 
[#32746](https://github.com/apache/doris/pull/32746)
 
 **8. Add new functions `uuid_to_int` and `int_to_uuid`**
 
-These two functions allow users to convert between UUID and integer, 
significantly helping in scenarios that require handling UUID data.
+These two functions allow users to convert between UUID and integer, 
significantly helping in scenarios that require handling UUID data. 
[#33005](https://github.com/apache/doris/pull/33005)
 
 **9. Add `bypass_workload_group` session variable to bypass query queue**
 
-The `bypass_workload_group` session variable allows certain queries to bypass 
the Workload Group queue and execute directly, which is useful for handling 
critical queries that require quick responses.
+The `bypass_workload_group` session variable allows certain queries to bypass 
the Workload Group queue and execute directly, which is useful for handling 
critical queries that require quick responses. 
[#33101](https://github.com/apache/doris/pull/33101)
 
 **10. Add strcmp function**
 
-The strcmp function compares two strings and returns their comparison result, 
simplifying text data processing.
+The strcmp function compares two strings and returns their comparison result, 
simplifying text data processing. 
[#33272](https://github.com/apache/doris/pull/33272)
 
 **11. Support HLL functions `hll_from_base64` and `hll_to_base64`**
 
-HyperLogLog (HLL) is an algorithm for cardinality estimation. These two 
functions allow users to decode HLL data from a Base64-encoded string or encode 
HLL data as a Base64 string, which is very useful for storing and transmitting 
HLL data.
+HyperLogLog (HLL) is an algorithm for cardinality estimation. These two 
functions allow users to decode HLL data from a Base64-encoded string or encode 
HLL data as a Base64 string, which is very useful for storing and transmitting 
HLL data. [#32089](https://github.com/apache/doris/pull/32089)
 
 ## Optimization and Improvements
 
 **1. Replace SipHash with XXHash to improve shuffle performance**
 
-Both SipHash and XXHash are hashing functions, but XXHash may provide faster 
hashing speeds and better performance in certain scenarios. This optimization 
aims to improve performance during data shuffling by adopting XXHash.
+Both SipHash and XXHash are hashing functions, but XXHash may provide faster 
hashing speeds and better performance in certain scenarios. This optimization 
aims to improve performance during data shuffling by adopting XXHash. 
[#32919](https://github.com/apache/doris/pull/32919)
 
 **2. Asynchronous materialized views support NULL partition columns in OLAP 
tables**
 
-This enhancement allows asynchronous materialized views to support NULL 
partition columns in OLAP tables, enhancing data processing flexibility.
+This enhancement allows asynchronous materialized views to support NULL 
partition columns in OLAP tables, enhancing data processing 
flexibility.[#32698](https://github.com/apache/doris/pull/32698)
 
 **3. Limit maximum string length to 1024 when collecting column statistics to 
control BE memory usage**
 
-Limiting the string length when collecting column statistics prevents 
excessive data from consuming too much BE memory, helping maintain system 
stability and performance.
+Limiting the string length when collecting column statistics prevents 
excessive data from consuming too much BE memory, helping maintain system 
stability and performance. [#32470](https://github.com/apache/doris/pull/32470)
 
 **4. Support dynamic deletion of Bitmap cache to improve performance**
 
-Dynamically deleting no longer needed Bitmap Cache can free up memory and 
improve system performance.
+Dynamically deleting no longer needed Bitmap Cache can free up memory and 
improve system performance. [#32991](https://github.com/apache/doris/pull/32991)
 
 **5. Reduce memory usage during ALTER operations**
 
-Reducing memory usage during ALTER operations improves the efficiency of 
system resource utilization.
+Reducing memory usage during ALTER operations improves the efficiency of 
system resource utilization. 
[#33474](https://github.com/apache/doris/pull/33474)
 
 **6. Support constant folding for complex types**
 
-Supports constant folding for Array/Map/Struct complex types.
+Supports constant folding for Array/Map/Struct complex 
types.[#32867](https://github.com/apache/doris/pull/32867)
 
 **7. Add support for Variant type in Aggregate Key Model**
 
-The Variant data type can store multiple data types. This optimization allows 
aggregation operations on Variant type data, enhancing the flexibility of 
semi-structured data analysis.
+The Variant data type can store multiple data types. This optimization allows 
aggregation operations on Variant type data, enhancing the flexibility of 
semi-structured data analysis. 
[#33493](https://github.com/apache/doris/pull/33493)
 
-**8. Support new inverted index format in CCR**
+**8. Support new inverted index format in CCR** 
[#33415](https://github.com/apache/doris/pull/33415)
 
-**9. Optimize rewriting performance for nested materialized views**
+**9. Optimize rewriting performance for nested materialized views** 
[#34127](https://github.com/apache/doris/pull/34127)
 
 **10. Support decimal256 type in row-based storage format**
 
-Supporting the decimal256 type in row-based storage extends the system's 
ability to handle high-precision numerical data.
+Supporting the decimal256 type in row-based storage extends the system's 
ability to handle high-precision numerical data. 
[#34887](https://github.com/apache/doris/pull/34887)
 
 ## Behavioral Changes
 
 **1. Authorization**
 
-- **Grant_priv permission changes**: `Grant_priv` can no longer be arbitrarily 
granted. When performing a `GRANT` operation, the user not only needs to have 
`Grant_priv` but also the permissions to be granted. For example, to grant 
`SELECT` permission on `table1`, the user needs both `GRANT` permission and 
`SELECT` permission on `table1`, enhancing security and consistency in 
permission management. #32825
+- **Grant_priv permission changes**: `Grant_priv` can no longer be arbitrarily 
granted. When performing a `GRANT` operation, the user not only needs to have 
`Grant_priv` but also the permissions to be granted. For example, to grant 
`SELECT` permission on `table1`, the user needs both `GRANT` permission and 
`SELECT` permission on `table1`, enhancing security and consistency in 
permission management. [#32825](https://github.com/apache/doris/pull/32825)
 
-- **Workload group and resource usage_priv**: `Usage_priv` for Workload Group 
and Resource is no longer global but limited to Resource and Workload Group, 
making permission granting and usage more specific. #32907
+- **Workload group and resource usage_priv**: `Usage_priv` for Workload Group 
and Resource is no longer global but limited to Resource and Workload Group, 
making permission granting and usage more specific. 
[#32907](https://github.com/apache/doris/pull/32907)
 
-- **Authorization for operations**: Operations that were previously 
unauthorized now have corresponding authorizations for more detailed and 
comprehensive operational permission control. #33347
+- **Authorization for operations**: Operations that were previously 
unauthorized now have corresponding authorizations for more detailed and 
comprehensive operational permission control. 
[#33347](https://github.com/apache/doris/pull/33347)
 
 **2. LOG directory configuration**
 
-The log directory configuration for FE and BE now uniformly uses the `LOG_DIR` 
environment variable. All other different types of logs will be stored with 
`LOG_DIR` as the root directory. To maintain compatibility between versions, 
the previous configuration item `sys_log_dir` can still be used. #32933
+The log directory configuration for FE and BE now uniformly uses the `LOG_DIR` 
environment variable. All other different types of logs will be stored with 
`LOG_DIR` as the root directory. To maintain compatibility between versions, 
the previous configuration item `sys_log_dir` can still be used. 
[#32933](https://github.com/apache/doris/pull/32933)
 
 **3. S3 Table Function (TVF)**
 
-Due to issues with correctly recognizing or processing S3 URLs in certain 
cases, the parsing logic for object storage paths has been refactored. For file 
paths in S3 table functions, the `force_parsing_by_standard_uri` parameter 
needs to be passed to ensure correct parsing. #33858
+Due to issues with correctly recognizing or processing S3 URLs in certain 
cases, the parsing logic for object storage paths has been refactored. For file 
paths in S3 table functions, the `force_parsing_by_standard_uri` parameter 
needs to be passed to ensure correct parsing. 
[#33858](https://github.com/apache/doris/pull/33858)
 
 ## Upgrade Issues
 
-Since many users use certain keywords as column names or attribute values, the 
following keywords have been set as non-reserved, allowing users to use them as 
identifiers. #34613
+Since many users use certain keywords as column names or attribute values, the 
following keywords have been set as non-reserved, allowing users to use them as 
identifiers. [#34613](https://github.com/apache/doris/pull/34613)
 
 ## Bug Fixes
 
@@ -148,44 +148,44 @@ Resolved the no data error that could occur when reading 
Hive tables on Tencent
 
 **2. Fix incorrect results returned by `milliseconds_diff` function**
 
-Fixed an issue where the `milliseconds_diff` function returned incorrect 
results in some cases, ensuring the accuracy of time difference calculations.
+Fixed an issue where the `milliseconds_diff` function returned incorrect 
results in some cases, ensuring the accuracy of time difference calculations. 
[#32897](https://github.com/apache/doris/pull/32897)
 
 **3. User-defined variables should be rorwarded to the Master node**
 
-Ensured that user-defined variables are correctly passed to the Master node 
for consistency and correct execution logic across the entire system.
+Ensured that user-defined variables are correctly passed to the Master node 
for consistency and correct execution logic across the entire system. 
[#33013]https://github.com/apache/doris/pull/33013
 
 **4. Fix Schema Change issues when adding complex type columns**
 
-Resolved Schema Change issues that could arise when adding complex type 
columns, ensuring the correctness of Schema Changes.
+Resolved Schema Change issues that could arise when adding complex type 
columns, ensuring the correctness of Schema Changes. 
[#31824](https://github.com/apache/doris/pull/31824)
 
 **5. Fix data loss issue in Routine Load when FE Master node changes**
 
-`Routine Load` is often used to subscribe to Kafka message queues. This fix 
addresses potential data loss issues that may occur during FE Master node 
changes.
+`Routine Load` is often used to subscribe to Kafka message queues. This fix 
addresses potential data loss issues that may occur during FE Master node 
changes. [#33678](https://github.com/apache/doris/pull/33678)
 
 **6. Fix Routine Load failure when Workload Group cannot be found**
 
-Resolved an issue where `Routine Load` would fail if the specified Workload 
Group could not be found.
+Resolved an issue where `Routine Load` would fail if the specified Workload 
Group could not be found. [#33596](https://github.com/apache/doris/pull/33596)
 
 **7. Support column string64 to avoid join failures when string size overflows 
unit32**
 
-In some cases, string sizes may exceed the unit32 limit. Supporting the 
`string64` type ensures correct execution of string JOIN operations.
+In some cases, string sizes may exceed the unit32 limit. Supporting the 
`string64` type ensures correct execution of string JOIN operations. 
[#33850](https://github.com/apache/doris/pull/33850)
 
 **8. Allow Hadoop users to create Paimon Catalog**
 
-Permitted authorized Hadoop users to create Paimon Catalogs.
+Permitted authorized Hadoop users to create Paimon 
Catalogs.[#33833](https://github.com/apache/doris/pull/33833)
 
 **9. Fix `function_ipxx_cidr` function issues with constant parameters**
 
-Resolved problems with the `function_ipxx_cidr` function when handling 
constant parameters, ensuring the correctness of function execution.
+Resolved problems with the `function_ipxx_cidr` function when handling 
constant parameters, ensuring the correctness of function 
execution.[#33968](https://github.com/apache/doris/pull/33968)
 
 **10. Fix file download errors when restoring using HDFS**
 
-Resolved "failed to download" errors encountered during data restoration using 
HDFS, ensuring the accuracy and reliability of data recovery.
+Resolved "failed to download" errors encountered during data restoration using 
HDFS, ensuring the accuracy and reliability of data recovery. 
[#33303](https://github.com/apache/doris/issues/33303)
 
 **11. Fix column permission issues related to hidden columns**
 
-In some cases, permission settings for hidden columns may be incorrect. This 
fix ensures the correctness and security of column permission settings.
+In some cases, permission settings for hidden columns may be incorrect. This 
fix ensures the correctness and security of column permission settings. 
[#34849](https://github.com/apache/doris/pull/34849)
 
 **12. Fix issue where Arrow Flight cannot obtain the correct IP in K8s 
deployments**
 
-This fix resolves an issue where Arrow Flight cannot correctly obtain the IP 
address in Kubernetes deployment environments.
\ No newline at end of file
+This fix resolves an issue where Arrow Flight cannot correctly obtain the IP 
address in Kubernetes deployment 
environments.[#34850](https://github.com/apache/doris/pull/34850)
\ No newline at end of file


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org
For additional commands, e-mail: commits-h...@doris.apache.org


Reply via email to