This is an automated email from the ASF dual-hosted git repository.
morningman 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 e09893216b4 remove some unsuitable commercial content (#1154)
e09893216b4 is described below
commit e09893216b4e520b1ace36c72a775cf50e3707be
Author: Mingyu Chen <morning...@163.com>
AuthorDate: Wed Sep 25 23:16:57 2024 +0800
remove some unsuitable commercial content (#1154)
# Versions
- [ ] dev
- [ ] 3.0
- [ ] 2.1
- [ ] 2.0
# Languages
- [ ] Chinese
- [ ] English
---
blog/apache-doris-vs-rockset.md | 2 +-
.../tutorials/log-storage-analysis.md | 14 +++------
.../import/migrate-data-from-other-olap.md | 10 +++++--
docs/lakehouse/sql-dialect.md | 24 ++++++---------
gettingStarted/tutorials/log-storage-analysis.md | 34 +++++++++-------------
.../import/migrate-data-from-other-olap.md | 11 ++++---
.../current/lakehouse/sql-dialect.md | 26 +++++++----------
.../import/migrate-data-from-other-olap.md | 11 ++++---
.../import/migrate-data-from-other-olap.md | 11 ++++---
.../version-2.1/lakehouse/sql-dialect.md | 26 +++++++----------
.../import/migrate-data-from-other-olap.md | 11 ++++---
.../version-3.0/lakehouse/sql-dialect.md | 26 +++++++----------
.../import/migrate-data-from-other-olap.md | 12 ++++++--
.../practical-guide/log-storage-analysis.md | 14 ++-------
.../import/migrate-data-from-other-olap.md | 10 +++++--
.../version-2.1/lakehouse/sql-dialect.md | 24 ++++++---------
.../practical-guide/log-storage-analysis.md | 14 ++-------
.../import/migrate-data-from-other-olap.md | 10 +++++--
.../version-3.0/lakehouse/sql-dialect.md | 24 ++++++---------
.../practical-guide/log-storage-analysis.md | 16 +++-------
20 files changed, 146 insertions(+), 184 deletions(-)
diff --git a/blog/apache-doris-vs-rockset.md b/blog/apache-doris-vs-rockset.md
index a176b14afe8..03a98a2beee 100644
--- a/blog/apache-doris-vs-rockset.md
+++ b/blog/apache-doris-vs-rockset.md
@@ -60,4 +60,4 @@ As an open-source real-time data warehouse, Apache Doris is
trusted by over 4000
As a Top-Level Project of the Apache Software Foundation, Apache Doris is
supported by a robust and fast-growing community. It has accumulated over 11.8K
GitHub stars and 636 contributors so far.
-If you are seeking a fully managed solution instead of an open source product,
you might want to look into [VeloDB](https://www.velodb.io). As the commercial
service provider of Apache Doris, VeloDB offers a wider range of products that
are more tailored to the needs of enterprises. [VeloDB
Cloud](https://www.velodb.io/cloud) decouples compute and storage on the basis
of Apache Doris, thus realizing higher elastic scalability and cost efficiency.
Like cloud-based Rockset, it frees users [...]
\ No newline at end of file
+Apache Doris is the best open-source alternative to Rockset. Feel free to
contact d...@doris.apache.org for more assistance.
diff --git a/common_docs_zh/gettingStarted/tutorials/log-storage-analysis.md
b/common_docs_zh/gettingStarted/tutorials/log-storage-analysis.md
index be72b599a70..59be6a9010a 100644
--- a/common_docs_zh/gettingStarted/tutorials/log-storage-analysis.md
+++ b/common_docs_zh/gettingStarted/tutorials/log-storage-analysis.md
@@ -60,7 +60,7 @@ under the License.
经过 Benchmark 测试及生产验证，基于 Apache Doris 构建的日志存储与分析平台，性价比相对于 Elasticsearch 具有 5～10
倍的提升。Apache Doris 的性能优势，主要得益于全球领先的高性能存储和查询引擎，以及下面一些针对日志场景的专门优化：
- **写入吞吐提升**：Elasticsearch 写入的性能瓶颈在于解析数据和构建倒排索引的 CPU 消耗。相比之下，Apache Doris
进行了两方面的写入优化：一方面利用 SIMD 等 CPU 向量化指令提升了 JSON
数据解析速度和索引构建性能；另一方面针对日志场景简化倒了排索引结构，去掉日志场景不需要的正排等数据结构，有效降低了索引构建的复杂度。同样的资源，Apache
Doris 的写入性能是 Elasticsearch 的 3～5 倍。
-- **存储成本降低**：Elasticsearch 存储瓶颈在于正排、倒排、Docvalue 列存多份存储和通用压缩算法压缩率较低。相比之下，Apache
Doris 在存储上进行了以下优化：去掉正排，缩减了 30% 的索引数据量；采用列式存储和 Zstandard 压缩算法，压缩比可达到 5～10 倍，远高于
Elasticsearch 的 1.5 倍；日志数据中冷数据访问频率很低，Apache Doris
冷热分层功能可以将超过定义时间段的日志自动存储到更低的对象存储中，冷数据的存储成本可降低 70% 以上。同样的原始数据，SelectDB 的存储成本只需要
Elasticsearch 的 20% 左右。
+- **存储成本降低**：Elasticsearch 存储瓶颈在于正排、倒排、Docvalue 列存多份存储和通用压缩算法压缩率较低。相比之下，Apache
Doris 在存储上进行了以下优化：去掉正排，缩减了 30% 的索引数据量；采用列式存储和 Zstandard 压缩算法，压缩比可达到 5～10 倍，远高于
Elasticsearch 的 1.5 倍；日志数据中冷数据访问频率很低，Apache Doris
冷热分层功能可以将超过定义时间段的日志自动存储到更低的对象存储中，冷数据的存储成本可降低 70% 以上。同样的原始数据，Doris 的存储成本只需要
Elasticsearch 的 20% 左右。
- **查询性能提升**：Apache Doris
将全文检索的流程简化，跳过了相关性打分等日志场景不需要的算法，加速基础的检索性能。同时针对日志场景常见的查询，比如查询包含某个关键字的最新 100
条日志，在查询规划和执行上做专门的 TopN 动态剪枝等优化。
### 分析能力强
@@ -154,11 +154,6 @@ Apache Doris 对 Flexible Schema 的日志数据提供了几个方面的支持
完成资源评估后，可以开始部署 Apache Doris 集群，推荐在物理机及虚拟机环境中进行部署。手动部署集群，可参考
[手动部署](../../install/cluster-deployment/standard-deployment)。
-另，推荐使用 SelectDB Enterprise 推出的 Cluster Manager 工具部署集群，以降低整体部署成本。更多关于 Cluster
Manager 的信息，可参考以下文档：
-
-- [Cluster Manager for Apache Doris 24.x
安装手册](https://docs.selectdb.com/docs/enterprise/cluster-manager-guide/deployment-guide/deployment-guide-24.x)
-- [Cluster Manager for Apache Doris 24.x
使用手册](https://docs.selectdb.com/docs/enterprise/cluster-manager-guide/management-guide/management-guide-24.x)
-
### 第 3 步：优化 FE 和 BE 配置
完成集群部署后，需分别优化 FE 和 BE 配置参数，以更加契合日志存储与分析的场景。
@@ -555,16 +550,15 @@ ORDER BY ts DESC LIMIT 10;
**可视化日志分析**
-基于 Apache Doris 构建的 SelectDB Enterprise Core 提供了名为 Doris WebUI 的数据开发平台，Doris
WebUI 包含了类 Kibana Discover 的日志检索分析界面，提供直观、易用的探索式日志分析交互，如下图所示：
+一些第三方厂商提供了基于 Apache Doris 的可视化日志分析开发平台，包含类 Kibana Discover
的日志检索分析界面，提供直观、易用的探索式日志分析交互。
-在此界面上，Doris WebUI 主要支持以下功能：
-
- 支持全文检索和 SQL 两种模式
- 支持时间框和直方图上选择查询日志的时间段
- 支持信息丰富的日志明细展示，还可以展开成 JSON 或表格
- 在日志数据上下文交互式点击增加和删除筛选条件
- 搜索结果的字段 Top 值展示，便于发现异常值和进一步下钻分析
-你可以 [点此下载 SelectDB Enterprise
Core](https://www.selectdb.com/download/enterprise#core)，完成
[安装](https://docs.selectdb.com/docs/enterprise/enterprise-core-guide/selectdb-distribution-doris-core-deployment-guide)
后，即可使用 Doris WebUI 登录数据库。更多关于如何使用 Doris WebUI 的信息，可参考
[WebUI](https://docs.selectdb.com/docs/enterprise/enterprise-core-guide/selectdb-webui-guide)。
\ No newline at end of file
+您可以联系 d...@doris.apache.org 获得更多帮助。
+
diff --git a/docs/data-operate/import/migrate-data-from-other-olap.md
b/docs/data-operate/import/migrate-data-from-other-olap.md
index 1a54eb939b0..10ea5a10227 100644
--- a/docs/data-operate/import/migrate-data-from-other-olap.md
+++ b/docs/data-operate/import/migrate-data-from-other-olap.md
@@ -32,7 +32,13 @@ To migrate data from other OLAP systems to Doris, you have a
variety of options:
- You can also leverage the connectors of the OLAP systems, use tools like
Spark / Flink, and then call the corresponding Doris Connector to write data
into Doris.
-In addition to the above methods, [VeloDB](https://www.velodb.io), the
commercial supporter of Apache Doris, provides a free visual data migration
tool: X2Doris. Developed by VeloDB, X2Doris is designed to migrate various
offline data into Apache Doris. It combines the funtionalities of automatic
table creation and data migration. Currently, it supports migrating data to
Doris from databases including Apache Doris/Hive/Kudu and StarRocks. The entire
process is performed through a visual [...]
+In addition to the three methods mentioned above, VeloDB offers a free visual
data migration tool called [X2Doris](https://www.velodb.io/download/tools).
+
+X2Doris is a core tool specifically for migrating various offline data to
Apache Doris. This tool integrates `automatic Doris table creation` and `data
migration`. Currently, it supports the migration of data from Apache
Doris/Hive/Kudu, and StarRocks databases to Doris. The entire process is
visualized on a platform, making it very simple and easy to use, thereby
lowering the threshold for synchronizing data to Doris.
+
+:::info NOTE
+X2Doris are not maintained or endorsed by the Apache Doris, which is overseen
by the Committers and the Doris PMC. Their use is entirely at your discretion,
and the community is not responsible for verifying the licenses or validity of
these tools.
+:::
## X2Doris
@@ -40,7 +46,7 @@ In addition to the above methods,
[VeloDB](https://www.velodb.io), the commercia
As a one-stop data migration tool, X2Doris supports Apache Hive, Apache Kudu,
StarRocks, and Apache Doris itself as data source. What's more, there are more
data sources such as Greenplum and Druid that are under development and will be
released subsequently. Among them, the Hive version already supports Hive 1.x
and 2.x, while Doris, StarRocks, Kudu, and other data sources also support
multiple different versions.
-Now, X2Doris is supported migrating data to Apache Doris and VeloDB, including
VeloDB Cloud and VeloDB Enterprise. With X2Doris, users can build a complete
database migration link from other OLAP systems to Apache Doris, and can also
achieve data backup and recovery between different Doris clusters.
+With X2Doris, users can build a complete database migration link from other
OLAP systems to Apache Doris, and can also achieve data backup and recovery
between different Doris clusters.
diff --git a/docs/lakehouse/sql-dialect.md b/docs/lakehouse/sql-dialect.md
index e7aafe870f2..7f3c9ddd26d 100644
--- a/docs/lakehouse/sql-dialect.md
+++ b/docs/lakehouse/sql-dialect.md
@@ -31,38 +31,32 @@ Starting from version 2.1, Doris can support multiple SQL
dialects, such as Pres
:::
:::caution
- 1. This function is currently an experimental function. If you encounter any
problems during use, you are welcome to provide feedback through the mail
group, [GitHub issue](https://github.com/apache/doris/issues), etc. .
-
+This function is currently an experimental function. If you encounter any
problems during use, you are welcome to provide feedback through the mail
group, [GitHub issue](https://github.com/apache/doris/issues)
:::
## Deploy service
1. Download latest [Doris SQL
Convertor](https://www.selectdb.com/tools/doris-sql-convertor)
- > Note:
- >
- > The SQL convertor tool is based on the open source
[SQLGlot](https://github.com/tobymao/sqlglot). For more information about
SQLGlot, please refer to [SQLGlot official
website](https://sqlglot.com/sqlglot.html)
+ :::info NOTE
+ The SQL dialect conversion tool is based on the open-source
[SQLGlot](https://github.com/tobymao/sqlglot) and has been further developed by
SelectDB. For more information about SQLGlot, please refer to the [SQLGlot
official website](https://sqlglot.com/sqlglot.html).
+The SQL Convertor is not maintained or endorsed by Apache Doris; these efforts
are supervised by Committers and the Doris PMC. The use of these resources and
services is entirely at your own discretion, and the community does not verify
the licensing or validity of these tools.
+ :::
2. On any FE node, start the service through the following command:
`sh bin/start.sh`
- :::tip
- 1. This service is a stateless service and can be started and stopped
at any time.
-
- 2. The default startup port is `5001`, and the specified port can be
configured in `conf/config.conf`.
-
- 3. It is recommended to start a separate service on each FE node.
- :::
+ - This service is a stateless service and can be started and stopped at
any time.
+ - The default startup port is `5001`, and the specified port can be
configured in `conf/config.conf`.
+ - It is recommended to start a separate service on each FE node.
3. Start the Doris cluster (version 2.1 or higher)
4. Set the URL of the SQL Dialect Conversion Service with the following
command in Doris:
`MySQL> set global sql_converter_service_url =
"http://127.0.0.1:5001/api/v1/convert"`
- :::tip
- 1. `127.0.0.1:5001` is the deployment node IP and port of the SQL
dialect conversion service.
- :::
+ - `127.0.0.1:5001` is the deployment node IP and port of the SQL
dialect conversion service.
## Use SQL dialect
diff --git a/gettingStarted/tutorials/log-storage-analysis.md
b/gettingStarted/tutorials/log-storage-analysis.md
index 59d152c8676..f000b40bf25 100644
--- a/gettingStarted/tutorials/log-storage-analysis.md
+++ b/gettingStarted/tutorials/log-storage-analysis.md
@@ -68,7 +68,7 @@ After Benchmark testing and production validation, the log
storage and analysis
- **Improved write throughput**: Elasticsearch's write performance bottleneck
lies in CPU consumption for parsing data and building inverted indexes. In
comparison, Apache Doris has optimized writes in two aspects: using SIMD and
other CPU vector instructions to improve JSON data parsing speed and
index-building performance and simplifying the inverted index structure for log
scenarios by removing unnecessary data structures like forward indexes,
effectively reducing index build complexi [...]
-- **Reduced storage costs**: Elasticsearch's storage bottleneck comes from
multiple storage of forward, inverted, Docvalue columns, and lower compression
ratios with general compression algorithms. Conversely, Apache Doris has
optimized storage by eliminating forward indexes, reducing index data volume by
30%; adopting columnar storage and Zstandard compression algorithm, achieving
compression ratios 5-10 times higher than Elasticsearch's 1.5 times; with low
access frequency of cold data [...]
+- **Reduced Storage Costs**: The storage bottleneck in Elasticsearch lies in
the multiple storage formats for forward indexes, inverted indexes, and
Docvalue columns, as well as the relatively low compression ratio of its
general compression algorithms. In contrast, Apache Doris has made the
following optimizations in storage: it removes the forward index, reducing the
index data size by 30%; it uses columnar storage and the Zstandard compression
algorithm, achieving a compression ratio [...]
### Strong analytical capabilities
@@ -175,13 +175,7 @@ Refer to the following table to learn about the values of
indicators in the exam
### Step 2: Deploy the cluster
-After estimating the resources, you need to deploy the cluster. It is
recommended to deploy in both physical and virtual environments manually. For
manual deployment, refer to [Manual
Deployment](../../install/cluster-deployment/standard-deployment).
-
-Alternatively, it is recommended to use VeloDB Manager provided by VeloDB
Enterprise to deploy the cluster, reducing overall deployment costs. For more
information about the VeloDB Manager, please refer to the following documents:
-
-- [VeloDB Manager 24.x Installation
Manual](https://docs.velodb.io/enterprise/velodb-manager-guide/deployment-guide/deployment-guide-24.x)
-
-- [VeloDB Manager 24.x User
Guide](https://docs.velodb.io/enterprise/velodb-manager-guide/management-guide/management-guide-24.x)
+After estimating the resources, you need to deploy the cluster. It is
recommended to deploy in both physical and virtual environments manually. For
manual deployment, refer to [Manual
Deployment](../install/cluster-deployment/standard-deployment.md).
### Step 3: Optimize FE and BE configurations
@@ -201,7 +195,7 @@ You can find FE configuration fields in `fe/conf/fe.conf`.
Refer to the followin
| `autobucket_min_buckets = 10` | Increase the
minimum number of automatically bucketed buckets from 1 to 10 to avoid
insufficient buckets when the log volume increases. |
| `max_backend_heartbeat_failure_tolerance_count = 10` | In log
scenarios, the BE server may experience high pressure, leading to short-term
timeouts, so increase the tolerance count from 1 to 10. |
-For more information, refer to [FE
Configuration](../../admin-manual/config/fe-config).
+For more information, refer to [FE
Configuration](../admin-manual/config/fe-config.md).
**Optimize BE configurations**
@@ -231,7 +225,7 @@ You can find BE configuration fields in `be/conf/be.conf`.
Refer to the followin
| - | `trash_file_expire_time_sec = 300`
`path_gc_check_interval_second = 900` `path_scan_interval_second = 900` |
Accelerate the recycling of trash files. |
-For more information, refer to [BE
Configuration](../../admin-manual/config/be-config).
+For more information, refer to [BE
Configuration](../admin-manual/config/be-config.md).
### Step 4: Create tables
@@ -241,7 +235,7 @@ Due to the distinct characteristics of both writing and
querying log data, it is
- For data partitioning:
- - Enable [range
partitioning](../../table-design/data-partition#range-partition) with [dynamic
partitions](../../table-design/data-partition#dynamic-partition) managed
automatically by day.
+ - Enable [range
partitioning](https://doris.apache.org/docs/table-design/data-partition#range-partition)
with [dynamic
partitions](https://doris.apache.org/docs/table-design/data-partition#dynamic-partition)
managed automatically by day.
- Use a field in the DATETIME type as the key for accelerated retrieval of
the latest N log entries.
@@ -251,7 +245,7 @@ Due to the distinct characteristics of both writing and
querying log data, it is
- Use the Random strategy to optimize batch writing efficiency when paired
with single tablet imports.
-For more information, refer to [Data
Partitioning](../../table-design/data-partition).
+For more information, refer to [Data
Partitioning](../table-design/data-partition.md).
**Configure compaction fileds**
@@ -402,7 +396,7 @@ output {
./bin/logstash -f logstash_demo.conf
```
-For more information about the Logstash Doris Output plugin, see [Logstash
Doris Output Plugin](../../ecosystem/logstash).
+For more information about the Logstash Doris Output plugin, see [Logstash
Doris Output Plugin](../ecosystem/logstash.md).
**Integrating Filebeat**
@@ -470,7 +464,7 @@ headers:
./filebeat-doris-1.0.0 -c filebeat_demo.yml
```
-For more information about Filebeat, refer to [Beats Doris Output
Plugin](../../ecosystem/beats).
+For more information about Filebeat, refer to [Beats Doris Output
Plugin](../ecosystem/beats.md).
**Integrating Kafka**
@@ -478,7 +472,7 @@ Write JSON formatted logs to Kafka's message queue, create
a Kafka Routine Load,
You can refer to the example below, where `property.*` represents Librdkafka
client-related configurations and needs to be adjusted according to the actual
Kafka cluster situation.
-```sql
+```SQL
CREATE ROUTINE LOAD load_log_kafka ON log_db.log_table
COLUMNS(ts, clientip, request, status, size)
PROPERTIES (
@@ -503,13 +497,13 @@ FROM KAFKA (
<br />SHOW ROUTINE LOAD;
```
-For more information about Kafka, see [Routine
Load](../../data-operate/import/routine-load-manual)。
+For more information about Kafka, see [Routine
Load](../data-operate/import/routine-load-manual.md)。
**Using customized programs to collect logs**
In addition to integrating common log collectors, you can also customize
programs to import log data into Apache Doris using the Stream Load HTTP API.
Refer to the following code:
-```shell
+```shell
curl
--location-trusted
-u username:password
@@ -580,12 +574,10 @@ ORDER BY ts DESC LIMIT 10;
**Analyze logs visually**
-VeloDB Enterprise Core, built on Apache Doris, provides a data development
platform called VeloDB Enterprise WebUI ("WebUI"), featuring a Kibana
Discover-like log retrieval and analysis interface for intuitive and easy
exploratory log analysis interaction as shown in the image below:
+Some third-party vendors offer visual log analysis development platforms based
on Apache Doris, which include a log search and analysis interface similar to
Kibana Discover. These platforms provide an intuitive and user-friendly
exploratory log analysis interaction.
-On this interface, WebUI supports the following operations:
-
- Support for full-text search and SQL modes
- Support for selecting query log timeframes with time boxes and histograms
@@ -596,4 +588,4 @@ On this interface, WebUI supports the following operations:
- Display of top field values in search results for finding anomalies and
further drilling down for analysis
-You can [click to download VeloDB Enterprise
Core](https://www.velodb.io/download/enterprise) and [install
it](https://docs.velodb.io/enterprise/enterprise-core-guide/velodb-distribution-doris-core-deployment-guide)
to use WebUI. For more information about the main functions and how to use
WebUI, see
[WebUI](https://docs.velodb.io/enterprise/enterprise-core-guide/velodb-webui-guide).
\ No newline at end of file
+Please contact d...@doris.apache.org to find more.
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/migrate-data-from-other-olap.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/migrate-data-from-other-olap.md
index c631c8a8056..cd08da9bd2e 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/migrate-data-from-other-olap.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/migrate-data-from-other-olap.md
@@ -35,7 +35,11 @@ under the License.
除了以上三种方式，[SelectDB](https://www.selectdb.com/tools/x2doris) 提供了免费的可视化的数据迁移工具
X2Doris。
-X2Doris 是 SelectDB 开发的，专门用于将各种离线数据迁移到 Apache Doris 中的核心工具，该工具集 `自动建 Doris 表` 和
`数据迁移` 为一体，目前支持了 Apache Doris/Hive/Kudu、StarRocks 数据库往 Doris
迁移的工作，整个过程可视化的平台操作，非常简单易用，减轻数据同步到 Doris 中的门槛。
+X2Doris 专门用于将各种离线数据迁移到 Apache Doris 中的核心工具，该工具集 `自动建 Doris 表` 和 `数据迁移`
为一体，目前支持了 Apache Doris/Hive/Kudu、StarRocks 数据库往 Doris
迁移的工作，整个过程可视化的平台操作，非常简单易用，减轻数据同步到 Doris 中的门槛。
+
+:::info NOTE
+X2Doris 并非由 Apache Doris 维护或认可，这些工作由 Committers 和 Doris PMC
监督。使用这些资源和服务完全由您自行决定，社区不负责验证这些工具的许可或有效性。
+:::
## X2Doris 核心特性
@@ -43,8 +47,7 @@ X2Doris 是 SelectDB 开发的，专门用于将各种离线数据迁移到 Apac
定位于一站式数据迁移工具，X2Doris 目前已支持了 Apache Hive、Apache Kudu、StarRocks 以及 Apache Doris
自身作为数据源端，Greenplum、Druid 等更多数据源正在开发中，后续将陆续发布。其中 Hive 版本已支持 Hive 1.x 和 2.x
版本，Doris、StarRocks、Kudu 等数据源也同时支持了多个不同版本。
-目标端已支持 Apache Doris 和 SelectDB，包含 SelectDB Cloud 和 SelectDB Enterprise。基于
X2Doris 用户可以构建从其他 OLAP 系统到 Apache Doris 的整库迁移链路，并可以实现不同 Doris 集群间的数据备份和恢复。
-
+基于 X2Doris 用户可以构建从其他 OLAP 系统到 Apache Doris 的整库迁移链路，并可以实现不同 Doris 集群间的数据备份和恢复。
@@ -75,4 +78,4 @@ X2Doris 为此场景做了适配，在此以 Hive 表迁移为例。在迁移 Hi
- 立即下载：https://www.selectdb.com/download/tools#x2doris
--
文档地址：https://docs.selectdb.com/docs/ecosystem/x2doris/x2doris-deployment-guide
\ No newline at end of file
+-
文档地址：https://docs.selectdb.com/docs/ecosystem/x2doris/x2doris-deployment-guide
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/sql-dialect.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/sql-dialect.md
index 06678e4eff1..b58a805f305 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/sql-dialect.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/lakehouse/sql-dialect.md
@@ -31,31 +31,27 @@ under the License.
:::
:::caution
-1. 该功能目前是实验性功能，您在使用过程中如遇到任何问题，欢迎通过邮件组、[GitHub
Issue](https://github.com/apache/doris/issues) 等方式进行反馈。
-
+该功能目前是实验性功能，您在使用过程中如遇到任何问题，欢迎通过邮件组、[GitHub
Issue](https://github.com/apache/doris/issues) 等方式进行反馈。
:::
## 部署服务
-**1. 下载最新版本的 [SQL 方言转换工具](https://www.selectdb.com/tools/doris-sql-convertor)**
-
- > 注：
- >
- > SQL 方言转换工具基于开源的 [SQLGlot](https://github.com/tobymao/sqlglot) 二次开发，关于
SQLGlot 可参阅 [SQLGlot 官网](https://sqlglot.com/sqlglot.html)
+1. 下载最新版本的 [SQL 方言转换工具](https://www.selectdb.com/tools/doris-sql-convertor)
+ :::info NOTE
+ SQL 方言转换工具基于开源的 [SQLGlot](https://github.com/tobymao/sqlglot) ，由 SelectDB
进行二次开发，关于 SQLGlot 可参阅 [SQLGlot 官网](https://sqlglot.com/sqlglot.html)。
+ SQL Convertor 并非由 Apache Doris 维护或认可，这些工作由 Committers 和 Doris PMC
监督。使用这些资源和服务完全由您自行决定，社区不负责验证这些工具的许可或有效性。
+ :::
2. 在任意 FE 节点，通过以下命令启动服务：
`sh bin/start.sh`
- :::tip
-
- **1. 该服务是一个无状态的服务，可随时启停。**
+ - 该服务是一个无状态的服务，可随时启停。
- 2. 默认启动端口是`5001`，可在`conf/config.conf`中配置指定端口。
+ - 默认启动端口是`5001`，可在`conf/config.conf`中配置指定端口。
- 3. 建议在每个 FE 节点都单独启动一个服务。
- :::
+ - 建议在每个 FE 节点都单独启动一个服务。
3. 启动 Doris 集群（2.1 或更高版本）
@@ -63,9 +59,7 @@ under the License.
`MySQL> set global sql_converter_service_url =
"http://127.0.0.1:5001/api/v1/convert"`
- :::tip
- `127.0.0.1:5001` 是 SQL 方言转换服务的部署节点 ip 和端口。
- :::
+ - `127.0.0.1:5001` 是 SQL 方言转换服务的部署节点 ip 和端口。
## 使用 SQL 方言
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/data-operate/import/migrate-data-from-other-olap.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/data-operate/import/migrate-data-from-other-olap.md
index c631c8a8056..cd08da9bd2e 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/data-operate/import/migrate-data-from-other-olap.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/data-operate/import/migrate-data-from-other-olap.md
@@ -35,7 +35,11 @@ under the License.
除了以上三种方式，[SelectDB](https://www.selectdb.com/tools/x2doris) 提供了免费的可视化的数据迁移工具
X2Doris。
-X2Doris 是 SelectDB 开发的，专门用于将各种离线数据迁移到 Apache Doris 中的核心工具，该工具集 `自动建 Doris 表` 和
`数据迁移` 为一体，目前支持了 Apache Doris/Hive/Kudu、StarRocks 数据库往 Doris
迁移的工作，整个过程可视化的平台操作，非常简单易用，减轻数据同步到 Doris 中的门槛。
+X2Doris 专门用于将各种离线数据迁移到 Apache Doris 中的核心工具，该工具集 `自动建 Doris 表` 和 `数据迁移`
为一体，目前支持了 Apache Doris/Hive/Kudu、StarRocks 数据库往 Doris
迁移的工作，整个过程可视化的平台操作，非常简单易用，减轻数据同步到 Doris 中的门槛。
+
+:::info NOTE
+X2Doris 并非由 Apache Doris 维护或认可，这些工作由 Committers 和 Doris PMC
监督。使用这些资源和服务完全由您自行决定，社区不负责验证这些工具的许可或有效性。
+:::
## X2Doris 核心特性
@@ -43,8 +47,7 @@ X2Doris 是 SelectDB 开发的，专门用于将各种离线数据迁移到 Apac
定位于一站式数据迁移工具，X2Doris 目前已支持了 Apache Hive、Apache Kudu、StarRocks 以及 Apache Doris
自身作为数据源端，Greenplum、Druid 等更多数据源正在开发中，后续将陆续发布。其中 Hive 版本已支持 Hive 1.x 和 2.x
版本，Doris、StarRocks、Kudu 等数据源也同时支持了多个不同版本。
-目标端已支持 Apache Doris 和 SelectDB，包含 SelectDB Cloud 和 SelectDB Enterprise。基于
X2Doris 用户可以构建从其他 OLAP 系统到 Apache Doris 的整库迁移链路，并可以实现不同 Doris 集群间的数据备份和恢复。
-
+基于 X2Doris 用户可以构建从其他 OLAP 系统到 Apache Doris 的整库迁移链路，并可以实现不同 Doris 集群间的数据备份和恢复。
@@ -75,4 +78,4 @@ X2Doris 为此场景做了适配，在此以 Hive 表迁移为例。在迁移 Hi
- 立即下载：https://www.selectdb.com/download/tools#x2doris
--
文档地址：https://docs.selectdb.com/docs/ecosystem/x2doris/x2doris-deployment-guide
\ No newline at end of file
+-
文档地址：https://docs.selectdb.com/docs/ecosystem/x2doris/x2doris-deployment-guide
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/migrate-data-from-other-olap.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/migrate-data-from-other-olap.md
index c631c8a8056..cd08da9bd2e 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/migrate-data-from-other-olap.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/migrate-data-from-other-olap.md
@@ -35,7 +35,11 @@ under the License.
除了以上三种方式，[SelectDB](https://www.selectdb.com/tools/x2doris) 提供了免费的可视化的数据迁移工具
X2Doris。
-X2Doris 是 SelectDB 开发的，专门用于将各种离线数据迁移到 Apache Doris 中的核心工具，该工具集 `自动建 Doris 表` 和
`数据迁移` 为一体，目前支持了 Apache Doris/Hive/Kudu、StarRocks 数据库往 Doris
迁移的工作，整个过程可视化的平台操作，非常简单易用，减轻数据同步到 Doris 中的门槛。
+X2Doris 专门用于将各种离线数据迁移到 Apache Doris 中的核心工具，该工具集 `自动建 Doris 表` 和 `数据迁移`
为一体，目前支持了 Apache Doris/Hive/Kudu、StarRocks 数据库往 Doris
迁移的工作，整个过程可视化的平台操作，非常简单易用，减轻数据同步到 Doris 中的门槛。
+
+:::info NOTE
+X2Doris 并非由 Apache Doris 维护或认可，这些工作由 Committers 和 Doris PMC
监督。使用这些资源和服务完全由您自行决定，社区不负责验证这些工具的许可或有效性。
+:::
## X2Doris 核心特性
@@ -43,8 +47,7 @@ X2Doris 是 SelectDB 开发的，专门用于将各种离线数据迁移到 Apac
定位于一站式数据迁移工具，X2Doris 目前已支持了 Apache Hive、Apache Kudu、StarRocks 以及 Apache Doris
自身作为数据源端，Greenplum、Druid 等更多数据源正在开发中，后续将陆续发布。其中 Hive 版本已支持 Hive 1.x 和 2.x
版本，Doris、StarRocks、Kudu 等数据源也同时支持了多个不同版本。
-目标端已支持 Apache Doris 和 SelectDB，包含 SelectDB Cloud 和 SelectDB Enterprise。基于
X2Doris 用户可以构建从其他 OLAP 系统到 Apache Doris 的整库迁移链路，并可以实现不同 Doris 集群间的数据备份和恢复。
-
+基于 X2Doris 用户可以构建从其他 OLAP 系统到 Apache Doris 的整库迁移链路，并可以实现不同 Doris 集群间的数据备份和恢复。
@@ -75,4 +78,4 @@ X2Doris 为此场景做了适配，在此以 Hive 表迁移为例。在迁移 Hi
- 立即下载：https://www.selectdb.com/download/tools#x2doris
--
文档地址：https://docs.selectdb.com/docs/ecosystem/x2doris/x2doris-deployment-guide
\ No newline at end of file
+-
文档地址：https://docs.selectdb.com/docs/ecosystem/x2doris/x2doris-deployment-guide
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/sql-dialect.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/sql-dialect.md
index 06678e4eff1..b58a805f305 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/sql-dialect.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/lakehouse/sql-dialect.md
@@ -31,31 +31,27 @@ under the License.
:::
:::caution
-1. 该功能目前是实验性功能，您在使用过程中如遇到任何问题，欢迎通过邮件组、[GitHub
Issue](https://github.com/apache/doris/issues) 等方式进行反馈。
-
+该功能目前是实验性功能，您在使用过程中如遇到任何问题，欢迎通过邮件组、[GitHub
Issue](https://github.com/apache/doris/issues) 等方式进行反馈。
:::
## 部署服务
-**1. 下载最新版本的 [SQL 方言转换工具](https://www.selectdb.com/tools/doris-sql-convertor)**
-
- > 注：
- >
- > SQL 方言转换工具基于开源的 [SQLGlot](https://github.com/tobymao/sqlglot) 二次开发，关于
SQLGlot 可参阅 [SQLGlot 官网](https://sqlglot.com/sqlglot.html)
+1. 下载最新版本的 [SQL 方言转换工具](https://www.selectdb.com/tools/doris-sql-convertor)
+ :::info NOTE
+ SQL 方言转换工具基于开源的 [SQLGlot](https://github.com/tobymao/sqlglot) ，由 SelectDB
进行二次开发，关于 SQLGlot 可参阅 [SQLGlot 官网](https://sqlglot.com/sqlglot.html)。
+ SQL Convertor 并非由 Apache Doris 维护或认可，这些工作由 Committers 和 Doris PMC
监督。使用这些资源和服务完全由您自行决定，社区不负责验证这些工具的许可或有效性。
+ :::
2. 在任意 FE 节点，通过以下命令启动服务：
`sh bin/start.sh`
- :::tip
-
- **1. 该服务是一个无状态的服务，可随时启停。**
+ - 该服务是一个无状态的服务，可随时启停。
- 2. 默认启动端口是`5001`，可在`conf/config.conf`中配置指定端口。
+ - 默认启动端口是`5001`，可在`conf/config.conf`中配置指定端口。
- 3. 建议在每个 FE 节点都单独启动一个服务。
- :::
+ - 建议在每个 FE 节点都单独启动一个服务。
3. 启动 Doris 集群（2.1 或更高版本）
@@ -63,9 +59,7 @@ under the License.
`MySQL> set global sql_converter_service_url =
"http://127.0.0.1:5001/api/v1/convert"`
- :::tip
- `127.0.0.1:5001` 是 SQL 方言转换服务的部署节点 ip 和端口。
- :::
+ - `127.0.0.1:5001` 是 SQL 方言转换服务的部署节点 ip 和端口。
## 使用 SQL 方言
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/data-operate/import/migrate-data-from-other-olap.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/data-operate/import/migrate-data-from-other-olap.md
index c631c8a8056..cd08da9bd2e 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/data-operate/import/migrate-data-from-other-olap.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/data-operate/import/migrate-data-from-other-olap.md
@@ -35,7 +35,11 @@ under the License.
除了以上三种方式，[SelectDB](https://www.selectdb.com/tools/x2doris) 提供了免费的可视化的数据迁移工具
X2Doris。
-X2Doris 是 SelectDB 开发的，专门用于将各种离线数据迁移到 Apache Doris 中的核心工具，该工具集 `自动建 Doris 表` 和
`数据迁移` 为一体，目前支持了 Apache Doris/Hive/Kudu、StarRocks 数据库往 Doris
迁移的工作，整个过程可视化的平台操作，非常简单易用，减轻数据同步到 Doris 中的门槛。
+X2Doris 专门用于将各种离线数据迁移到 Apache Doris 中的核心工具，该工具集 `自动建 Doris 表` 和 `数据迁移`
为一体，目前支持了 Apache Doris/Hive/Kudu、StarRocks 数据库往 Doris
迁移的工作，整个过程可视化的平台操作，非常简单易用，减轻数据同步到 Doris 中的门槛。
+
+:::info NOTE
+X2Doris 并非由 Apache Doris 维护或认可，这些工作由 Committers 和 Doris PMC
监督。使用这些资源和服务完全由您自行决定，社区不负责验证这些工具的许可或有效性。
+:::
## X2Doris 核心特性
@@ -43,8 +47,7 @@ X2Doris 是 SelectDB 开发的，专门用于将各种离线数据迁移到 Apac
定位于一站式数据迁移工具，X2Doris 目前已支持了 Apache Hive、Apache Kudu、StarRocks 以及 Apache Doris
自身作为数据源端，Greenplum、Druid 等更多数据源正在开发中，后续将陆续发布。其中 Hive 版本已支持 Hive 1.x 和 2.x
版本，Doris、StarRocks、Kudu 等数据源也同时支持了多个不同版本。
-目标端已支持 Apache Doris 和 SelectDB，包含 SelectDB Cloud 和 SelectDB Enterprise。基于
X2Doris 用户可以构建从其他 OLAP 系统到 Apache Doris 的整库迁移链路，并可以实现不同 Doris 集群间的数据备份和恢复。
-
+基于 X2Doris 用户可以构建从其他 OLAP 系统到 Apache Doris 的整库迁移链路，并可以实现不同 Doris 集群间的数据备份和恢复。
@@ -75,4 +78,4 @@ X2Doris 为此场景做了适配，在此以 Hive 表迁移为例。在迁移 Hi
- 立即下载：https://www.selectdb.com/download/tools#x2doris
--
文档地址：https://docs.selectdb.com/docs/ecosystem/x2doris/x2doris-deployment-guide
\ No newline at end of file
+-
文档地址：https://docs.selectdb.com/docs/ecosystem/x2doris/x2doris-deployment-guide
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/lakehouse/sql-dialect.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/lakehouse/sql-dialect.md
index 06678e4eff1..b58a805f305 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/lakehouse/sql-dialect.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-3.0/lakehouse/sql-dialect.md
@@ -31,31 +31,27 @@ under the License.
:::
:::caution
-1. 该功能目前是实验性功能，您在使用过程中如遇到任何问题，欢迎通过邮件组、[GitHub
Issue](https://github.com/apache/doris/issues) 等方式进行反馈。
-
+该功能目前是实验性功能，您在使用过程中如遇到任何问题，欢迎通过邮件组、[GitHub
Issue](https://github.com/apache/doris/issues) 等方式进行反馈。
:::
## 部署服务
-**1. 下载最新版本的 [SQL 方言转换工具](https://www.selectdb.com/tools/doris-sql-convertor)**
-
- > 注：
- >
- > SQL 方言转换工具基于开源的 [SQLGlot](https://github.com/tobymao/sqlglot) 二次开发，关于
SQLGlot 可参阅 [SQLGlot 官网](https://sqlglot.com/sqlglot.html)
+1. 下载最新版本的 [SQL 方言转换工具](https://www.selectdb.com/tools/doris-sql-convertor)
+ :::info NOTE
+ SQL 方言转换工具基于开源的 [SQLGlot](https://github.com/tobymao/sqlglot) ，由 SelectDB
进行二次开发，关于 SQLGlot 可参阅 [SQLGlot 官网](https://sqlglot.com/sqlglot.html)。
+ SQL Convertor 并非由 Apache Doris 维护或认可，这些工作由 Committers 和 Doris PMC
监督。使用这些资源和服务完全由您自行决定，社区不负责验证这些工具的许可或有效性。
+ :::
2. 在任意 FE 节点，通过以下命令启动服务：
`sh bin/start.sh`
- :::tip
-
- **1. 该服务是一个无状态的服务，可随时启停。**
+ - 该服务是一个无状态的服务，可随时启停。
- 2. 默认启动端口是`5001`，可在`conf/config.conf`中配置指定端口。
+ - 默认启动端口是`5001`，可在`conf/config.conf`中配置指定端口。
- 3. 建议在每个 FE 节点都单独启动一个服务。
- :::
+ - 建议在每个 FE 节点都单独启动一个服务。
3. 启动 Doris 集群（2.1 或更高版本）
@@ -63,9 +59,7 @@ under the License.
`MySQL> set global sql_converter_service_url =
"http://127.0.0.1:5001/api/v1/convert"`
- :::tip
- `127.0.0.1:5001` 是 SQL 方言转换服务的部署节点 ip 和端口。
- :::
+ - `127.0.0.1:5001` 是 SQL 方言转换服务的部署节点 ip 和端口。
## 使用 SQL 方言
diff --git
a/versioned_docs/version-2.0/data-operate/import/migrate-data-from-other-olap.md
b/versioned_docs/version-2.0/data-operate/import/migrate-data-from-other-olap.md
index 4fcecbf4086..10ea5a10227 100644
---
a/versioned_docs/version-2.0/data-operate/import/migrate-data-from-other-olap.md
+++
b/versioned_docs/version-2.0/data-operate/import/migrate-data-from-other-olap.md
@@ -1,6 +1,6 @@
---
{
- "title": "Migrating data from other OLAP",
+ "title": "Migrating Data from Other OLAP",
"language": "en"
}
---
@@ -32,7 +32,13 @@ To migrate data from other OLAP systems to Doris, you have a
variety of options:
- You can also leverage the connectors of the OLAP systems, use tools like
Spark / Flink, and then call the corresponding Doris Connector to write data
into Doris.
-In addition to the above methods, [VeloDB](https://www.velodb.io), the
commercial supporter of Apache Doris, provides a free visual data migration
tool: X2Doris. Developed by VeloDB, X2Doris is designed to migrate various
offline data into Apache Doris. It combines the funtionalities of automatic
table creation and data migration. Currently, it supports migrating data to
Doris from databases including Apache Doris/Hive/Kudu and StarRocks. The entire
process is performed through a visual [...]
+In addition to the three methods mentioned above, VeloDB offers a free visual
data migration tool called [X2Doris](https://www.velodb.io/download/tools).
+
+X2Doris is a core tool specifically for migrating various offline data to
Apache Doris. This tool integrates `automatic Doris table creation` and `data
migration`. Currently, it supports the migration of data from Apache
Doris/Hive/Kudu, and StarRocks databases to Doris. The entire process is
visualized on a platform, making it very simple and easy to use, thereby
lowering the threshold for synchronizing data to Doris.
+
+:::info NOTE
+X2Doris are not maintained or endorsed by the Apache Doris, which is overseen
by the Committers and the Doris PMC. Their use is entirely at your discretion,
and the community is not responsible for verifying the licenses or validity of
these tools.
+:::
## X2Doris
@@ -40,7 +46,7 @@ In addition to the above methods,
[VeloDB](https://www.velodb.io), the commercia
As a one-stop data migration tool, X2Doris supports Apache Hive, Apache Kudu,
StarRocks, and Apache Doris itself as data source. What's more, there are more
data sources such as Greenplum and Druid that are under development and will be
released subsequently. Among them, the Hive version already supports Hive 1.x
and 2.x, while Doris, StarRocks, Kudu, and other data sources also support
multiple different versions.
-Now, X2Doris is supported migrating data to Apache Doris and VeloDB, including
VeloDB Cloud and VeloDB Enterprise. With X2Doris, users can build a complete
database migration link from other OLAP systems to Apache Doris, and can also
achieve data backup and recovery between different Doris clusters.
+With X2Doris, users can build a complete database migration link from other
OLAP systems to Apache Doris, and can also achieve data backup and recovery
between different Doris clusters.
diff --git a/versioned_docs/version-2.0/practical-guide/log-storage-analysis.md
b/versioned_docs/version-2.0/practical-guide/log-storage-analysis.md
index cb41a8e4d9c..f000b40bf25 100644
--- a/versioned_docs/version-2.0/practical-guide/log-storage-analysis.md
+++ b/versioned_docs/version-2.0/practical-guide/log-storage-analysis.md
@@ -68,7 +68,7 @@ After Benchmark testing and production validation, the log
storage and analysis
- **Improved write throughput**: Elasticsearch's write performance bottleneck
lies in CPU consumption for parsing data and building inverted indexes. In
comparison, Apache Doris has optimized writes in two aspects: using SIMD and
other CPU vector instructions to improve JSON data parsing speed and
index-building performance and simplifying the inverted index structure for log
scenarios by removing unnecessary data structures like forward indexes,
effectively reducing index build complexi [...]
-- **Reduced storage costs**: Elasticsearch's storage bottleneck comes from
multiple storage of forward, inverted, Docvalue columns, and lower compression
ratios with general compression algorithms. Conversely, Apache Doris has
optimized storage by eliminating forward indexes, reducing index data volume by
30%; adopting columnar storage and Zstandard compression algorithm, achieving
compression ratios 5-10 times higher than Elasticsearch's 1.5 times; with low
access frequency of cold data [...]
+- **Reduced Storage Costs**: The storage bottleneck in Elasticsearch lies in
the multiple storage formats for forward indexes, inverted indexes, and
Docvalue columns, as well as the relatively low compression ratio of its
general compression algorithms. In contrast, Apache Doris has made the
following optimizations in storage: it removes the forward index, reducing the
index data size by 30%; it uses columnar storage and the Zstandard compression
algorithm, achieving a compression ratio [...]
### Strong analytical capabilities
@@ -177,12 +177,6 @@ Refer to the following table to learn about the values of
indicators in the exam
After estimating the resources, you need to deploy the cluster. It is
recommended to deploy in both physical and virtual environments manually. For
manual deployment, refer to [Manual
Deployment](../install/cluster-deployment/standard-deployment.md).
-Alternatively, it is recommended to use VeloDB Manager provided by VeloDB
Enterprise to deploy the cluster, reducing overall deployment costs. For more
information about the VeloDB Manager, please refer to the following documents:
-
-- [VeloDB Manager 24.x Installation
Manual](https://docs.velodb.io/enterprise/velodb-manager-guide/deployment-guide/deployment-guide-24.x)
-
-- [VeloDB Manager 24.x User
Guide](https://docs.velodb.io/enterprise/velodb-manager-guide/management-guide/management-guide-24.x)
-
### Step 3: Optimize FE and BE configurations
After completing the cluster deployment, it is necessary to optimize the
configuration parameters for both the front-end and back-end separately, so as
to better suit the scenario of log storage and analysis.
@@ -580,12 +574,10 @@ ORDER BY ts DESC LIMIT 10;
**Analyze logs visually**
-VeloDB Enterprise Core, built on Apache Doris, provides a data development
platform called VeloDB Enterprise WebUI ("WebUI"), featuring a Kibana
Discover-like log retrieval and analysis interface for intuitive and easy
exploratory log analysis interaction as shown in the image below:
+Some third-party vendors offer visual log analysis development platforms based
on Apache Doris, which include a log search and analysis interface similar to
Kibana Discover. These platforms provide an intuitive and user-friendly
exploratory log analysis interaction.
-On this interface, WebUI supports the following operations:
-
- Support for full-text search and SQL modes
- Support for selecting query log timeframes with time boxes and histograms
@@ -596,4 +588,4 @@ On this interface, WebUI supports the following operations:
- Display of top field values in search results for finding anomalies and
further drilling down for analysis
-You can [click to download VeloDB Enterprise
Core](https://www.velodb.io/download/enterprise) and [install
it](https://docs.velodb.io/enterprise/enterprise-core-guide/velodb-distribution-doris-core-deployment-guide)
to use WebUI. For more information about the main functions and how to use
WebUI, see
[WebUI](https://docs.velodb.io/enterprise/enterprise-core-guide/velodb-webui-guide).
\ No newline at end of file
+Please contact d...@doris.apache.org to find more.
diff --git
a/versioned_docs/version-2.1/data-operate/import/migrate-data-from-other-olap.md
b/versioned_docs/version-2.1/data-operate/import/migrate-data-from-other-olap.md
index 1a54eb939b0..10ea5a10227 100644
---
a/versioned_docs/version-2.1/data-operate/import/migrate-data-from-other-olap.md
+++
b/versioned_docs/version-2.1/data-operate/import/migrate-data-from-other-olap.md
@@ -32,7 +32,13 @@ To migrate data from other OLAP systems to Doris, you have a
variety of options:
- You can also leverage the connectors of the OLAP systems, use tools like
Spark / Flink, and then call the corresponding Doris Connector to write data
into Doris.
-In addition to the above methods, [VeloDB](https://www.velodb.io), the
commercial supporter of Apache Doris, provides a free visual data migration
tool: X2Doris. Developed by VeloDB, X2Doris is designed to migrate various
offline data into Apache Doris. It combines the funtionalities of automatic
table creation and data migration. Currently, it supports migrating data to
Doris from databases including Apache Doris/Hive/Kudu and StarRocks. The entire
process is performed through a visual [...]
+In addition to the three methods mentioned above, VeloDB offers a free visual
data migration tool called [X2Doris](https://www.velodb.io/download/tools).
+
+X2Doris is a core tool specifically for migrating various offline data to
Apache Doris. This tool integrates `automatic Doris table creation` and `data
migration`. Currently, it supports the migration of data from Apache
Doris/Hive/Kudu, and StarRocks databases to Doris. The entire process is
visualized on a platform, making it very simple and easy to use, thereby
lowering the threshold for synchronizing data to Doris.
+
+:::info NOTE
+X2Doris are not maintained or endorsed by the Apache Doris, which is overseen
by the Committers and the Doris PMC. Their use is entirely at your discretion,
and the community is not responsible for verifying the licenses or validity of
these tools.
+:::
## X2Doris
@@ -40,7 +46,7 @@ In addition to the above methods,
[VeloDB](https://www.velodb.io), the commercia
As a one-stop data migration tool, X2Doris supports Apache Hive, Apache Kudu,
StarRocks, and Apache Doris itself as data source. What's more, there are more
data sources such as Greenplum and Druid that are under development and will be
released subsequently. Among them, the Hive version already supports Hive 1.x
and 2.x, while Doris, StarRocks, Kudu, and other data sources also support
multiple different versions.
-Now, X2Doris is supported migrating data to Apache Doris and VeloDB, including
VeloDB Cloud and VeloDB Enterprise. With X2Doris, users can build a complete
database migration link from other OLAP systems to Apache Doris, and can also
achieve data backup and recovery between different Doris clusters.
+With X2Doris, users can build a complete database migration link from other
OLAP systems to Apache Doris, and can also achieve data backup and recovery
between different Doris clusters.
diff --git a/versioned_docs/version-2.1/lakehouse/sql-dialect.md
b/versioned_docs/version-2.1/lakehouse/sql-dialect.md
index e7aafe870f2..7f3c9ddd26d 100644
--- a/versioned_docs/version-2.1/lakehouse/sql-dialect.md
+++ b/versioned_docs/version-2.1/lakehouse/sql-dialect.md
@@ -31,38 +31,32 @@ Starting from version 2.1, Doris can support multiple SQL
dialects, such as Pres
:::
:::caution
- 1. This function is currently an experimental function. If you encounter any
problems during use, you are welcome to provide feedback through the mail
group, [GitHub issue](https://github.com/apache/doris/issues), etc. .
-
+This function is currently an experimental function. If you encounter any
problems during use, you are welcome to provide feedback through the mail
group, [GitHub issue](https://github.com/apache/doris/issues)
:::
## Deploy service
1. Download latest [Doris SQL
Convertor](https://www.selectdb.com/tools/doris-sql-convertor)
- > Note:
- >
- > The SQL convertor tool is based on the open source
[SQLGlot](https://github.com/tobymao/sqlglot). For more information about
SQLGlot, please refer to [SQLGlot official
website](https://sqlglot.com/sqlglot.html)
+ :::info NOTE
+ The SQL dialect conversion tool is based on the open-source
[SQLGlot](https://github.com/tobymao/sqlglot) and has been further developed by
SelectDB. For more information about SQLGlot, please refer to the [SQLGlot
official website](https://sqlglot.com/sqlglot.html).
+The SQL Convertor is not maintained or endorsed by Apache Doris; these efforts
are supervised by Committers and the Doris PMC. The use of these resources and
services is entirely at your own discretion, and the community does not verify
the licensing or validity of these tools.
+ :::
2. On any FE node, start the service through the following command:
`sh bin/start.sh`
- :::tip
- 1. This service is a stateless service and can be started and stopped
at any time.
-
- 2. The default startup port is `5001`, and the specified port can be
configured in `conf/config.conf`.
-
- 3. It is recommended to start a separate service on each FE node.
- :::
+ - This service is a stateless service and can be started and stopped at
any time.
+ - The default startup port is `5001`, and the specified port can be
configured in `conf/config.conf`.
+ - It is recommended to start a separate service on each FE node.
3. Start the Doris cluster (version 2.1 or higher)
4. Set the URL of the SQL Dialect Conversion Service with the following
command in Doris:
`MySQL> set global sql_converter_service_url =
"http://127.0.0.1:5001/api/v1/convert"`
- :::tip
- 1. `127.0.0.1:5001` is the deployment node IP and port of the SQL
dialect conversion service.
- :::
+ - `127.0.0.1:5001` is the deployment node IP and port of the SQL
dialect conversion service.
## Use SQL dialect
diff --git a/versioned_docs/version-2.1/practical-guide/log-storage-analysis.md
b/versioned_docs/version-2.1/practical-guide/log-storage-analysis.md
index cb41a8e4d9c..f000b40bf25 100644
--- a/versioned_docs/version-2.1/practical-guide/log-storage-analysis.md
+++ b/versioned_docs/version-2.1/practical-guide/log-storage-analysis.md
@@ -68,7 +68,7 @@ After Benchmark testing and production validation, the log
storage and analysis
- **Improved write throughput**: Elasticsearch's write performance bottleneck
lies in CPU consumption for parsing data and building inverted indexes. In
comparison, Apache Doris has optimized writes in two aspects: using SIMD and
other CPU vector instructions to improve JSON data parsing speed and
index-building performance and simplifying the inverted index structure for log
scenarios by removing unnecessary data structures like forward indexes,
effectively reducing index build complexi [...]
-- **Reduced storage costs**: Elasticsearch's storage bottleneck comes from
multiple storage of forward, inverted, Docvalue columns, and lower compression
ratios with general compression algorithms. Conversely, Apache Doris has
optimized storage by eliminating forward indexes, reducing index data volume by
30%; adopting columnar storage and Zstandard compression algorithm, achieving
compression ratios 5-10 times higher than Elasticsearch's 1.5 times; with low
access frequency of cold data [...]
+- **Reduced Storage Costs**: The storage bottleneck in Elasticsearch lies in
the multiple storage formats for forward indexes, inverted indexes, and
Docvalue columns, as well as the relatively low compression ratio of its
general compression algorithms. In contrast, Apache Doris has made the
following optimizations in storage: it removes the forward index, reducing the
index data size by 30%; it uses columnar storage and the Zstandard compression
algorithm, achieving a compression ratio [...]
### Strong analytical capabilities
@@ -177,12 +177,6 @@ Refer to the following table to learn about the values of
indicators in the exam
After estimating the resources, you need to deploy the cluster. It is
recommended to deploy in both physical and virtual environments manually. For
manual deployment, refer to [Manual
Deployment](../install/cluster-deployment/standard-deployment.md).
-Alternatively, it is recommended to use VeloDB Manager provided by VeloDB
Enterprise to deploy the cluster, reducing overall deployment costs. For more
information about the VeloDB Manager, please refer to the following documents:
-
-- [VeloDB Manager 24.x Installation
Manual](https://docs.velodb.io/enterprise/velodb-manager-guide/deployment-guide/deployment-guide-24.x)
-
-- [VeloDB Manager 24.x User
Guide](https://docs.velodb.io/enterprise/velodb-manager-guide/management-guide/management-guide-24.x)
-
### Step 3: Optimize FE and BE configurations
After completing the cluster deployment, it is necessary to optimize the
configuration parameters for both the front-end and back-end separately, so as
to better suit the scenario of log storage and analysis.
@@ -580,12 +574,10 @@ ORDER BY ts DESC LIMIT 10;
**Analyze logs visually**
-VeloDB Enterprise Core, built on Apache Doris, provides a data development
platform called VeloDB Enterprise WebUI ("WebUI"), featuring a Kibana
Discover-like log retrieval and analysis interface for intuitive and easy
exploratory log analysis interaction as shown in the image below:
+Some third-party vendors offer visual log analysis development platforms based
on Apache Doris, which include a log search and analysis interface similar to
Kibana Discover. These platforms provide an intuitive and user-friendly
exploratory log analysis interaction.
-On this interface, WebUI supports the following operations:
-
- Support for full-text search and SQL modes
- Support for selecting query log timeframes with time boxes and histograms
@@ -596,4 +588,4 @@ On this interface, WebUI supports the following operations:
- Display of top field values in search results for finding anomalies and
further drilling down for analysis
-You can [click to download VeloDB Enterprise
Core](https://www.velodb.io/download/enterprise) and [install
it](https://docs.velodb.io/enterprise/enterprise-core-guide/velodb-distribution-doris-core-deployment-guide)
to use WebUI. For more information about the main functions and how to use
WebUI, see
[WebUI](https://docs.velodb.io/enterprise/enterprise-core-guide/velodb-webui-guide).
\ No newline at end of file
+Please contact d...@doris.apache.org to find more.
diff --git
a/versioned_docs/version-3.0/data-operate/import/migrate-data-from-other-olap.md
b/versioned_docs/version-3.0/data-operate/import/migrate-data-from-other-olap.md
index 1a54eb939b0..10ea5a10227 100644
---
a/versioned_docs/version-3.0/data-operate/import/migrate-data-from-other-olap.md
+++
b/versioned_docs/version-3.0/data-operate/import/migrate-data-from-other-olap.md
@@ -32,7 +32,13 @@ To migrate data from other OLAP systems to Doris, you have a
variety of options:
- You can also leverage the connectors of the OLAP systems, use tools like
Spark / Flink, and then call the corresponding Doris Connector to write data
into Doris.
-In addition to the above methods, [VeloDB](https://www.velodb.io), the
commercial supporter of Apache Doris, provides a free visual data migration
tool: X2Doris. Developed by VeloDB, X2Doris is designed to migrate various
offline data into Apache Doris. It combines the funtionalities of automatic
table creation and data migration. Currently, it supports migrating data to
Doris from databases including Apache Doris/Hive/Kudu and StarRocks. The entire
process is performed through a visual [...]
+In addition to the three methods mentioned above, VeloDB offers a free visual
data migration tool called [X2Doris](https://www.velodb.io/download/tools).
+
+X2Doris is a core tool specifically for migrating various offline data to
Apache Doris. This tool integrates `automatic Doris table creation` and `data
migration`. Currently, it supports the migration of data from Apache
Doris/Hive/Kudu, and StarRocks databases to Doris. The entire process is
visualized on a platform, making it very simple and easy to use, thereby
lowering the threshold for synchronizing data to Doris.
+
+:::info NOTE
+X2Doris are not maintained or endorsed by the Apache Doris, which is overseen
by the Committers and the Doris PMC. Their use is entirely at your discretion,
and the community is not responsible for verifying the licenses or validity of
these tools.
+:::
## X2Doris
@@ -40,7 +46,7 @@ In addition to the above methods,
[VeloDB](https://www.velodb.io), the commercia
As a one-stop data migration tool, X2Doris supports Apache Hive, Apache Kudu,
StarRocks, and Apache Doris itself as data source. What's more, there are more
data sources such as Greenplum and Druid that are under development and will be
released subsequently. Among them, the Hive version already supports Hive 1.x
and 2.x, while Doris, StarRocks, Kudu, and other data sources also support
multiple different versions.
-Now, X2Doris is supported migrating data to Apache Doris and VeloDB, including
VeloDB Cloud and VeloDB Enterprise. With X2Doris, users can build a complete
database migration link from other OLAP systems to Apache Doris, and can also
achieve data backup and recovery between different Doris clusters.
+With X2Doris, users can build a complete database migration link from other
OLAP systems to Apache Doris, and can also achieve data backup and recovery
between different Doris clusters.
diff --git a/versioned_docs/version-3.0/lakehouse/sql-dialect.md
b/versioned_docs/version-3.0/lakehouse/sql-dialect.md
index e7aafe870f2..7f3c9ddd26d 100644
--- a/versioned_docs/version-3.0/lakehouse/sql-dialect.md
+++ b/versioned_docs/version-3.0/lakehouse/sql-dialect.md
@@ -31,38 +31,32 @@ Starting from version 2.1, Doris can support multiple SQL
dialects, such as Pres
:::
:::caution
- 1. This function is currently an experimental function. If you encounter any
problems during use, you are welcome to provide feedback through the mail
group, [GitHub issue](https://github.com/apache/doris/issues), etc. .
-
+This function is currently an experimental function. If you encounter any
problems during use, you are welcome to provide feedback through the mail
group, [GitHub issue](https://github.com/apache/doris/issues)
:::
## Deploy service
1. Download latest [Doris SQL
Convertor](https://www.selectdb.com/tools/doris-sql-convertor)
- > Note:
- >
- > The SQL convertor tool is based on the open source
[SQLGlot](https://github.com/tobymao/sqlglot). For more information about
SQLGlot, please refer to [SQLGlot official
website](https://sqlglot.com/sqlglot.html)
+ :::info NOTE
+ The SQL dialect conversion tool is based on the open-source
[SQLGlot](https://github.com/tobymao/sqlglot) and has been further developed by
SelectDB. For more information about SQLGlot, please refer to the [SQLGlot
official website](https://sqlglot.com/sqlglot.html).
+The SQL Convertor is not maintained or endorsed by Apache Doris; these efforts
are supervised by Committers and the Doris PMC. The use of these resources and
services is entirely at your own discretion, and the community does not verify
the licensing or validity of these tools.
+ :::
2. On any FE node, start the service through the following command:
`sh bin/start.sh`
- :::tip
- 1. This service is a stateless service and can be started and stopped
at any time.
-
- 2. The default startup port is `5001`, and the specified port can be
configured in `conf/config.conf`.
-
- 3. It is recommended to start a separate service on each FE node.
- :::
+ - This service is a stateless service and can be started and stopped at
any time.
+ - The default startup port is `5001`, and the specified port can be
configured in `conf/config.conf`.
+ - It is recommended to start a separate service on each FE node.
3. Start the Doris cluster (version 2.1 or higher)
4. Set the URL of the SQL Dialect Conversion Service with the following
command in Doris:
`MySQL> set global sql_converter_service_url =
"http://127.0.0.1:5001/api/v1/convert"`
- :::tip
- 1. `127.0.0.1:5001` is the deployment node IP and port of the SQL
dialect conversion service.
- :::
+ - `127.0.0.1:5001` is the deployment node IP and port of the SQL
dialect conversion service.
## Use SQL dialect
diff --git a/versioned_docs/version-3.0/practical-guide/log-storage-analysis.md
b/versioned_docs/version-3.0/practical-guide/log-storage-analysis.md
index 5637457b6b5..f000b40bf25 100644
--- a/versioned_docs/version-3.0/practical-guide/log-storage-analysis.md
+++ b/versioned_docs/version-3.0/practical-guide/log-storage-analysis.md
@@ -68,7 +68,7 @@ After Benchmark testing and production validation, the log
storage and analysis
- **Improved write throughput**: Elasticsearch's write performance bottleneck
lies in CPU consumption for parsing data and building inverted indexes. In
comparison, Apache Doris has optimized writes in two aspects: using SIMD and
other CPU vector instructions to improve JSON data parsing speed and
index-building performance and simplifying the inverted index structure for log
scenarios by removing unnecessary data structures like forward indexes,
effectively reducing index build complexi [...]
-- **Reduced storage costs**: Elasticsearch's storage bottleneck comes from
multiple storage of forward, inverted, Docvalue columns, and lower compression
ratios with general compression algorithms. Conversely, Apache Doris has
optimized storage by eliminating forward indexes, reducing index data volume by
30%; adopting columnar storage and Zstandard compression algorithm, achieving
compression ratios 5-10 times higher than Elasticsearch's 1.5 times; with low
access frequency of cold data [...]
+- **Reduced Storage Costs**: The storage bottleneck in Elasticsearch lies in
the multiple storage formats for forward indexes, inverted indexes, and
Docvalue columns, as well as the relatively low compression ratio of its
general compression algorithms. In contrast, Apache Doris has made the
following optimizations in storage: it removes the forward index, reducing the
index data size by 30%; it uses columnar storage and the Zstandard compression
algorithm, achieving a compression ratio [...]
### Strong analytical capabilities
@@ -177,12 +177,6 @@ Refer to the following table to learn about the values of
indicators in the exam
After estimating the resources, you need to deploy the cluster. It is
recommended to deploy in both physical and virtual environments manually. For
manual deployment, refer to [Manual
Deployment](../install/cluster-deployment/standard-deployment.md).
-Alternatively, it is recommended to use VeloDB Manager provided by VeloDB
Enterprise to deploy the cluster, reducing overall deployment costs. For more
information about the VeloDB Manager, please refer to the following documents:
-
-- [VeloDB Manager 24.x Installation
Manual](https://docs.velodb.io/enterprise/velodb-manager-guide/deployment-guide/deployment-guide-24.x)
-
-- [VeloDB Manager 24.x User
Guide](https://docs.velodb.io/enterprise/velodb-manager-guide/management-guide/management-guide-24.x)
-
### Step 3: Optimize FE and BE configurations
After completing the cluster deployment, it is necessary to optimize the
configuration parameters for both the front-end and back-end separately, so as
to better suit the scenario of log storage and analysis.
@@ -398,7 +392,7 @@ output {
3. Run Logstash according to the command below, collect logs, and output to
Apache Doris.
-```shell
+```shell
./bin/logstash -f logstash_demo.conf
```
@@ -580,12 +574,10 @@ ORDER BY ts DESC LIMIT 10;
**Analyze logs visually**
-VeloDB Enterprise Core, built on Apache Doris, provides a data development
platform called VeloDB Enterprise WebUI ("WebUI"), featuring a Kibana
Discover-like log retrieval and analysis interface for intuitive and easy
exploratory log analysis interaction as shown in the image below:
+Some third-party vendors offer visual log analysis development platforms based
on Apache Doris, which include a log search and analysis interface similar to
Kibana Discover. These platforms provide an intuitive and user-friendly
exploratory log analysis interaction.
-On this interface, WebUI supports the following operations:
-
- Support for full-text search and SQL modes
- Support for selecting query log timeframes with time boxes and histograms
@@ -596,4 +588,4 @@ On this interface, WebUI supports the following operations:
- Display of top field values in search results for finding anomalies and
further drilling down for analysis
-You can [click to download VeloDB Enterprise
Core](https://www.velodb.io/download/enterprise) and [install
it](https://docs.velodb.io/enterprise/enterprise-core-guide/velodb-distribution-doris-core-deployment-guide)
to use WebUI. For more information about the main functions and how to use
WebUI, see
[WebUI](https://docs.velodb.io/enterprise/enterprise-core-guide/velodb-webui-guide).
\ No newline at end of file
+Please contact d...@doris.apache.org to find more.
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org
For additional commands, e-mail: commits-h...@doris.apache.org
